summaryrefslogtreecommitdiffstats
path: root/jjb/apex/apex-iso-verify.sh
AgeCommit message (Collapse)AuthorFilesLines
2020-08-03Remove Apex jobsCédric Ollivier1-75/+0
Apex dropped a few years ago and false dependencies between Apex and Functest jobs forbid Functest maintainance. Change-Id: Ic63995325a281e0308abc28e9a89e8054c123391 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.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-02Apex: disable iso verify for master branchTim Rozet1-0/+5
Change-Id: I46753983e1fb37300df70700c474c3dda3532ffa Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-23Apex: Fixes iso verify depending on previous build workspaceTim Rozet1-3/+10
There is a bug where if there are multiple builds queued and daily build completes, the following iso verify job will try to use the workspace of the completed daily build to get the iso file. However, if another build job has already started it may clean and overwrite the workspace of the daily build job, and the iso verify job will fail because the file is now gone. This makes the build job copy the iso to a tmp directory for apex iso verify to consume. This should be safe since only one daily can run at a time on the host and daily jobs build and iso verify have to always execute on the same node. Change-Id: Ie8e32c4abefbc311e505688d6da2b26ae08ed98f Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-22Apex: fix iso verify build dir to absolute pathTim Rozet1-2/+0
Change-Id: I0c85806e5fa04a890a130d8106d96c7fb812e691 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-22APEX: fix permission for rm in iso verifyFeng Pan1-1/+1
Change-Id: Icbecbb39465a3cf4ef4ea3e8f5901561a4874c51 Signed-off-by: Feng Pan <fpan@redhat.com>
2017-05-21APEX: iso verify fixesFeng Pan1-59/+20
The current implementation of iso verify can potentially block indefinitely and/or return incorrect string matching results. This patch changes iso verify to use log file instead of tcp serial console. Change-Id: I89accc9c2165836a23a21a223fa33e920c529772 Signed-off-by: Feng Pan <fpan@redhat.com>
2017-04-25Apex: fixes iso verifyTim Rozet1-1/+3
Change-Id: Id22995b49d12fdb2a5d5d7532d1459f3ac4338f2 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-04-24Apex: fix iso verifyTim Rozet1-1/+1
Change-Id: Ia1d6da64fa245407c5c71f7a56bb6d372fb11ebc Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-04-19Apex: more fixes for iso verifyTim Rozet1-0/+2
Change-Id: Ie1a59806b20072f27adc2f7248c4244e53a5f2bb Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-04-18Adding iso verify to Apex buildsDan Radez1-0/+100
JIRA: APEX-377 Change-Id: I1e02fc602e8258e76f9447d05b09b17e55d0d25a Signed-off-by: Dan Radez <dradez@redhat.com>