Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I2341191b9afbf7b572a6ae28a50eb722b66109c7
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Change-Id: I449037e727abed363766ca47a26ea3d2bd6abf4e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
The flow is
- OPNFV compose job gets triggered by the ArtifactPublishedEvents published by
ODL and ONAP autorelease jobs, composing the corresponding scenarios. At the
end, CompositionDefinedEvent is published for the composed scenario.
- OPNFV test job gets triggered by the CompositionDefinedEvents published by
OPNFV compose jobs, deploying and testing the composed scenario. At the end,
ConfidenceLevelModifiedEvent is published for the tested scenario which can
be consumed by ODL and/or ONAP Jenkinses, doing further promotion.
Change-Id: Ice1736d65f3f2b26e849302fec2bb0c579da4a1c
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: If05f7922d5888775eff113877b8bdd319948956a
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I1efdff3dbcfdcc9b0820b43d982f686bbe1db4a7
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
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>
|
|
The jjb will be proposed to ODL Releng once it is verified on OPNFV
Jenkins.
The flow is
- ODL autorelease job publishes an ArtifactPublishedEvent to make the
availability of a new version that is tested known to the world
- ODL 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 ODL scenario
- run the deployment and testing of ODL 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: I51d7e0cfcb5f2552fcc9ac287ed12ed70f582895
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|