wiki
Wiki: CUBiT FAQ

CollabNet CUBiT FAQ

CUBiT Community Home -- FAQ Index -- Find Page

CUBiT Product Questions

What is CUBiT?

• Cubit is an acronym for “Centralized Unified Build, Integration, and Test”.
• It allows developers and users to dynamically provision their own systems from a pool of centralized virtual and physical resources based on reusable profiles - a role that traditionally fulfilled by IT infrastructure groups.

What are Profiles?

• Profiles contain a description of an operating system which may or may not include additional applications.
• When a profile is applied to a physical or virtual resource a fully functional system is provisioned based on the exact description within the profile.
• Profiles are also versioned controlled by Subversion, allowing re-provisioning of system stacks to a point in time.

What is a Build Library?

• A Build Library is a central storage area that is not versioned controlled for binaries that are associated with a software development project.
• These binaries can be daily builds or software package that requires distribution amongst developers.

What is the intended use of a Build Library?

• The Build Library can securely store builds and packages that require distribution and reuse amongst developers.
• Access control to the Build Library adds additional security that is required by regulatory compliance.
• Centralization minimizes the duplication of binaries and thus reduces the storage costs.
• Cubit provides hooks between Profiles and the Build Library allow systems that are newly provisioned to reach back into the Build Library and install asset that are already built and stored.

How are users restricted within CUBiT?

• CUBiT is integrated into either ?SourceForge Enterprise Edition or ?CollabNet Enterprise Edition that provides fine grained role based access.

• Projects are the core resource container with CUBiT.
• Within each Project are enrolled users and developers that can be granted differing authorization levels.
• Additionally within Projects are virtual and physical assets that can be provisioned to become fully functional systems.
• Provisioning capabilities of individual users are determined by their role within CUBiT.
• Currently there are four roles in CUBiT, from minimum to most privileges are User, Root, Project Administrator and Domain Administrator.

What operating systems and hardware does CUBiT support?

• Windows XP, Windows 2003 including R2 and Windows 2000
• Red Hat Enterprise and Advance Server, Version 3, 4 and 5
• CentOS Enterprise 3, 4 and 5
• Solaris version 10 (x86 and Sparc)

Can I deploy CUBiT in my data center with hardware I already own?

• yes, you can install CUBiT within you own datacenter

How does CUBiT support centralized build management? Does it work with build tools?

• CUBiT provisioned systems (also known as client nodes) will natively support any centralized build management that will run on an operating system supported by CUBiT.

• ?CollabNet can also provide and support “custom” profiles that can provision ?CruiseControl and Maven continuous build management.

• Through CUBiT’s Web API’s, integration and workflow can be constructed to achieve an automated build and test process.

Trouble Shooting

I cannot establish a SSH / Putty session to my Linux or Solaris CUBiT system using a SSH tunnel

First check that you system is “UP” from the CUBiT manager by login into your CUBiT instance.

1. If your system is down it can be rebooted from the CUBiT manager interface “Projects -> CUBiT -> hosts -> {system} -> Configuration -> Reboot

2. If the system remains “Down” after a reboot then contact your AEDC domain

Check that your SSH tunnel is configured correctly using Putty

1. Check that the Host Name is set correctly.

2. Go into your session settings and review SSH -> Tunnels. Make sure that your SSH tunnel rules exists and is set correctly.

3. Make sure that you initial putty tunnel that creates the SSH tunnel remains open whilst opening a SSH session to CUBiT system.
4. Make sure that your initial SSH tunnel session responds with “Tunnel established” message
5. Make sure that the high numbered port that you specified for your local workstation in your rule does not conflict with any other listening services. You can determine this by running “netstat –an” from a command prompt and review all LISTENING services and cross reference port numbers.
6. If you still can not connect then contact you CUBiT domain administrator.

I'm having problems connecting my Eclipse IDE to CUBiT

Make sure that the “?CollabNet” Perspective is available and open.

• From Eclipse “Windows -> Open Perspective -> Other -> ?CollabNet”

Make sure that your Eclipse ?CollabNet settings are correct. Right click your CUBiT connection in the ?CollabNet Perspective and check the following:

• Make sure the URL is set correctly
• Your “User name” is set correctly
• Your API key is set correctly. You can confirm this by login into the CUBiT manager and check the bottom of “My Pages”
• Make sure that “Tunnels required” is checked

Make sure that your workstation can connect to the CUBiT manager

• Test by connecting via a web browser to your CUBiT instance and logon with userid/passwd

Do you have more that one CUBiT connection configured in your ?CollabNet Perspective? This can cause secure tunnel conflicts.

• Delete any unnecessary CUBiT connections from your ?CollabNet Perspective

If you still continue to have problems then contact you CUBiT domain administrator.

I Cannot connect to CUBiT using port forwarding with SSH/Putty

This is also applicable to VNC and RDP.

Confirm with your CUBiT domain administrator that your port forwarding rule has been added:

• Typically for SSH the rule should target a destination port of TCP 22
• Typically for RDP the rule should target a destination port of TCP 3389
• Typically for VNC the rule should target a destination port of TCP 5900 or 5901

When you establish your remote connection using either SSH, VNC or RDP you must target CUBIT box with the number as defined in port forwarding rule and as specified by your domain administrator.