summaryrefslogtreecommitdiffstats
path: root/jjb/xci/osa-periodic-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2017-06-28Remove invalid Timed trigger from Bifrost JobsTrevor Bramwell1-1/+1
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>
2017-04-04xci: Introduce XCI_LOOP variable to control what to do properlydanube.1.0Fatih Degirmenci1-0/+3
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>
2017-04-02xci: Create periodic osa jobs to find working versionFatih Degirmenci1-0/+146
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>