Age | Commit message (Collapse) | Author | Files | Lines |
|
It is necessary to log the eventBody to console before we attempt
to publish it since it is not possible to see the event body in
case if the publisher errors out due to invalid JSON.
Change-Id: I79cb93f64f5e6e275e306b375210f5f2ed7bd53d
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I9bdcbf24573bb2202e8ec3c43b3cdfc2ba7df321
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I9da4c2587874a7ea4ca0f2b90dd7ec15c9e05e34
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>
|