Age | Commit message (Collapse) | Author | Files | Lines |
|
Download was not properly being skipped on upstream scenarios because
the scenario was not being detected and was set as "gate".
Change-Id: I38533ad8140be48726aa2cb1c106d7ef6ca9afd5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Scenario names with 'upstream' in them will not download any artifacts
and deploy from upstream. For now, this even applies to the apex
python RPM for daily deployments. We will only use git repo for
daily until after Fraser.
Change-Id: I0da16dfde117ba6c1e7597294d8e4afc8501dd53
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2f4a8c57bf056fcc266a0757b291309671ecc151
Signed-off-by: Peng Liu <pliu@redhat.com>
|
|
Change-Id: I75bd15be3e68fa630a59cd30a0da72b8f17b8b84
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I30bc270c1ae9c648ec184e446a712bd304ad1230
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0455283ba94501119786ffbc3b1217bb71cc35c7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ib71936bec70951dea7478c1dcf657c5f2581fdf6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We always update the latest properties file on daily builds. We should
be pulling that to find artifacts rather than the current date properties
versions.
Change-Id: I52d3b53fdd17ecb6cbb43759309568d0c22013f8
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We dont need ISO to deploy, just RPMs.
Change-Id: Id3515630ad70f2da6aa0b99b7c1c8cb8857e2311
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ib12722ec85fe46d1b6dccb7bfc2da748386dac97
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2dae20c688ccd2cb690c01a843cb75d5743e129b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- Remove any build blockers on 'apex-build-*' jobs.
- Adds script to download latest build artifacts before deployment.
- Make each deploy download the needed artifacts before running.
- ARTIFACT_VERSION now set to dev for verify builds to indicate tarball
should be uploaded to artifacts repo
- apex.yml jjb is now generated by using apex-jjb-renderer
- scenarios are managed in scenarios.yaml
JIRA: APEX-328
Change-Id: I4a51565686bd2011a310c3926d8260cd4641dca5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|