Difference between jenkins and Urbancode build

What is the difference between jenkins and Urbancode build?

jenkins Urbancode build
Jenkins is open framework for automating the repeative tasks and has great plugins which can be used to create entire automated customized continous integration framework. Urbancode build(uBuild) is for automating the repeative tasks and has great limited sets of plugins which can be used to create entire automated continous integration flow.
Jenkins can deliver core CI loop: Detect a change, do a build, test, and deliver feedback and its open framework allows and can be used for software Deployment as well. Urbancode build(uBuild) can deliver core CI loop: Detect a change, do a build, test, and deliver feedback but it can be not be used for deployment. Urbancode Deploy(uDeploy) is another product by IBM which can be used for deployment.
Jenkins can be extended with Large sets of plugins https://plugins.jenkins.io/ Urbancode build(uBuild) can be extended with Limited sets of plugins https://developer.ibm.com/urbancode/plugins/
Jenkins is one of top active Open Source and free developed in Java. Urbancode build(uBuild) is properiety tool by IBM, previously known as Urbancode and developed in Java
Jenkins has plugins which needs extra learning curve by development teams for centrally defined templates Urbancode build(uBuild) has built-in Easy addition of new projects by development teams based on centrally defined templates
Jenkins has Dependency management and but not awareness. Build based on project relationships. Urbancode build(uBuild) has Dependency management and awareness. Build based on project relationships.

My Recommendation – Jenkins

Tagged : / / / /

How to Install plug-ins in IBM UrbanCode Deploy

Procedure

  1. Download the installation files for one or more plug-ins from the following site: https://developer.ibm.com/urbancode/plugins/ibm-urbancode-deploy/
  2. Load the plug-ins:
    1. For automation plug-ins, click Settings > Automation Plugins, then click Load Plugin.
    2. For source plug-ins, click Settings > Source Config Plugins, then click Load Plugin.
    3. Enter the path to the compressed plug-in file, and then click Submit.

Results

The plug-in is listed on either the Automation Plugins pane or the Source Config Plugins pane. After the plug-in is installed, it is available immediately.

Uninstalling a plug-in

To uninstall a plug-in, click Settings > Automation Plugins, find the plug-in, and then click Delete.

Note: Before uninstalling a plug-in, verify that it is no longer in use. Deleting a plug-in which is being used by existing processes causes those processes to be invalid.

Rolling back plug-ins

You cannot roll back a plug-in version to a previous version. If you have mistakenly deleted a version of a plug-in being used in processes, the step will display “PLUGIN DELETED”. The server retains the pertinent steps to avoid breaking persistent processes and snapshots, but the configuration should be updated according to intention. If the intention is to use an earlier version of the plug-in, perform the following steps:

    1. Uninstall (Delete) the later version of the plug-in. Now, in all processes, steps from that plug-in are shown with the text “PLUGIN DELETED”. These steps should never be left in this state.Note: The server retains the later version steps to avoid breaking snapshots. However, you cannot add these steps to processes after you delete the plug-in. All deleted steps should be updated immediately.
    2. Install the earlier version of the plug-in (if not already installed).Note: If an earlier plug-in version was installed and previously upgraded, this step is not necessary, as the previous version will be now be usable again.
    3. In each process that used steps from the later plug-in, re-create and delete the steps that are labeled “PLUGIN DELETED.” This will “roll back” the step from the later to earlier version. The process steps cannot be changed until you re-create them, even if you installed another version of the plug-in.

Note: Re-installing the later version of the plug-in will restore the processes.

Tagged : / /

How to Install plug-ins in IBM UrbanCode Release

 

Procedure

  1. Download the installation files for one or more plug-ins from the following site: https://developer.ibm.com/urbancode/plugins/ibm-urbancode-build/. Do not extract the compressed files.
  2. Load the plug-ins:
    1. From the IBM UrbanCode Build user interface, click the System tab.
    2. In the Server group, click Plug-ins.
    3. On the Plugins page, Browse and locate the plug-in installation file and then click Open.
    4. On the Plugins page, click Load.

Results

After the upload to the server is complete, the plug-in is listed on the Plugins page and available for immediate use.

Uninstalling a plug-in

To uninstall a plug-in, click System > Plug-ins, locate the plug-in, and then click the Delete icon.

Note: Before uninstalling a plug-in, verify that it is no longer in use. Deleting a plug-in which is being used by existing processes causes those processes to be invalid.

Tagged : / / /

How to Install plug-ins in IBM UrbanCode Build

Procedure

  1. Download the installation files for one or more plug-ins from the following site: https://developer.ibm.com/urbancode/plugins/ibm-urbancode-build/. Do not extract the compressed files.
  2. Load the plug-ins:
    1. From the IBM UrbanCode Build user interface, click the System tab.
    2. In the Server group, click Plug-ins.
    3. On the Plugins page, Browse and locate the plug-in installation file and then click Open.
    4. On the Plugins page, click Load.

Results

After the upload to the server is complete, the plug-in is listed on the Plugins page and available for immediate use.

Uninstalling a plug-in

To uninstall a plug-in, click System > Plug-ins, locate the plug-in, and then click the Delete icon.

Note: Before uninstalling a plug-in, verify that it is no longer in use. Deleting a plug-in which is being used by existing processes causes those processes to be invalid.

Tagged : / / / /

Upgrading from IBM uBuild 5.0.1.3 or earlier

SSLv3 is no longer supported by IBM uBuild or IBM UrbanCode Build due to the POODLE vulnerability. In fixing the vulnerability, there are a few steps that should be taken prior to upgrading to uBuild 5.0.1.4 or later and UrbanCode Build 6.1 and later.

Before starting your upgrade, you should do the following:

  1. Shut down your IBM uBuild or IBM UrbanCode Build server
  2. Download the latest IBM UrbanCode Build release
  3. Extract the IBM UrbanCode Build .zip file
  4. Navigate to extracted directory
  5. Navigate to the agentupgrade directory
  6. Copy the air-agentupgrade.jar file to your existing server’s opt/tomcat/webapps/ROOT directory
  7. When prompted, replace the existing file
  8. Start your IBM uBuild or IBM UrbanCode Build server
  9. Navigate to the Agents tab
  10. Select all existing agents and tell them to upgrade

Upgrading the agents ahead of time prevents an issue where old agents are no longer able to connect to the IBM UrbanCode Build server because they try to use SSLv3. If you do not upgrade proactively the agents will be unable to communicate with the server, requiring manual upgrades. Once all of your existing agents have been upgraded, proceed to upgrade your server as you normally would.

Once you have upgraded your server, you must also upgrade any plugins that upload any information back to the server. This would include any issue tracking, reporting, or SCM plugins. If the plugins are not upgraded, you will see an SSL Handshake Exception whenever step from the plugin tries to upload anything to the server.

The full list of plugins that need to be upgraded is as follows:

  • AccuRev
  • AccuWork
  • Checkstyle
  • ClearQuest
  • Cobertura
  • CodeStation
  • CppUnit
  • CVS
  • FileSystem
  • FindBugs
  • Git
  • HP Fortify
  • HP Quality Center
  • JaCoCo
  • JIRA
  • JUnit
  • Mercurial
  • MSTest
  • NUnit
  • Perforce
  • PMD
  • Rally
  • Rational Team Concert SCM
  • Rational Team Concert Work Items
  • Report Publisher
  • Reporting
  • Sonargraph
  • SonarQube
  • Team Foundation Server
  • TFS Work Items

Reference

https://developer.ibm.com/urbancode/docs/upgrading-ibm-ubuild-5-0-1-3-earlier/

 

Tagged : / /