summaryrefslogtreecommitdiffstats
path: root/jjb/openci/openci-onap-daily-jobs.yaml
AgeCommit message (Collapse)AuthorFilesLines
2021-02-08Clean obsolete jjbsCédric Ollivier1-81/+0
They should have been cleant when closing the projects. Change-Id: Id00da883e6ea14631f2098e40978bcf793d5636b Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-09-20openci: Switch to python utility for publishing messagesFatih Degirmenci1-21/+3
Change-Id: Iee41f1fcaf80f0a0b3a58cd189a04cefcbfbb028 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-05-18openci: Further filter triggering events based on scenario for ODL and ONAPFatih Degirmenci1-0/+2
Change-Id: If05f7922d5888775eff113877b8bdd319948956a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-05-18openci: Add event publisher to ODL and ONAP Autorelease jobsFatih Degirmenci1-4/+30
Change-Id: I1efdff3dbcfdcc9b0820b43d982f686bbe1db4a7 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-05-17openci: Add skeletons for ONAP autorelease and promotion jobsFatih Degirmenci1-0/+71
The jjb will be proposed to ONAP Releng once it is verified on OPNFV Jenkins. The flow is - ONAP autorelease job publishes an ArtifactPublishedEvent to make the availability of a new version that is tested known to the world - ONAP promote job gets triggered by a ConfidenceLevelModifiedEvent published by OPNFV CI to promote autorelease artifact further. The prototype doing realistic stuff will be built on top of these jobs and - parse the triggering event to find the location of autorelease artifact - download the artifact for composing ONAP scenario - run the deployment and testing of ONAP scenario Please note that this change just adds the basic structure for the jobs to share the idea. Further changes will add triggering, message costruction, and publishing. Change-Id: Ib8939ab44d664ff71f472db66a0e2171ed7b56c5 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com> Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>