User Tools

Site Tools


fuel_opnfv:ci

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
fuel_opnfv:ci [2015/12/22 15:07]
Fatih Degirmenci created
fuel_opnfv:ci [2015/12/22 20:53] (current)
Fatih Degirmenci
Line 4: Line 4:
  
 ====== Fuel Jobs in OPNFV CI ====== ====== 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
 +  * branch: master
 +    * [[https://​build.opnfv.org/​ci/​job/​fuel-nosdn-opnfv-jump-2-daily-master/​ | Fuel Daily on LF POD2]], triggered 02:00UTC.
 +    * [[https://​build.opnfv.org/​ci/​view/​fuel/​job/​fuel-nosdn-ericsson-pod2-daily-master/​ | Fuel Daily on Ericsson POD2]], triggered 03:00UTC.
 +
 +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 [[http://​artifacts.opnfv.org/​ | 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**
 +  - You can start full run which executes build, deploy, functest, and yardstick.
 +  - Login to Jenkins using [[https://​build.opnfv.org/​ci/​login?​from=%2Fci%2F | this link]] if you are not logged in already.
 +  - Click [[https://​build.opnfv.org/​ci/​job/​fuel-nosdn-opnfv-jump-2-daily-master/​ | this link]] to open the daily job.
 +  - Click [[https://​build.opnfv.org/​ci/​job/​fuel-nosdn-opnfv-jump-2-daily-master/​build?​delay=0sec | Build with Parameters]] link from the links on the upper left side.
 +  - 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.
 +  - Click Build button.
 +  - 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.
 +  - You can see full console log of the latest main job from [[
 +https://​build.opnfv.org/​ci/​job/​fuel-nosdn-ericsson-pod2-daily-master/​lastBuild/​consoleFull| this link]] and navigate to other jobs by clicking links on this log.
 +
 +**Starting Deployment Only**
 +  - You can skip build and test jobs and directly start the deployment using the latest built ISO.
 +  - Login to Jenkins using [[https://​build.opnfv.org/​ci/​login?​from=%2Fci%2F | this link]] if you are not logged in already.
 +  - Click [[https://​build.opnfv.org/​ci/​job/​fuel-deploy-ericsson-pod2-daily-master/​ | this link]] to open the deploy job.
 +  - Click [[https://​build.opnfv.org/​ci/​job/​fuel-deploy-ericsson-pod2-daily-master/​build?​delay=0sec | Build with Parameters]] link from the links on the upper left side.
 +  - 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.
 +  - Click Build button.
 +  - After you clicked the button, the deploy job will start running. It will download the latest ISO and do the deployment on the POD.
 +  - You can see full console log of the latest main job from [[
 +https://​build.opnfv.org/​ci/​job/​fuel-deploy-ericsson-pod2-daily-master/​lastBuild/​consoleFull| 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 ===== ===== Verify Jobs =====
Line 59: Line 109:
  
 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**. 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**.
- 
-===== Build Jobs ===== 
- 
-==== Purpose ==== 
- 
-Fuel has one daily build job per branch. The purpose of these jobs is to do Fuel builds on the branch they'​re configured for.  
- 
-These jobs periodically poll Fuel repo every 6 hours to check if there is a new commit in the repo. If the job finds a new commit, it gets triggered, building the latest ISO. 
- 
-The daily build jobs do not vote on Gerrit and do not send comments there. 
- 
-Current daily build jobs are 
-  * branch: master 
-    * [[https://​build.opnfv.org/​ci/​job/​fuel-build-daily-master/​ | fuel-build-daily-master]] 
- 
-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 [[http://​artifacts.opnfv.org/​ | OPNFV Artifact Repo]] and the ISOs are named opnfv-<​timestamp>​.iso. 
- 
-===== Deployment and Test Jobs ===== 
- 
fuel_opnfv/ci.1450796855.txt.gz · Last modified: 2015/12/22 15:07 by Fatih Degirmenci