summaryrefslogtreecommitdiffstats
path: root/jjb/apex/apex-download-artifact.sh
AgeCommit message (Collapse)AuthorFilesLines
2018-10-15Apex: Fix pkg install for gambiaTim Rozet1-1/+1
Missed a check where we install packages based on old package convention. Change-Id: If1da8db9b10b81ea5825b7548509be29e08e6f91 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-09-28Apex: Fixes branch checkingTim Rozet1-2/+2
With the move to upstream artifacts post-fraser the checks to use upstream artifacts were relying on BRANCH == 'master'. This doesn't scale as we preserve fraser functionality but add more branches like gambia. Therefore inversing the logic to accomodate for new branches. Change-Id: Ice17f6afd33744f44d253d320a194c3f6d02d8bf Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-24Apex: fix unbound variable in artifact dlTim Rozet1-3/+2
We still need VERSION_EXTENSION var to figure out which RPM files to remove on the slave. Change-Id: I03cc9c3318edec9860c8f3ffc01db52517a644b4 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-02Apex: Update for master upstream deploymentsTim Rozet1-23/+20
Change-Id: I92635178ddc354dd7773cd372a34d46f5ee0bf2a Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-12APEX: Fix gate check scenario detectionFeng Pan1-15/+2
- Change scenario parsing to allow k8s scenarios in gate jobs. - Remove scenario detection in shell scripts. Also changes network setting file for fd.io scenarios as we don't use separate config files any more. Change-Id: Icbcc6cb7b6b66c7cc43f5d6c58dd97730e41ea5f Signed-off-by: Feng Pan <fpan@redhat.com>
2018-03-28Apex: Adds parsing scenario on artifact downloadTim Rozet1-0/+20
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>
2018-03-15Apex: add support for deploying upstream onlyTim Rozet1-1/+4
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>
2017-09-18Apex: add back legacy support for danube rpmPeng Liu1-1/+7
Change-Id: I2f4a8c57bf056fcc266a0757b291309671ecc151 Signed-off-by: Peng Liu <pliu@redhat.com>
2017-09-01Apex: fix find command for rpmsTim Rozet1-1/+1
Change-Id: I75bd15be3e68fa630a59cd30a0da72b8f17b8b84 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-01Apex: fixes always downloading RPMs in daily deployTim Rozet1-4/+14
Change-Id: I30bc270c1ae9c648ec184e446a712bd304ad1230 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-24Apex: Updates CI to use new rpm namesTim Rozet1-5/+2
Change-Id: I0455283ba94501119786ffbc3b1217bb71cc35c7 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-08Apex: adds onos rpm back to upload/downloadTim Rozet1-1/+1
Change-Id: Ib71936bec70951dea7478c1dcf657c5f2581fdf6 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-26Apex: fixes downloading artifacts for rpms/isoTim Rozet1-3/+2
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>
2017-05-23Apex: remove downloading ISO for deployTim Rozet1-10/+1
We dont need ISO to deploy, just RPMs. Change-Id: Id3515630ad70f2da6aa0b99b7c1c8cb8857e2311 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-15Apex: fixes upload artifactTim Rozet1-1/+9
Change-Id: Ib12722ec85fe46d1b6dccb7bfc2da748386dac97 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-15Apex: fixes dev label names for artifactsTim Rozet1-1/+2
Change-Id: I2dae20c688ccd2cb690c01a843cb75d5743e129b Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-10Allow Asynchronous Apex BuildsTrevor Bramwell1-0/+71
- 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>