Differences

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

--- octopus:infrastructure [2015/02/13 17:53]
Fatih Degirmenci Added list of CI tools/resources, tasks to enable basic CI functionality and plugins to install.
+++ octopus:infrastructure [2015/02/17 16:21] (current)
Fatih Degirmenci [Jenkins Job Builder]
@@ Line 46: / Line 46: @@
 | Configure Jenkins master/apply configuration to Jenkins Global Configuration| High | LF | Whatever is necessary.|
 | Create domains | Medium | LF | Whatever is necessary.|
-| Install Jenkins Plugins and configure them | High | LF | Please see below for initial list of plugins.|
+| Install Jenkins Plugins and configure them | High | LF | Please see below or [[https://wiki.opnfv.org/octopus/infrastructure#list_of_plugins_to_install|click here]] for initial list of plugins.|
 | Connect Jenkins to Gerrit        | High    | LF   | Need to be able to trigger jobs on Gerrit events. \\ Please see [[https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-AdministrativeSettings|here.]] |
 | Connect/configure slaves         | High    | LF   | Can/will start with echoing "Hello World!" by jobs running on master. \\ And then connect/use community(Ericsson/Intel BGS) hosting until LF resources are ready.|
@@ Line 68: / Line 68: @@
 ^ Summary                          ^ Priority    ^ Responsible  ^ Notes ^
 | Agree on if we need artifact repository or not | High        | Octopus Team/OPNFV Community| SSH keys etc. setup on Gerrit. \\ Also it should be granted to Gerrit stream events. \\ Please see [[https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-Gerritaccessrights|here]].  |
-| Decide which artifact repository to use with the guidance from LF | High | Octopus Team/LF/OPNFV Community| Swift/Artifactory/REST |
+| Decide which artifact repository to use with the guidance from LF | High | Octopus Team/LF/OPNFV Community| Swift/Artifactory/Nexus|
 | Guide OPNFV Community regarding artifact repository selection | High | LF| Given that LF already hosts repositories for other OSS projects. |
 | Decide and create repositories | Medium | Octopus Team/LF| We can start with "a" repo and evolve later on. |
 | Decide retention policy | Medium | Octopus Team/LF| If storage becomes the bottleneck, we may need to start cleaning up based on the policy. |
-| Acquire/provide storage if existing storage has potential to be bottleneck | Low | OPNFV Management | This needs to be evaluated while we move on and raised by the community.  |
+| Acquire/provide storage if storage becomes the bottleneck even after enforcing the the retention policy | Low | OPNFV Management | This needs to be evaluated while we move on and raised by the community.  |
 ===== Hardware Resources =====
@@ Line 81: / Line 81: @@
 | Assist Ericsson/Intel OPNFV Contributors to securely connect hosting to Jenkins | High        | LF| This requires discussions.  |
 | Configure/connect LF resources | High        | LF/Octopus Team| N/A  |
+====== Jenkins Job Builder ======
+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 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.
+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.
+Here are some links
+  * Jenkins Job Builder: http://ci.openstack.org/jenkins-job-builder/
+  * How OpenDaylight uses Jenkins: https://wiki.opendaylight.org/view/RelEng:Jenkins
+  * OpenDaylight Builder: https://jenkins.opendaylight.org/releng/view/builder/
+  * OpenDaylight Build/Release jobs on Jenkins: https://jenkins.opendaylight.org/releng/
 ====== List of Plugins to Install ======
-This is initial list of plugins to install and new ones will probably be added based on Octopus/Community feedback/needs.
+This is the initial list of plugins to install and new ones will probably be added based on Octopus/Community feedback/needs.
 The ones that are marked as low priority can be skipped for the timebeing to see/evaluate the load on Jenkins master when other plugins are installed. If the load looks fine, they can be installed as well.
@@ Line 122: / Line 140: @@
 |Delivery Pipeline Plugin| Visualize delivery pipeline| LF |Low | [[https://wiki.jenkins-ci.org/display/JENKINS/Delivery+Pipeline+Plugin|Delivery Pipeline Plugin]]|
 |Robot Framework Plugin| Publishes/stores Robot FW test reports| LF |High |[[https://wiki.jenkins-ci.org/display/JENKINS/Robot+Framework+Plugin|Robot Framework plugin]]|

Wiki

User Tools

Site Tools

Differences

Page Tools