summaryrefslogtreecommitdiffstats
path: root/jjb/armband
AgeCommit message (Collapse)AuthorFilesLines
2017-07-18Revert "armband-deploy.sh: Inherit env vars for sudo"Alexandru Avadanii1-1/+1
Using sudo triggers a chain of dependencies in our infrastructure, ranging from issues cleaning up the Jenkins workspace to deploy-time permission issues. As it turns out, cleaning all looses ends after that change is not a trivial task, and the remaining work outweights the benefits of using sudo in the first place. The original motivation for using sudo was a superposition of: - hardcoded check for running as root in Fuel's ci/deploy.sh; - the ability to install packages on the hosts via apt-get/yum; - the ability to spawn VMs using virt-manager; All of the above can be mitigated by imposing a series of restrictions for the Jenkins slave / jump server workstation and the jenkins user: - check for sudo rights instead of running as root user; - explicitly use sudo for package installation and/or system-level changes; - add jenkins user to "kvm" and "libvirtd" groups; So, revert using sudo when calling the deploy script, and limit sudo actions to package installation in Armband's deploy script. To compensate running as a regular user, a series of small changes is required in Armband project itself, together with the appropiate Jenkins slave user configuration on the machines running this script. This reverts commit 67d8bac7b2a97531ad465f275747b3dc455d4fe4. Change-Id: I88df6db1a43b93b7314ceca53d353f9000f15153 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-07-17armband-deploy.sh: Inherit env vars for sudoAlexandru Avadanii1-1/+1
Previous commit adding sudo for ci/deploy.sh call breaks Armband deploys, since ci/deploy.sh relies on $WORKSPACE env var being set. Change-Id: I948c8e3c00b430e0c186c0a727e1b7e027d7a089 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-07-17armband-deploy.sh: sudo ci/deploy.shAlexandru Avadanii1-1/+1
New MCP deploy scripts have a hard requirement on running as root. Bring back sudo for the `ci/deploy.sh` invocation, aligning with Fuel@OPNFV. NOTE: This can be later avoided/reverted if we can guarantee the "jenkins" user has sudo rights, even without a tty present. Change-Id: Ibec7b14e9174a7f482609890e5e68912931a8d05 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-07-11armband: Disable ISO actions for MCPAlexandru Avadanii4-8/+27
Sync with changes for Fuel@OPNFV targeting master branch (MCP): - disable ISO build for master branch; - turn off upload action & checkout; - add retrieving OS credentials for MCP; - disable ISO download for master branch; Change-Id: I11eacfad7ee1f738119e17c2e63c3d92707f8e1f Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-06-12Reschedule armband jobsCristina Pauna1-14/+14
Removed the master jobs until mcp is functional on arm. Rescheduled the danube jobs 8 hours apart. Change-Id: I90037a76a50d61c76c13cd68fa5926e1a73e88e6 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-05-21dovetail: conditional steps added to armpodMatthewLi1-14/+19
JIRA: DOVETAIL-432 1, only run against os-(nosdn-odl_l2)-(nofeature-bgpvpn)-ha scenario this can reduce the CI/pod time resource dovetail test cases by now (refstack, ha, ipv6, bgpvpn) 2, this has been tested on compass pod, and works well Change-Id: I1bcf8165d5fcc93c78b47cbd23e0c07f19b01189 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-04-26Rename arm-pod3-2 to arm-pod4Cristina Pauna2-20/+20
Arm-pod3-2 is a second jenkins slave for arm-pod3. This slave is arm while the old jenkins slave is x86. Fatih requested for this slave to be renamed to arm-pod4 instead of arm-pod3-2, even if it's a slave for an existing pod JIRA: ARMBAND-252 Change-Id: I5645edd7d774f763e5e72115851c7061bfafd344 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-04-21Merge "dovetail: Change CI jobs to run test suite "proposed_tests" instead ↵Jun Li1-1/+1
of "debug""
2017-04-19dovetail: Change CI jobs to run test suite "proposed_tests" instead of "debug"MatthewLi1-1/+1
JIRA: DOVETAIL-397 now, team decide to use proposed_tests suite instead of debug Change-Id: Iff8ec0b32a24e51bc2d2536605c9867b94f8921c Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-04-18Make arm-virtual1 pod not available for CI jobsAlexandru Nemes1-7/+80
Change-Id: I1ae47f2105744bfea8c8c589f41282d1c4ae2159 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
2017-03-29Set the jobs 4 hours apartCristina Pauna1-9/+9
A non-ci pod is made ci-pod for danube release, therefore this patch modifies the cron jobs to be 4 hours apart instead of 8 This commit should be merged after the lable of the pods are changed Request: OPNFV Helpdesk #39128 Change-Id: Ic88180d01d9ea03d03b79355cd78891ad612c59b Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-03-16Add jobs to use the aarch64 jenkins slaveCristina Pauna2-0/+78
arm-pod3-2 is an aarch64 jenkins slave for the same POD as the existing x86 jenkins slave arm-pod3. This commit adds jobs so we can deploy the POD and run functest from the aarch64 jenkins slave. These jobs are non-ci JIRA: ARMBAND-241 Change-Id: Ie3b808a641e44649c02f3b75c83d79119217fdfe Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-03-15jjb: Set disable-strict-forbidden-file-verification to 'true'Markos Chandras1-0/+1
Previously, if an upstream patchset contained a change for a file listed in 'forbidden-file-paths' the job would not be triggered. This is not desirable since such a patchset may contain important changes so we enable the 'disable-strict-forbidden-file-verification' option which triggers the job unless the patchset only contains changes for the files listed in 'forbidden-file-paths'. Note: The diff was generated using the following script: for i in $(grep -l -r forbidden-file-paths *);do sed -i "s/\(^.*\)forbidden-file-paths/\1disable-strict-forbidden-file-verification: \'true\'\n&/" $i; done Please double check that the changes look sensible for each team's project. Change-Id: Ifa86d3a39b36375b2fd52b449e29c8dc757499b4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-03-15Modify triggers for armband danube jobsCristina Pauna1-12/+12
This commit rebalances the nr of runs between master and danube branch for CI jobs JIRA: ARMBAND-238 Change-Id: I541ddf3974680096d503829b279cb26ab76577bc Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-03-14Enable Danube JobsAric Gardner2-2/+2
Here are the projects that were branched: I will double check against this list that these changes make sense and that no one is missing as I go forward. wiki page of participating projects, and their jobs: https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube apex - already enabled armband - done availability - already enabled barometer - done bottlenecks - already enabled compass4nfv - done copper - already enabled daisy - (not participating -- keep jobs disabled?) doctor - already enabled domino - already enabled fds - N/A fuel - done functest - already enabled ipv6 - already enabled joid - done kvmfornfv - already enabled models - already enabled multisite - done netready - NOT DONE opera - NOT DONE opnfvdocs - done orchestra - Not participating onosfw - done ovsnfv - done parser - N/A promise - already enabled qtip - already enabled sdnvpn - N/A snaps - done securityscanning - N/A sfc - N/A storperf - done ves - already enabled vswitchperf - already enabled yardstick - already enabled Change-Id: I803662faf05c8554cfe7fa5f85da9521f72b03ff Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2017-02-08Update new slave tagCristina Pauna2-6/+6
The jenkins slave arm-build2 was retagged from opnfv-build-arm to opnfv-build-enea. This change was made to avoid confusion, as this slave is an x86 machine building an iso that is used by armband Change-Id: Iac4e9bf635c128070c32818874626a81a28e6cf7 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-02-04armband: Fix log collection by not setting errexitAlexandru Avadanii1-1/+0
Fuel and Armband deploy scripts trap internal errors and call exit in the trap handler, so the releng wrapper exists before collecting all deploy logs when shell option "errexit" is set. JIRA: ARMBAND-217 Change-Id: Icb1e3277c3e137abb3225a2b9a0b4269eaf08fc6 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-02-01merge GIT_BRANCH and GERRIT_BRANCH into BRANCHRyota MIBU6-13/+10
GIT_BRANCH parameter is different; master or stable/danube in daily jobs, but 'refs/changes/57/27657/6' in verify jobs. This breaks some job builders triggered by the both types of jobs. We have GERRIT_BRANCH parameter for verify jobs to identify stream and expected branch into the patch will be merged after it got +2 and submitted. To avoid further confusion and to have common job builders for daily and verify jobs, this patch introduce BRANCH parameter. GERRIT_BRANCH is now deprecated. Change-Id: Ibcd42c1cd8a0be0f330878b21d3011f1ec97043b Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-01-24Armband: Add sha256 hash for artifact ISOAlexandru Avadanii1-0/+1
JIRA: ARMBAND-208 Change-Id: I96cb3479d17fa5d16e02e65c81c65e7fbdf120df Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-01-20[macro] property logrotateRyota MIBU3-0/+5
This patch defines 'logrotate-default' property and replace 'logrotate' by it, as 'logrotate' is deprecated on jenkins>=1.637 . Change-Id: I900975e5b3f590bb7a4d430e2f623931ae782bf4 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-01-17Merge "Remove colorado jobs and create danube jobs"Fatih Degirmenci3-42/+50
2017-01-09Remove colorado jobs and create danube jobsFatih Degirmenci3-42/+50
Danube stream for the projects with daily jobs is disabled. Danube stream for the projects without daily jobs is left as enabled as there will be no changes coming to danube branch until branch is created. Dovetail, Apex and Fuel jobs have not been updated yet. Change-Id: Ice39826c8f829157fa864370557837290838f634 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-12-21Rebalance master vs. colorado scenario triggerscristinapauna1-10/+10
JIRA: ARMBAND-181 With Colorado release out, we need more jobs on master branch than on colorado branch Change-Id: Ic068a121567381ecfb527599ec2af530c1a8e93e Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-12-19fix ci jobs (daily && no branch param)Ryota MIBU2-0/+4
Change-Id: Iad856adf625a56c2f5c366fb414746d1e9e16691 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-12-19clean scm defenitionsRyota MIBU3-22/+6
This patch makes sure we use 2 types of scm, and allows us to specify them by adding one line in job-templates. - git-scm # for daily jobs and merge jobs - git-scm-gerrit # for verify jobs [New] Change-Id: Iddc8a5e0e115193c7081a6d6c53da209900e95c8 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-12-08dovetail/arm: ci loop job added to debug code bugsMatthewLi1-0/+17
JIRA: DOVETAIL-153 1.based on https://gerrit.opnfv.org/gerrit/#/c/25681/, however, this has to be triggered manually, not convinient for debugging, and may affect daily ci loops 2.not used for release criteria or compliance, only to debug the dovetail tool bugs with arm pods Change-Id: Ide35f50129f30f4c8d7b7f50d52f9fa1d35cac69 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-12-01Restrict Gerrit Triggers to OPNFV Gerrit ServerTrevor Bramwell1-0/+1
With the addition of ODL and OpenStack Gerrit servers, it's important we don't generate additional noise by accidentally building against these Gerrit servers when we don't intend to. JIRA: RELENG-179 Change-Id: Ia163c6c3eaa58e8e21dc6548a839062fcbde39ed Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2016-11-30armband: Enable deploy-cacheAlexandru Avadanii1-1/+14
This enables the mechanism added in [1]. Armband just added support for caching deploy artifacts, like bootstraps and target images, which take a lot of time at each deploy to be built, considering it requires a cross-debootstrap via qemu-user-static and binfmt. For easier setup, the deploy cache depends on the local ISO storage mechanism (/iso_mount/opnfv_ci), and reuses the same storage pool. To enable deploy caching, just create the deploy-cache directory at: /iso_mount/opnfv_ci/<branch>/deploy-cache JIRA: ARMBAND-172 [1] https://gerrit.opnfv.org/gerrit/#/c/25191 Change-Id: I161205a87f13cd78e79b96bfc37a5f68aba093cc Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-11-27Add jobs for ARM virtual PODcristinapauna2-7/+11
Pod virtual1 was added in the ENEA-ARM lab This commit adds the jobs for it JIRA: ARMBAND-162 Change-Id: Icaa798691f5ff60a58ae083eb1c366170c464b92 Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-11-02Armband: Verify: Removed upstream folder from forbidden file pathsAndrei Varvara1-2/+0
"forbidden-file-paths" prevents verify from running for patches that alter that dir so it was necessary to remove "upstream" ANT configuration completely Change-Id: I6c1f00fe500548695284ad1e947cb35bdce14c3e Signed-off-by: Andrei Varvara <andrei.varvara@enea.com>
2016-11-01Armband: Verify: Fix build params, tree pathsAlexandru Avadanii1-4/+4
Armband tree has ci, patches and upstream as folders. Updated the releng armband-verify-jobs.yml with the right paths. While replicating Fuel@OPNFV behavior, one default set of parameters was left pointing to x86 build defaults (opnfv-build-defaults), instead of opnfv-build-arm-defaults. JIRA: ARMBAND-99 Change-Id: I4a0ec09b6188ef4c7f06d2f0c0ddcb13ca9ad72f Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> Signed-off-by: Andrei Varvara <andrei.varvara@enea.com>
2016-10-31Armband: Verify: Don't enable virtual-deploy yetAlexandru Avadanii2-8/+5
While at it, add missing exec flag to one sh script, and cleanup some obsolete debug logs. Change-Id: Ib805e41177571f6413ed744edae405449c86412e Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-10-31Merge "Add verify jobs for Armband"Aric Gardner3-43/+283
2016-10-24Add verify jobs for ArmbandAndrei Varvara3-43/+283
This patch is similar to what releng/jjb/fuel does for verifying build and deploy. JIRA: ARMBAND-99 Change-Id: Ic6524e921acf458b55fbbb3453638c5fc30db15c Signed-off-by: Andrei Varvara <andrei.varvara@enea.com>
2016-10-18Set arm-pod-3 as non-ci PODcristinapauna1-0/+70
arm-pod-3 will be removed as CI pod and this commit add triggers to make it a non-ci pod Change-Id: Ice16b8d32c553a059a2c9885fd801a736a59a14d Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-10-14Merge "Armband: Move lab-config to OPNFV securedlab"Aric Gardner1-1/+1
2016-10-14Add sfc scenarios on ARMcristinapauna1-2/+55
Added old l2 sfc scenarios for both ha and noha on master branch JIRA: ARMBAND-144 Change-Id: Ie28f9f9b32abe82b9f596d5b7d6336e2df425eb4 Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-10-14Armband: Move lab-config to OPNFV securedlabAlexandru Avadanii1-1/+1
This depends on: - jenkins-enea ssh access to OPNFV gerrit; - master and stable/colorado securedlab definitions for arm-pod* [1]; [1] https://gerrit.opnfv.org/gerrit/#/c/23159/ JIRA: ARMBAND-149 Change-Id: Ic9a2e232027636694ffd441fe5203cb06975f137 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-10-12fuel, armband: build, deploy: export TERM="vt220"Alexandru Avadanii2-0/+4
Since we do not actually parse our build/deploy logs for color chars, set the terminal to "vt220". This will silence quite a few of colorization special identifiers, but NOT all of them (e.g. `tput sgr0` still prints a sequence). For Fuel@OPNFV build process, we also need to workaround docker terminal settings not being passed down when using a tty (see [1]), which will be fixed in Docker 1.13+. This fix is handled in [2]. [1] https://github.com/docker/docker/issues/9299 [2] https://gerrit.opnfv.org/gerrit/#/c/22883/ Change-Id: I5f0c6eae33349ef81b67dd17e6df4e0af6274fab Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-10-10Fix the jenkins jobscristinapauna1-5/+5
Some of the jobs were programmed at the same time This fix sets the jobs 8 hours apart Change-Id: I13463b8a00df67519e2e2b8e333b4c625f1e9d8b Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-10-05Set the jobs 8 hours apartcristinapauna1-9/+9
Modified the cron jobs to be 8 hours apart instead of 4 Change-Id: I670811901c7403f81812b1d51cdbaf46904e878c Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-09-19armband: new job schedulePaul Vaduva1-10/+10
Change-Id: I1d5dca9f7cc2c54e90af454a503e77486be361ef Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-09armband: deploy: upload logs to GSAlexandru Avadanii1-2/+23
Closes-bug: ARMBAND-72 Change-Id: I6c5a3e6ce4c320bf42f02b290a0137f5b892ad7f Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-09-08armband: enable concurrency and adjust throttle paramsPaul Vaduva1-3/+3
Change-Id: I72e061ae57ccdd06520dbf93cdf146390bfc0591 Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-07armband: fix job naming issuePaul Vaduva1-47/+47
We were refering jobs in other projects (mainly fuel) because the ci pods were named jost baremetal and virtual Change-Id: I9d02e2e61fe666f4ef46c1eb62f41da065e46059 Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-07Merge "armband: Deploy triggers yardstick tests for CI pods."Fatih Degirmenci1-0/+11
2016-09-07armband: Deploy triggers yardstick tests for CI pods.Paul Vaduva1-0/+11
Change-Id: I8b011aafd333c78eaeed59040476b1325e2dc56c Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-06armband: triggers modified to run twice a day each branchPaul Vaduva1-10/+10
Change-Id: I7fcd24852a0d1aecdfacf5f3cb1dfd49fb711916 Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-05armband: Fix file handler in lab-config test -eAlexandru Avadanii1-1/+1
Previous change adding lab-config/.../local_env support introduced an issue, in the form of `test -e file:///path/to/local_env`, which is not supported. Change-Id: I1566b41765329f18523cfc506c9112b6694a8317 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-09-01armband: Fix default params for labeled podsAlexandru Avadanii2-3/+10
After previous change introducing the usage of node labels for Armband CI deploy jobs, we discovered that the old params were not applied to labeled pods. To complicate things, we had different DEFAULT_BRIDGE params for each CI pod, which contradicts the Jenkins templating paradigm. Since we already have a mechanism in place for overriding env vars based on the POD we are running against, move both <DEPLOY_TIMEOUT> and <DEFAULT_BRIDGE> params to our local_env, which is sourced by the deploy script and can apply POD specific configuration. Add missing LAB_CONFIG_URL to newly added baremetal and virtual defaults for Armband. While at it, also replace "brahmaputra" comments with "colorado". v2 -> v3: Source local_env before using DEFAULT_BRIDGE in <armband-deploy.sh>. Previously, we (Armband) sourced this file in our <ci/deploy.sh> [1], which will be dropped after this change is merged. [1] https://git.opnfv.org/cgit/armband/tree/ci/deploy.sh#n24 Change-Id: Ibafea25b3df8c3118ce05e3f40934c8e8b9c8dcd Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>