summaryrefslogtreecommitdiffstats
path: root/jjb/xci/xci-merge-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-01-22xci: Clone releng-xci repo for phase jobs as wellFatih Degirmenci1-1/+6
Forgotten to fix phase jobs. Change-Id: I50c525089d6d3b4f28650ad78b8810817aaf150e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Clone the repo and checkout the patch for testingFatih Degirmenci1-0/+3
Change-Id: Ie1c2f76b6043133c3821272040b1a2a38de29035 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci: Always clone releng-xci into WORKSPACE for merge jobsFatih Degirmenci1-1/+6
The cloning of the correct version of the repo which the scenario resides in will be handled by get-opnfv-scenario-requirements.yml for all the scenarios. The change proposed for merge jobs will be reflected to verify jobs as well once it is verified with this. Change-Id: Icaa99a8b9e981c839969ce556e5af6a9ef6d9da8 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22xci sfc: Enable post merge deploymentFatih Degirmenci1-19/+11
This change enables the deployment upon merge of a change. Followup patches will incorporate functest smoke and promotion which the promotion will most likely be the first one as functest parts are a bit tricky due to failures while running testing in VMs. Apart from the enablement of the deployments, job concurrency is disabled as well since we should only test one change at a time and attempt promotion for any scenario in order to ensure we keep the promotion consistent. Change-Id: Ib4b5754b6b88f42eab83c656e03773c83068016f Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-10RFC: Set the basic structure for post merge jobsFatih Degirmenci1-0/+252
This change proposes structure for post-merge jobs for the scenarios that are onboarded to XCI. The idea with these jobs is to verify the sanity of impacted scenario to find out if the version that is tested should be promoted to the next level in XCI; daily on baremetal. If it succeeds, the metadata regarding the scenario needs to be stored somewhere (artifact repo, etc.) so daily jobs can poll that location to see if there is any scenario that is worth testing on baremetal. If it fails, the scenario could be demoted instead which still requires further discussion and thinking. We might perhaps leave the metadata of the version of the scenario with previous sha as the candidate for testing instead of demoting it since we need to have working version of the scenarios at all times. Change-Id: I85d7176b16d0d6da45cd2462b0cdb990485b6b0d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>