Age | Commit message (Collapse) | Author | Files | Lines |
|
A change to the NodeLabelParameter config in JJB caused any jobs using
the plugin to possibly have their jobs triggered on builders which
weren't online.
This in turn caused the queue to backup and newer jobs are blocked
waiting for older ones to complete, which never happens as they're never
queued on an online builder.
The 'all-nodes' parameter ensure jobs that are set to run concurrently
don't trigger across all available nodes at once, as this will include
offline nodes as well. As this is the default of the plugin, projects
which need it can enable it individually.
Change-Id: Ia690eef078209b6b056dad85613dda6868b18271
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I58fc2c56d32c04f2c96136ed69335b5c64771e05
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I450bbd4a3c0e386f949b3b06fe85e74661e2ef2b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
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: Iee41f1fcaf80f0a0b3a58cd189a04cefcbfbb028
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
lf-build2 seems not to have right ports open, causing problems while
connecting to ActiveMQ Message Broker.
https://build.opnfv.org/ci/view/OpenCI/job/openci-opnfv-k8-nosdn-onap-ha-compose-daily-master/10/console
Change-Id: If78cb8b2748080641db851182860f6a8630a323d
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I52d4ecb5f305f190a9e06c13407fd0927bc45a29
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Change-Id: I9da4c2587874a7ea4ca0f2b90dd7ec15c9e05e34
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Also remove the jms publisher, this is not going
to be used now, as the openci_publisher will be
used instead.
Change-Id: I9a3f4557724cc41ac85ce68a6d0c46ae78864b88
Signed-off-by: Yolanda Robla Mota <yroblamo@redhat.com>
|
|
Change-Id: Ie25586d8ef73a34b68fdf5580df27e5e609e84ce
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Change-Id: I0d6b8525cc12bb71852a8aeeb67cbc37d0456bcb
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Force workspace cleanup
Do not use credentials plugin, but hardcode it.
Change-Id: I5b6e59382c25fc75a748f90fbd030521dac9071f
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
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>
|