User Tools

Site Tools


octopus:infrastructure

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
octopus:infrastructure [2015/02/17 16:19]
Fatih Degirmenci
octopus:infrastructure [2015/02/17 16:21] (current)
Fatih Degirmenci [Jenkins Job Builder]
Line 86: Line 86:
 During Octopus Team Meeting on 2015-02-16, it has been suggested to give a try and perhaps use [[http://​ci.openstack.org/​jenkins-job-builder/​|OpenStack Jenkins Job Builder]] for OPNFV CI.  During Octopus Team Meeting on 2015-02-16, it has been suggested to give a try and perhaps use [[http://​ci.openstack.org/​jenkins-job-builder/​|OpenStack Jenkins Job Builder]] for OPNFV CI. 
  
-OpenDaylight also uses Jenkins Job Builder for Jenkins Jobs so this looks is a common way of handling Jenkins related things. As OPNFV uses OpenStack and OpenDaylight as upstream projects for the components themselves, using/doing CI in a similar way is also logical.+OpenDaylight also uses Jenkins Job Builder for Jenkins Jobs so this is a common way of handling Jenkins related things. As OPNFV uses OpenStack and OpenDaylight as upstream projects for the components themselves, using/doing CI in a similar way is also logical.
  
 As a first step, LF will help us setting up some simple jobs using Jenkins Job Builder and they will be put in Octopus repo on OPNFV Gerrit. Then we will continue with the rest of the evaluation but this looks quite promising as the things stand. As a first step, LF will help us setting up some simple jobs using Jenkins Job Builder and they will be put in Octopus repo on OPNFV Gerrit. Then we will continue with the rest of the evaluation but this looks quite promising as the things stand.
  
-Jenkins Job Builder helps us to develop ​and maintain Jenkins ​jobs as the source code; changes to jobs go through regular Gerrit review process and makes things visible to greater OPNFV Community. Having job configurations version controlled has its own benefits which is not needed to be listed here. Deploying those jobs could also be automated.+Jenkins Job Builder helps us to develop/maintain/​handle ​Jenkins ​job configurations like the source code; changes to jobs go through regular Gerrit review process and makes things visible to greater OPNFV Community. Having job configurations version controlled has its own benefits which is not needed to be listed here. Deploying those jobs could also be automated.
  
 Apart from all the good things listed in previous sentence, it also relieves us from creating/​modifying/​maintaining Jenkins jobs from Jenkins GUI, potentially reducing chance of mistakes and annoyance of clicking things around. Apart from all the good things listed in previous sentence, it also relieves us from creating/​modifying/​maintaining Jenkins jobs from Jenkins GUI, potentially reducing chance of mistakes and annoyance of clicking things around.
octopus/infrastructure.1424189957.txt.gz ยท Last modified: 2015/02/17 16:19 by Fatih Degirmenci