Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Id3c1c2e52b8506a312391ba028bdabb36e281145
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I5f811a0db6c1725e02b3bfd51d8c7c21b12633a2
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This patch proposes below changes:
- Run CI on intel-pod5 against stable/brahmaputra branch
- Run CI on intel-pod6 against master branch
- Configure functest against both branches on both PODs
- Enable yardstick against both branches on both PODs
- Comment out additional controllers until Arno scenario is verified
- Rename OPNFV_FEATURE to DEPLOY_SCENARIO
Please note that there are some duplications which need to be taken
care of in a separate patch.
Change-Id: Ic3deb77692cdb0908808fdb21098af77b937b831
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Replace default stream definitions with stream anchors in order
to be able to specify which job on which POD runs against which
branch.
Move project specific verify job to its own file to ease the stream
handling.
Enable automatic runs on Intel POD5.
Change-Id: Ic7c1137cb2d25604fbef6d31b5db5215e9d92304
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I1d14832cac2867ca9d9b64608bfe3231c316f2d5
Signed-off-by: David Blaisonneau <david.blaisonneau@orange.com>
|
|
Change-Id: Ibd17c68ac472d0a21cd2f2d46f4653e80c079102
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I8406026ba671820c386ebfbff1338f23610912f9
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Multijob project type has some advantages over the Freestyle project. [1]
- Jobs in same phase run in parallel.
- Jobs in another phase need to wait completion of jobs in earlier phase.
- Ability to create phases where different jobs can be run in parallel
so a deploy phase can contain virtual and bare metal deployment jobs
where both are running in parallel.
- Ability to determine what should be done when a job fails
- Ability to automatically abort other jobswhen a job is aborted. [2]
- Expose parameters from main job to jobs executed by it.
(If a parameter is defined in sub job, it won't be overriden.
That's why SDN_CONTROLLER and OPNFV_FEATURE parameters are not defined
in sub jobs.)
- See full CI pipeline by just clicking the main job.
- Access the console logs of sub jobs from main job.
See example job from link [3].
Other important aspects of this change are
- One main job per installer, SDN controller and POD created. The purpose
of the main job is to ease the scheduling and troubleshooting. The actual
stuff is done by subjobs.
- Use same build, deploy, and test jobs for an installer and POD for running
different combinations. The installer and test project scripts should do
what needs to be done by determining the combination using SDN_CONTROLLER
OPNFV_FEATURE env variables.
- Create and enable main installer jobs with supported SDN controllers by
the specific installer which will automatically be triggered.
- The change requires us to increase no of executors per pod jumphost/slave
by one since main and subjobs get executed on same slave due to passing
parameters from main job to subjobs.
- Enabling additional OPNFV features can be done by using Build with Parameters
manually and changing the OPNFV_FEATURE parameter before clicking the Build
button.
- Use common naming scheme for jobs:
Installer main jobs: [installer]-[controller]-[pod]-daily-[stream]
Installer sub jobs: [installer]-[activity]-[pod]-daily-[stream]
Test jobs: [test_project]-[installer]-[pod]-daily-[stream]
[1] Details of Multijob Plugin is available on below link.
https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin
[2] Available once the patch below gets merged.
https://review.openstack.org/#/c/257948/
[3] Example main job showing subjobs.
https://build.opnfv.org/ci/job/installer-controller-pod-daily-master/
Change-Id: Ie6ce2aaa7117583bc71e5153748a8e32f7d00351
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
default location and add joid_config folder creation"
|
|
location and add joid_config folder creation
Change-Id: I7f816915e14929cb62aa1ea893272154da0f1442
Signed-off-by: David Blaisonneau <david.blaisonneau@orange.com>
|
|
All the jobs should use INSTALLER_TYPE
Change-Id: I5386276fca837ba3ddda314f7c334c0f2957f78a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I09b3d06b2b2b615b3fbae5e422820356b465d895
Signed-off-by: David Blaisonneau <david.blaisonneau@orange.com>
|
|
Change-Id: Icbb7f50652f22bbca2835afd47669ab21fd99bf4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Icb776a50e50af8ccd8d8419430d4e36798b29901
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I128098d404a72711672026d4fc7b55fbd4f3b9bf
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Example jobs updated to match the slave/pod names.
Change-Id: I662a1710f75009efd94cdad61e7fe97139aa64e8
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Id6396ab32f0d939b74f18abe4750b06638a90c50
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Also set default value of controller to ODL.
Change-Id: I14e6619a15f815bb5ce8d6604061990c41060805
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Id0c23c86c2144316d0067266df6f768d9bcaed15
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change proposes
- Move installer params to common file
- Move pod params to common file
- Configure POD slaves in pod file and set slave to run using node label plugin
- Create one daily parent job per installer per controller
- Create common deploy job, taking controller name from parent job
- Change build display name to show installer + controller name
Please note that this is an example and things will evolve based on
how things work.
Change-Id: I4bc1d35e43c44d9401f4000090818e8e7b426e70
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|