Page tree
Skip to end of metadata
Go to start of metadata

Fuel in OPNFV CI

Please note that the most of the information on this page is valid for most of the OPNFV Projects. The information will be documented properly once CI setup of all the projects (installer projects mainly) are aligned.

Fuel Jobs in OPNFV CI

Daily Jobs

Purpose

Fuel currently has two daily jobs running against master branch. (after branch off, LF POD2 will switch to stable branch.) The purpose of these jobs is to do Fuel builds, deployments on bare metal, functest and yardstick.

These jobs are triggered once a day during the night.

The daily build jobs do not vote on Gerrit and do not send comments there.

Current daily jobs are

Please note that the daily build jobs for brahmaputra branch have not been created due to not having the branch yet.

The build job uploads the ISO to OPNFV Artifact Repo and the ISOs are named opnfv-<timestamp>.iso.

Retriggering Jobs

The only way to trigger daily build jobs is to login to Jenkins and click Build with Parameters. Fuel committers should be able to do this. If not, please open a ticket to OPNFV Helpdesk and contact Aric.

Starting Full Run

  1. You can start full run which executes build, deploy, functest, and yardstick.
  2. Login to Jenkins using this link if you are not logged in already.
  3. Click this link to open the daily job.
  4. Click Build with Parameters link from the links on the upper left side.
  5. The parameters SDN_CONTROLLER, OPNFV_FEATURE, and DEPLOY_SCENARIO are for you to change. So please change them as you will. But please note that these parameters don't mean/change anything if the corresponding functionality is not implemented in any of the jobs; build, deploy, or testing.
  6. Click Build button.
  7. After you clicked the button, the first job, build, will start running and will check if new ISO build is needed. If needed, it will build a new ISO, upload it and end. The next job is the deploy job, which will download the latest ISO and do the deployment on the POD. Test jobs will then run if the deployment is successful.
  8. You can see full console log of the latest main job from this link and navigate to other jobs by clicking links on this log.

Starting Deployment Only

  1. You can skip build and test jobs and directly start the deployment using the latest built ISO.
  2. Login to Jenkins using this link if you are not logged in already.
  3. Click this link to open the deploy job.
  4. Click Build with Parameters link from the links on the upper left side.
  5. The parameters SDN_CONTROLLER, OPNFV_FEATURE, and DEPLOY_SCENARIO are for you to change. So please change them as you will. But please note that these parameters don't mean/change anything if the corresponding functionality is not implemented in any of the jobs; build, deploy, or testing.
  6. Click Build button.
  7. After you clicked the button, the deploy job will start running. It will download the latest ISO and do the deployment on the POD.
  8. You can see full console log of the latest main job from this link.

Notes

  • Only 1 full run or deploy job can be run at any time on same POD.
  • Please always check if anyone working on the POD before starting new run.

Verify Jobs

Purpose

Fuel has one verify job per branch like all the other OPNFV Projects. The purpose of these jobs is to do a simple sanity check on the change by running Fuel build.

This job gets triggered by Gerrit when a new change/patch comes into Gerrit for Fuel repo and tries to build the patch and

  • if the build succeeds, the change on Gerrit gets voted by Jenkins with Verified +1.
  • if the build fails, the change on Gerrit gets voted by Jenkins with Verified -1.

The change can not be submitted while it has Verified -1 even if there is a +2.

Current verify jobs are

This job does not upload ISO to OPNFV Artifact Repo.

Please note that the verify job for brahmaputra branch has not been created due to not having the branch yet.

Retriggering Jobs

If the job fails due to environmental issues, it can be retriggered by adding a comment to change on Gerrit. The comment must contain either one of the keywords reverify or recheck.

Force Submit

In rare cases it might be needed to submit a change forcefully even though the change got Verified -1 from Jenkins

In this case, the Verified -1 vote can be removed by retriggering the job as explained above to remove the Verified vote. While to verify job is still running, committers can put +2 and Verified +1 there and click the submit button.

But it is not advised to do this!

Merge Jobs

Purpose

Fuel has two merge jobs per branch. The purpose of these jobs is to do Fuel build and virtual deployment on the branch they're configured for right after the change is submitted provide feedback.

These jobs get triggered by Gerrit when a change is submitted to corresponding branch on Gerrit.

The merge jobs do not vote on Gerrit but send comments there, stating the result of build and virtual deployments.

Current merge jobs are

Please note that the merge jobs for brahmaputra branch have not been created due to not having the branch yet.

The build job uploads the ISO to OPNFV Artifact Repo for virtual deployment purposes and removed afterwards if the virtual deployment is successful. The uploaded ISOs are named opnfv-gerrit-<gerrit_change_id>.iso.

Retriggering Jobs

If the job fails due to environmental issues, it can be retriggered by adding a comment to change on Gerrit. The comment must contain the keyword remerge.

  • No labels