dipanjans / openshiftio-cico-jobs Goto Github PK

In the devtools-ci-index.yaml file, we can find the definition of all the existing CI jobs for the project devtools. These job definitions are composed of several attributes whose purpose is explained in the following:

• git_organization: represents the name of the github organization from which to build, test and/or deploy an executable from a repository.

• git_repo: specifies the name of the github repository inside an organization.

• branch: this optional value identifies the name of the branch that will be taken into consideration in the build process.

• ci_project: specifies the name of the CI project. This value is used for scheduling to use CI resources assigned per project.

• ci_cmd: contains the command that will be triggered by the job inside the repository, e.g. /bin/bash cico_build_deploy.sh. This command usually runs a bash script named cico_build_deploy.sh where we can find all the logic.

• svc_name: identifies the name of the Openshift service that will be redeployed.

• timeout: specifies a maximum time to complete the execution of this job.

• <TEMPLATE_NAME>: this name corresponds with the name assigned to one of the available job templates.

A real example is described below:

This job definition is based on our pre-defined model for the communication between Github repositories and our Jenkins infrastructure. More information about This procedure can be found in https://wiki.centos.org/QaWiki/CI/GithubIntegration.

You need to install python-pip and then use pip to install the jenkins-job-builder tool.

To test your job definition, you have to run the following command: