summaryrefslogtreecommitdiffstats
path: root/jjb/apex/apex-verify-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-02-13Apex: Attempt to fix apex-virtual parallel executionTim Rozet1-1/+1
Remove passing node params and enable global queue scanning. Hopefully this will allow 2 apex-virtual jobs to run at the same time (1 per each slave). Change-Id: I310dbc477e267c302d50599bab2a933ce988dba7 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-08Apex: Cleanup slave/slave-label configurationTim Rozet1-4/+2
Changes Include: - Remove defining 'node:' per job template and use slave-params defaults - Gate job was using daily/build slave, when it should be using virtual slave Change-Id: Iec2321801daef1b1fa40724a244bf2f6edf36c6e Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-07Apex: Fixes scheduling with apex verifyTim Rozet1-1/+1
apex-verify job calls apex-virtual to deploy and run functest. Apex has 2 virtual slaves attached to the apex-virtual-master label. When 2 verify jobs are triggered at the same time, apex-verify job is scheduled on each slave correctly. However, when the mulitjob triggers apex-virtual jobs, it only schedules both of them to a single slave. This happens even though apex-virtual job has the same slave label and node parameters are not passed from verify job. This patch changes the node to be passed to apex-virtual from apex-verify. That way 2 nodes will be scheduled on, but this is still not ideal scheduling as more than 1 verify can run per node (but not more than one virtual job). Change-Id: I155351c9037f70df2c5dba11bb5592423849e760 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-12-20Apex: Enables verify trigger for ci directoryTim Rozet1-0/+2
We were missing triggering on the ci/ path in our Apex repo. This contains some code and a file we use to trigger verify jobs for dependent patches. Change-Id: I54f2826f8a16a1d0219d6ecc6ef8d257840b6399 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-17Fixes load-balancing jobs for virtual verifyTim Rozet1-1/+1
Issue where apex-virtual-master label node was being passed from verify job to deploy/functest. We allow multiple verify jobs to kick off on virtual slaves, but then passing the host down to the deploy/functest jobs causes the deploy/functest only run 1 job at a time on the same node, rather than running 2 jobs at a time, one on each slave. Change-Id: I1648eb6b84f17a2b08db4d161effe977c7952d63 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-15Apex: fix slave for verify jobsTim Rozet1-1/+1
We use apex-virtual-master label for slaves that will deploy and run functest. Build and unit test will not use this label and will use apex-build-master. Change-Id: Ibf266bd37813ea8ef38fc8060f73f83462275cfd Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-02Move Apex Verify Jobs to apex-verify-jobs fileTrevor Bramwell1-0/+364
JIRA: RELENG-287 Change-Id: Ie50fdddc47b47764d3e3064904f19015d5d39341 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>