Age | Commit message (Collapse) | Author | Files | Lines |
|
Changes-Include:
- Use 2 computes as required by ODL team
- Get rid of checking JOB_NAME var for csit, and simply check if
PROMOTE var is True
- Pass PROMOTE all the way from top-down into deploy job
- Use CSIT network settings file when deploying CSIT
Change-Id: I56d953516ce690749634b474e553baad3a762364
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I274dba9398ef549d20fa106eda88abebfbf48c9e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This job already does deploy and test, so just use that rather than
triggering seperate jobs.
Change-Id: Ie62088f434de93ebb7638ba4d4ef8791ac01aa1f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ie2d0a730801bc7f5bb784ee90e60e8e30562ef47
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Promotion name for master OS should just be nofeature.
Change-Id: I60086e94bbef87a1754f4f2cc00d096454668ded
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
Now that we only build apex python rpm in master, we can afford to build
RPM everytime and ensure it builds correctly.
Change-Id: Ica1efe1cc2c3db0dfe1c5677b5ab47df121c0966
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I881634a57f1d28cfcc3346476dc095873c014a22
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
global-jjb only supports the .yaml file ending for jjb jobs. Instead of
waiting for a release we're going to rename the files.
Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: If50ad310049edca687da8e0acf412a7e1eacd2b6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I46753983e1fb37300df70700c474c3dda3532ffa
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I92635178ddc354dd7773cd372a34d46f5ee0bf2a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Due to python-iptables calling out to ldconfig, we need to ensure
/usr/sbin is available when running the Apex unit tests.
Change-Id: I77fd4dedd6e7ad3c3831a1d181a5406d53a0e76e
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I17c1aad45f8b965543a9c7d769ff94f59b9381d5
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I41926856b129eb7dd99c5db8765961acd241eb55
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
We will not support RT KVM and IPv6 scenario.
Change-Id: Iabd52f3ff803488e1ac68e8946001a7c04f5ca7f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I055ec261368b341c5dd9f2ab5082c8ced15ad6e5
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
- 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>
|
|
The wrong job name was being triggered so no job was running to collect
logs.
Change-Id: Ib58b030ac24920fc7906bff92a481407587a39bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
As part of our new XCI effort, we only enable upstream ODL scenarios
initially.
Change-Id: I737bbffce14b6c5c69dfbbb653659c7e693cb4fb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ie7bd0d3299fbbb8bc3e865612026ad479c48392d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Logs were owned by root, so jenkins-ci could not upload them. Also
prints exact links for each file so it is easier to directly view logs
from jenkins output.
Change-Id: I919bf38c87561a696ae96683c56ad5f96c8d795e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
condition actually affects *next* phase execution and not conditional on
previous phase. This change fixes the condition so that fetch logs
always runs.
Change-Id: I50c3f9f9412682ea591c47116d406b5ed81ee2b5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I28e4b613d92c43d32e95f8e1b4f4a4e2db102bc5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
We were using 'stream' as part of the slave label to run unit tests on.
However, we typically just use master label for everything to avoid
having to update labels on slaves. Changing the unit test to follow the
same method.
Change-Id: I6a182c3f28d541109c8a9d94ea1dae2a80f2b835
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
With this commit:
https://gerrit.opnfv.org/gerrit/#/c/47875/
We can now gather logs from after at the end of a deploy/test job and
upload them to artifacts. This patch enables that behavior on verify
and daily jobs.
Change-Id: If7af4cf1363e4bbcee78d98850af7c0e20250f3f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I7f6072121c4d88192c828e2e3cf2beb5d6c22c37
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I37c7b8b6e4bd19ef94b9b42fe2e5e89cc3e2da21
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
Wrapping the script into a function will make it importable from other
python code. Calling the file directly will still work as it did before.
Change-Id: I8336d34b05687fa650ce1c123bb37fa311ce2978
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
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>
|
|
1. Run test suite ovp.1.0.0 on Apex with even 'BUILD_NUMBER'
for scenario nosdn-nofeature and bgpvpn.
2. Run test suite proposed_tests on Apex with odd 'BUILD_NUMBER'
for scenario nosdn-nofeature and bgpvpn.
JIRA: DOVETAIL-611
Change-Id: I5d4a86242d633eb83ddb0939dff5cf617c971c3b
Signed-off-by: xudan <xudan16@huawei.com>
|
|
fingers crossed
Change-Id: I220a36ec8a6a0d95e847a5672c4d8e5c0d34c5ac
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Remove and then re-add to see if we can get jjb merge to work
Change-Id: Iff380b38bbc5a69e2850cd91a99267b6d5b1128f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I88f33b7dcdf8f4d0a3aa3f8d46a07f10c62e6ae9
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
We were missing concurrent on this job which was preventing parallel
execution.
Change-Id: I4d1ea62aef2a321220799cebee008f494490886c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
Scenario list for Fraser:
https://wiki.opnfv.org/display/SWREL/Fraser+Scenario+Status
Change-Id: I083dc5b0b9cea9f91d7a9568a05df5865aeafa05
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
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>
|
|
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job
is triggered by Gerrit. Because it is not explicily defined, there is no
way to manually trigger jobs, as the git clone looks up the list of refs
by GERRIT_REFSPEC.
Being able to manually trigger jobs (with node parameters so they can be
restricted) is very helpful in debugging CI issues.
Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I92b3c2fce51dad5e0e00b836a41af40f845e701e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I7b10ac19a8844832886e6a54d065ee79dde026d0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
Since only APEX has the bgpvpn scenario in Euphrates, enable run dovetail
on Apex euphrates scenario os-odl-bgpvpn-ha to test sdnvpn test cases.
JIRA: DOVETAIL-568
Change-Id: Ic7c880a5ef911fac17807e19484f937bdaa53e21
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Change-Id: I2f6e54badddf234fb781adc49b8395ac0144da06
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
These scenarios will not be part of 5.1 release.
Change-Id: Ied91df7379705414850cda504842ecef2b3c7e0b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This value is usually passed by parent jobs (daily, verify, etc), but
exposing it as parameter should allow us to build from JJB GUI.
Change-Id: I294fbcd200ff5d8bbfca77681296c6e59d7f0063
Signed-off-by: Tim Rozet <trozet@redhat.com>
|