Age | Commit message (Collapse) | Author | Files | Lines |
|
Instead of setting the verbosity in jobs, they can be set in scripts
to move the setting to where it makes most sense and possibly easing
the work for ansible version adaptations by fixing it in one place.
Change-Id: Ie155b666cf5300a3f57687b3214a65d5d79aeee1
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I2f60bac555571d4fddbde63bf8002aae2df47de3
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This job
- updates osa periodic jobs to use multijob project type
- adds pollscm trigger to prevent running job unnecessarily
if there is no change in upstream osa
The execute shell parts will be sent in separate change(s).
Change-Id: I5f9b4cad04b245192171278e6bf2806c94369854
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
With the releng-xci code moving to it's own repository, the Jenkins jobs
need to be modify to clone the correct repo and point at the right
paths:
* The git repo is changed to 'releng-xci'
* The cloned directory is changed to '$WORKSPACE/releng-xci'
* References to the 'prototypes' directory path have been removed
Change-Id: Ia1d2ad0a2fb6cc9d1848356edf448b92ab67b017
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
A disabled trigger is set to the empty string, not prefixed with a
comment character.
Change-Id: I0b29857f0907f33bb0fb8156bb6db84113f1479d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
XCI has different jobs/loops to run
- patchset verification jobs (currently bifrost and osa in future)
- periodic jobs (bifrost and osa)
- daily jobs (for OPNFV platform deployment and testing)
The same scripts/playbooks used by XCI will also be used by developers.
We need to do different things depending on the context the scripts
and playbooks are executed.
- periodic jobs will use latest of everything to find working versions
of the components. (periodic osa will use unpinned role requirements
for example)
- daily jobs will use pinned versions in order to bring up the platform
and run OPNFV testing against it. (daily deployment will use pinned
versions and role requirements for example)
- developers might choose to use pinned versions or latest
Depending on what loop we are running, we need to do things differently
in scripts and playbooks. This variable will help us to do this in easy way.
We can of course do pattern matching of the job name but it will not
work if the scripts are used outside of Jenkins.
The default loop for non-Jenkins execution is set to daily as we want
developers to use working versions unless they change it to something
else intentionally.
Change-Id: Iff69c77ae3d9db2c14de1783ce098da9e9f0c83d
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
These jobs run periodically against the HEAD of master and stable/ocata
branches in order to attempt deployment and help us to find more
recent working versions to pin.
In perfect world, these jobs should be run post-merge, helping us
to move faster but lack of resources prevent us doing that.
One thing to note here is that we use the pinned version of bifrost
in order to make sure we change one thing at a time to reduce the
delta.
Change-Id: Ieaff7e80581c7577b253b3646ca386313295a45a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|