Age | Commit message (Collapse) | Author | Files | Lines |
|
With the refactor of snapshot pipeline to include other snapshots, the
path had changed to be generic for where temporary snapshot files are
stored (from /tmp/csit to /tmp/snap). See this commit:
https://gerrit.opnfv.org/gerrit/#/c/65157/4/jjb/apex/apex-fetch-snap-info.sh
This patch fixes the path for triggering CSIT job.
Change-Id: I63308d73c13e8c714078a38bc6cf9bb75cbeec5c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This reverts commit fca796f895e8c3e00fb4f7b7f0bfa2e366627db0.
Change-Id: I5e96ae38519865dfb42c4134c09f5eb4be275225
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
It replaces blocking-level by block-level [1].
https://docs.openstack.org/infra/jenkins-job-builder/properties.html
Change-Id: I304ab122de3699401d2be92955e151e774206c07
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Var checks for unset required proper parameter expansion to avoid
nounset.
Change-Id: Ide5db47e2243c8aee0f97369bf3cd0673e7f4bd3
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
When we run deployments for snapshot creation we typically pass in the
OS_VERSION var so we know what openstack version we are deploying with.
However when we run a verify/gate job to ensure that the snapshot
deploys work we do not have this variable, and need to detect it based
on the OPNFV branch, or if the branch is master, the deploy scenario
naming scheme.
Change-Id: If1445dc564d2af59b9740391de56b821b78de0b5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This patch changes snapshot related scripts to allow for more than just
the current snapshot type of "csit". This allows us to add other
snapshot types, including the functest type. The same
snapshot.properties file will be used to store information for all types
of snapshots. The snap cache folder structure will remain the same, but
hold different types of snapshots in the same folders.
These changes include renaming the URLs for the snapshot artifacts to
reflect the snapshot type, but remains backwards compatible until enough
promotions have occurred and other apex snapshot deployment scripts have
been migrated to the new format.
Change-Id: If3e47e700b5ad9c95418179042b85814fe389233
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Enable Gambia read the docs stream for all projects that have
a gambia branch
Also added edgecloud rtd job as it was missing
Change-Id: I64d159cde0200871cd4ba3d2c071853c9bd502c1
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Fixes passing quotes as the value for the variable, so now what is
passed is just an empty string.
Change-Id: I9abb681374934fe4cf7c8024118278674880f7e9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Both flex PODs have been offline for a while. Disabling the Apex jobs
scheduled on them will reduce the queue and they can be re-enabled once
they come back online.
Change-Id: I2f82379225ae6fc728fc655680e5ee8799a4bbbb
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
When using 'shell' builder directly '{}' is interpreted as a JJB
substitution. This can be escaped with '{{}}' but breaks due to Apex
use of Jinja2. Moving the entire script to a shell fixes this issue.
Change-Id: I874a45cf25ca69373275849f98c89c534f3de0bb
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
It avoids facing with wrong substitutions [1]
[1] https://build.opnfv.org/ci/job/functest-apex-baremetal-daily-gambia/23/console
Change-Id: I4b8c990add51024d7984cd10668a33dd7c50c395
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
DEPLOY_SCENARIO wrongly contains DOCKER_TAG [1].
[1] https://build.opnfv.org/ci/job/functest-apex-baremetal-daily-gambia/20/console
Change-Id: I85ddd47e4c15b36f507684d6d7fb9b0d90347507
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It defines DOCKER_TAG as parameter in Functest daily job.
It also fixes DOCKER_TAG default value in properties files and then
complete the previous commit [1].
It should fix the current gate issues [2].
[1] https://gerrit.opnfv.org/gerrit/#/c/64069/
[2] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-gambia/18/console
Change-Id: Ia531ca68a455cc20294e123286062265b9b79d6f
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It let functest-alpine process branches right after [1].
[1] https://build.opnfv.org/ci/job/functest-apex-virtual-suite-master/241/console
Change-Id: I6ed804fe9f3628f67421157433e09da3bcbf585c
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The file needs to at least exist for the inject to work in the case
where the scenario is not rocky.
Change-Id: I2fca0574d69c08a13d0cc797741b276281eb3600
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Moving these jobs to start earlier so that the entire EST daytime job
queue isn't full.
Change-Id: I2cbf8f8fa448a7447b59230abe59d9e559b518c7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
It replaces Queens logics as it should be useless since new gambia
jjbs have been created.
From the time being, Apex jjbs run master containers which should
work thanks to backward compatibility but vnfs are falsy skipped.
[1].
It updates verify-jobs to run the right container (hunter in case of
rocky).
[1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/373/console
Change-Id: I0df483eb78092e8155dd288d3c86d10b7762e433
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
|
|
The URL should not include the gs:// prefix
Change-Id: I09d7c650f665379813eea5fbbfdbe91c1de2fabf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This reverts commit 751002f537007f35a536959e4180ce7c48e18bf1.
Change-Id: I4c7cef7f4296686fda70011e9bf840b114f11845
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
This reverts commit 2e1815d026f209e46fcc7eb29a7d4a28a48b2354.
Change-Id: Idff665fdc88c0936bf7b4fb0bb895d90553ca835
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
I ran all the rtd jobs that were just created
all the ones that got a +1 I have removed the skip vote
these jobs will vote going forward
Change-Id: Ia9a7749f758b96cf1b6a46f00d08a5de7f7d9bbe
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
RTD jobs for all active projects
All jobs start as non-voting.
All rtd jobs are in their own file to
faciliate future bulk changes:
jjb/$project/$project-rtd-jobs.yaml
All project have rtd pages
https://opnfv-$project.readthedocs.io
Change-Id: I776e41f968d38f08cb3187f743f69d5d6b697e8e
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
When we promote artifacts we do not want to include the apex branch (for
example "gambia") in the gs path URL for where snapshots are uploaded.
We may use a different apex branch to promote older OS versions of
snapshots, but we still want a unified url of just
apex/<os_version>/<topology> for our snapshot artifacts.
Change-Id: I7dfe40558ce05d04e1805884cd6a47c82220581e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We want the ability to be able to force a promotion and skip CSIT. This
patch introduces a variable we can use when manually triggering a
promotion job to force promotion. The use case here is for HA scenarios
we have no snapshots because CSIT always fails. We want to be able to
force promotions for this case to at least have some snapshot available.
Change-Id: I7e81b458f4169596929f032e9394695477fbb940
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
apex-virtual-{stream} is not being blocked and running at the same time
while csit tests are running. This should stop it from running until the
promotion job is finished.
Change-Id: Ie164bbee08253a7e79892d36780b66fe0ad2cf97
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
With changes to deploy scenario files for gambia, we still need the
logic to pull in the right csit-env. That logic broke as it depended on
DEPLOY_SCENARIO with the changes to scenario names. This patch fixes it
to check openstack version (OS_VERSION) instead.
Change-Id: Ie130efd0fc3cb7f09a3fa4e896ad461d24394777
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Now that Gambia branch is used for queens promotion, scenario files use
nofeature instead of using branch name.
Change-Id: I76e8f851bc6ef337301d1367dcafd798b212bb38
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Missed a check where we install packages based on old package
convention.
Change-Id: If1da8db9b10b81ea5825b7548509be29e08e6f91
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
jjb/lf-ci-jobs.yaml has jjb-version: 2.2.1 as a minimum
change block-level to blocking-level:
https://review.openstack.org/#/c/608092/
We will need to change this back once we move past
jenkins-job-builder>2.5.0
Change-Id: I12d0f55ee3c2dad20340ebf0fa8428ee1ad8484c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Includes a minor fix to ipv6 rocky scenario.
Change-Id: I55440dff2fcf7674d4a9c86d9dcb131c226e68ea
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
With the move to upstream artifacts post-fraser the checks to use
upstream artifacts were relying on BRANCH == 'master'. This doesn't
scale as we preserve fraser functionality but add more branches like
gambia. Therefore inversing the logic to accomodate for new branches.
Change-Id: Ice17f6afd33744f44d253d320a194c3f6d02d8bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Adds Gambia daily/verify jobs and prepares to migrate master queens
scenarios to rocky scenarios.
Change-Id: I7bfe6202e00fd62c1e668f3a6f9b481b9fbca99d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Now that we branched for Gambia, we want Gambia code to handle promotion
for Queens snapshots, while Apex master is responsible for rocky/master
promotions.
Change-Id: I6f4fffabd728d72fe9b6b2e5a983f6d8762272a9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The logic should have been checking for stable/fraser and didn't account
for newer branches other than master.
Change-Id: I1164ce57338ba1734aa68c98bfe22a8a5f4209ac
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I22c05b0cb2973e84b6352a0ab4e7e38132e909f9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I51e5ecce1e7e5ef851e3c031aeb7819c0712c72d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Make apex verify virtual deployment occur on the same node where
apex-verify job is running. Block apex-verify from starting if csit
promote is running.
Change-Id: I86e76232003b509db516e8d78703d43d36456d14
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Adds pip installing odltools into the cperf container. CSIT jobs now
fetch ODL and other OS logs via apex.
Change-Id: I532d3a6fed156709cb305a9f7a6721d1db2eaebc
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Adds ipv6 nosdn scenario to daily. Also includes a fix where the
trailing new line in the template would be removed and fail jjb check in
jenkins.
Change-Id: I928f7b1cf12381cb2af3a8c7e4beb8e8014451c9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Job will allow us to promote all-in-one snapshots.
Change-Id: I0d0bec8e7598219e17df32bb05a4e8d6efbc52dd
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Id2ac2945af9a419303f21f74cca8eb513f90ce80
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This patch allows us to run a gate job against csit environment, by
doing something like:
start-gate-scenario: os-nosdn-nofeature-noha-csit
Change-Id: I3041404cdfdffe159cff33ecd72be93fe9383e10
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This allows us to run a verify job on an all-in-one (control+compute)
type of deployment.
Change-Id: Ia4174c8eb5d55aaa05e63ddce59301e62b3a8a04
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes-Include:
- OPENSTACK_TOPO is now decided dynamically
- Make the containerized start/stop commands more simple
- Include CSIT logging in CSIT promotion
Change-Id: I4b178cfd95cf45b808ab9e82b317b729e5f3028f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I4a14a7c6bc474b17b3bb04603187c18d0c8c1cf2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Now that we have CSIT suite passing, we want to use that to gate our
snapshot promotion rather than tempest.
Change-Id: Ifddaf7921da15150a253021ee5ca64ab2fd438ff
Signed-off-by: Tim Rozet <trozet@redhat.com>
|