A Linux or macOS system (Windows is not supported at this time)

zip, unzip, wget

$yum install zip -y
$ yum install unzip -y
$ yum install wget -y
$ yum install git -y

Python 2 or 3
This is installed in each RHEL 7 and Ubunutu server by defaul.

Node.js

curl --silent --location https://rpm.nodesource.com/setup_8.x | sudo bash -
OR
curl --silent --location https://rpm.nodesource.com/setup_10.x | sudo bash -
sudo yum -y install nodejs

Bazel

## RHEL/CentOS 7 64-Bit ##
$ wget https://copr.fedorainfracloud.org/coprs/vbatts/bazel/repo/epel-7/vbatts-bazel-epel-7.repo
$ cp vbatts-bazel-epel-7.repo /etc/yum.repos.d/
$ yum install -y bazel

How to Installing Bazel on Ubuntu?
https://docs.bazel.build/versions/master/install-ubuntu.html

Maven

$ cd /opt
$ wget http://www-us.apache.org/dist/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.zip
$ unzip apache-maven-3.5.4-bin.zip
$ mv apache-maven-3.5.4 maven
$ export PATH=$PATH:/op/maven/bin

gcc

$ sudo yum install gcc-c++ make

Now, Bazel in tree driven means it can only be built from within Gerrit tree. Clone or link the plugin into gerrit/plugins directory:

# First become a non-root user

A JDK for Java 8

$ cd
$ wget -c --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u181-b13/96a7b8442fe848ef90c96a2fad6ed6d1/jdk-8u181-linux-x64.tar.gz
$ tar -xvf jdk-8u181-linux-x64.tar.gz
$ export JAVA_HOME=/home/ec2-user/jdk1.8.0_181
$ java -version

Follow for Gerrit.war

$ git clone --recursive https://gerrit.googlesource.com/gerrit
$ cd gerrit 
$ bazel build release

Follow for plugins such as its-jira

$ cd plugins
$ git clone https://gerrit.googlesource.com/plugins/its-jira
$ git clone https://gerrit.googlesource.com/plugins/its-base
$ bazel build plugins/its-jira

The output can be normally found in the following directory:

bazel-genfiles/plugins/its-jira/its-jira.jar

# Some plugins describe their build process in src/main/resources/Documentation/build.md file. It may worth checking.

# Some plugins cane be build using maven as well

Reference

• https://gerrit-review.googlesource.com/Documentation/dev-bazel.html
• https://gerrit.googlesource.com/gerrit/
• https://gerrit-review.googlesource.com/Documentation/cmd-plugin-install.html
• https://gerrit-review.googlesource.com/Documentation/dev-build-plugins.html

The post How to compile and build Gerrit Plugins? appeared first on scmGalaxy.

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. 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.

The post How to Install plug-ins in IBM UrbanCode Deploy appeared first on scmGalaxy.

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.

The post How to Install plug-ins in IBM UrbanCode Release appeared first on scmGalaxy.

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.

The post How to Install plug-ins in IBM UrbanCode Build appeared first on scmGalaxy.

Environment variables and properties defined in jenkins

Jenkins Set Environment Variables

When a Jenkins job executes, it sets some environment variables that you may use in your shell script, batch command, Ant script or Maven POM 1. The following table contains a list of all of these environment variables.

Promoted Build Plugin Environment Variables

If you are using the Promoted Build Plugin, you will have access to the following environment variables. This allows you to access information about your Jenkins build since certain environment variables stated above (such as BUILD_TAG now refer to the Promoted Build Plugin’s job.

System Properties

Environment Variables

Plugins

Useful Plugins

https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin

Reference

https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project
http://jenkins:8080/systemInfo

The post Environment variables and properties defined in jenkins | Jenkins Tutorial appeared first on scmGalaxy.

Reporting plugins
Plugins which generate reports, are configured as reports in the POM and run under the site generation
lifecycle.

This plugin consists of several reports that you can run selectively, individually or even run all of them. Please see below for instructions on how to configure your pom.xml to do this.

Run All Reports
To include all Project Info Reports in your project, you must configure your pom.xml. Use “mvn site:site” to generate the configured reports.

project
…

…
org.apache.maven.plugins
maven-project-info-reports-plugin
…

…

Run Selective Reports

…

…
org.apache.maven.plugins
maven-project-info-reports-plugin

dependencies
project-team
mailing-list
cim
issue-tracking
license
scm

…

…

Reporting plugins are configured in the POM as in this example:
…

org.apache.maven.plugins
maven-project-info-reports-plugin

…

Configuration in the reporting section also applies if plugin goals are invoked individually. The converse is not true– if you configure the plugin inside , that configuration will NOT apply to .

Configuring multiple reports for one plugin using . Each must have a unique . For more information on UMLGraph, see the UMLGraph site and this page.

…

org.apache.maven.plugins
maven-javadoc-plugin

uml

gr.spinellis.umlgraph.doclet.UmlGraph

gr.spinellis
UmlGraph
4.4

-views
target/uml
private

javadoc

html

private

javadoc

…

Known Plugins That Provide Reports

• Project-Info-Reports – Standard Reports
• Javadoc – Javadoc
• JXR – Source Cross-Reference
• Surefire-Report – Surefire Test Report
• Changes – Changes & JIRA Report
• Taglist – Taglist Report (For TODO, @deprecated, etc.)
• PMD – PMD Report for Source-code analysis

The post Reporting Plugins in Maven | Maven Plugins That Provide Reports appeared first on scmGalaxy.