Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I25a8eb8606134255cc77d0b3d5c387e2cf4ee082
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I7a2fa9e3e2bb78ccc2dc6f26be7848019e6de6b8
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I0e1d922ec303bf71e0683b624c51a254da0b9c88
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I82e5db83092b5f4d6f4ea25464f416ce879d4709
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Only ubuntu job votes. The rest is still non-voting.
Change-Id: I0fa2398d3a3d3c5e6e9570488f9e2c15db1c371c
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
According to
https://docs.openstack.org/infra/jenkins-job-builder/definition.html#macro-notes
we only need to use ${{x}} when the macro has parameters. However, none
of our macros has so the correct way to use the shell variable is ${x}.
Moreover, we set the missing execute bit in the jenkins test script.
Additionally, we fix the OPNFV_RELENG_DEV_PATH parameter to point to the
directory inside the VM where the releng-xci repo is located.
Finally we fix the parent directory in which the test is executed.
Change-Id: Ic6157caa5042274a3a3d0de276bdacc15a90a82d
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
We need to respect the environment during testing so we need to create
a proper test script which exports all the variables that matter for our
tests. We do that before we create the VM so the VM creation script can
rsync the test for us. We also properly escape the DISTRO variable when
destroying the VM.
Change-Id: Ic3fff40868155af31762e458c1faee24354c0712
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The XCI script now uses more accurate VM names, so replace
the VM name in the destroy job as well.
Change-Id: Ia4c8ea204ecaa6ae765ce67aff3923dabab6d5f0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Per Idec0fc06c82435adc1a4d569b8e578616998de5f it's now possible
to use a clean virtual machine to verify XCI so lets make use of
it. Moreover this patch updates the distro parameter to use more
accurate names and bring it inline with what dib expects.
Change-Id: I18c88637819884fef07d0bfa0dc2c1077a26c2f1
Signed-off-by: Markos Chandras <mchandras@suse.de>
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Updated all the jobs that use functest-suite.
For single test cases, we need to know to which docker image
the test belongs to.
Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
bifrost is part of XCI so we should run the Jenkins jobs when only
submitting bifrost related changes.
Change-Id: I215b4ca241fd4ffba90c0201dbe8f4c23b8ec280
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
Change-Id: I399fa81c61ae3149c0dada688307627ecc1979f6
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I3a40077f14429de7a23ebf733dff5b13b8bc5d9e
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change adds possibility for patch submitters to skip the full
xci-verify if the change doesn't impact the deployment.
Since the patch will be reviewed by others, reviewers can always
ask the submitter to run it through full xci-verify by changing
the topic and posting reverify or recheck as comment to gerrit
change.
The keyword to put in topic branch is skip-verify.
Change-Id: Ib7be71cadd1e1ddff181936ae77753fbfbf3a1d3
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Instead of setting the verbosity in jobs, they can be set in scripts
to move the setting to where it makes most sense and possibly easing
the work for ansible version adaptations by fixing it in one place.
Change-Id: Ie155b666cf5300a3f57687b3214a65d5d79aeee1
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This patch should unblock:
https://gerrit.opnfv.org/gerrit/#/c/40533/
Change-Id: I72e827b0feae559e6477d213d0f752ed04cd62b3
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
The external network, docker installation and other parts need
to be fixed in OPNFV host before functest can be enabled.
Change-Id: I42a3adf2e36f91e6425d49e2578003b52ca4f101
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Functest daily is based on the functest alpine dockers:
- healthcheck
- smoke
- features
- vnf
Change-Id: I922f3a5946e8bc06229fb03a959abd2bfead132b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
We only care to trigger builds based on changes under xci/, not
including xci/README.rst
Change-Id: I347e0d7ef658c41322b7c3e25740fa4d2f960bdc
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
There is no 'README.rst' at the root of the repo, but there are
README.rst under xci, bifrost, etc. Changes to these READMEs shouldn't
trigger builds.
Change-Id: I6a09388cf40b35211d58413b45b5ac8c596a2dc7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
- add the rc file retrieval in fetch_os.sh
- adapt alpine to split healtcheck from daily
(healthcheck + smoke + features)
- adapt the xci builder
Change-Id: I38836814240a1d769d379a10c9ef14def7e6df97
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
The job doesn't need to be triggered if there is no code change, eg
commit message updates.
The remnants of previous directory structure is also removed from
gerrit trigger/forbidden-file-paths.
Change-Id: I68b9e70d0d70253d7fbad95f8dedaaa63fb2b26e
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Change-Id: I2f60bac555571d4fddbde63bf8002aae2df47de3
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I18105f9289f67f634431013d08b24608380f00e4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
openSUSE Leap 42.3 is the latest release so update the CI jobs to make
use of it.
Change-Id: I875bf924be9c84607d4b859a72f5eade4ca5f36d
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
This job
- updates osa periodic jobs to use multijob project type
- adds pollscm trigger to prevent running job unnecessarily
if there is no change in upstream osa
The execute shell parts will be sent in separate change(s).
Change-Id: I5f9b4cad04b245192171278e6bf2806c94369854
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I370d2822071c77a16387935e1d465f608ee9e10e
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
- Fix environment variables set by the job
- Fix the default distro in deploy job since the {distro} is not passed to it
- Navigate to correct directory where xci-deploy.sh is located
Change-Id: Ie412dc4852a4aac5aae5c1f26bb271281ebbc111
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This job gets triggered when a new patchset to xci is created.
Currently only the deployment is run and healthcheck will be activated
once xci is adjusted for functest.
Change-Id: I3ea61524de6c6b5e2d872f59bb362d9c9be6053c
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
|
|
Make use of the build-timeout macro to kill the job after 90 minutes
which is more than enough for a bifrost job to finish.
Change-Id: Ic7ffa8291d057bf22f7d97d017c00bd3f3b6f4a9
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The errexit option is there to catch failures when the job is executed.
We don't want to mark the entire job as failed when we have troubles
uploading the logs when the actual job has passed so we disable the
errexit option to make the whole process less aggressive. Moreover, we
move the build log upload to the end of the operation so we can catch
as much output as possible.
Change-Id: Ice126471a8c837c54c95c8ef0935c059d37ea91b
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The full distro elements are not well maintained. Upstream OpenStack
also prefers the minimal elements when building images for the CI so
we should do the same to minimize the delta between the two systems.
Change-Id: Ifeddb0a74c2434df2cfa95cde36b4aaac1516698
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
With the releng-xci code moving to it's own repository, the Jenkins jobs
need to be modify to clone the correct repo and point at the right
paths:
* The git repo is changed to 'releng-xci'
* The cloned directory is changed to '$WORKSPACE/releng-xci'
* References to the 'prototypes' directory path have been removed
Change-Id: Ia1d2ad0a2fb6cc9d1848356edf448b92ab67b017
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Adds the 'email-jenkins-admins-on-build-failures' publishers for jobs
which have overridden the default list of publishers.
This will provide Jenkins administrators a time-series list of build
failures to assist in debugging issues with the master and agents.
JIRA: RELENG-257
Change-Id: I28f12877562113c9197ed6429ee2a7f3cdbaf346
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
A disabled trigger is set to the empty string, not prefixed with a
comment character.
Change-Id: I0b29857f0907f33bb0fb8156bb6db84113f1479d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Switch default target OS to Ubuntu Xenial (16.04) which is also the
version supported by bifrost.
Change-Id: Ia139af9d03c85225e741c78ce35ecc59cd990108
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Commit 0638af211db1 ("jjb: xci: xci-deploy.sh: Run the deployment
script as normal user") dropped 'sudo' from the bifrost provisioning
script. However this broke the jobs since the repositories were being
cloned into /opt where the jenkins user has not access to. As such,
clone the repositories in the $WORKSPACE directory instead.
Fixes: 0638af211db1 ("jjb: xci: xci-deploy.sh: Run the deployment script as normal user")
Change-Id: I55baceaada04496884470997562e3f512f2444a0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
xci-deploy.sh can now be run as normal user so fix the Jenkins job
accordingly.
Change-Id: Ifd0d7e4c42c930dbee0bbc30836fadc1a54f2f95
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Ansible can request elevated privileges using the 'become' directive.
As such there is no need to run ansible using sudo. Furthermore,
OpenStack CI runs all jobs as normal user and we need to do the same
in order to compare behavior and results properly.
Change-Id: Id198efd1d6fdf4619de931fbedc7caba8d68d2a0
|
|
The os_client_config Ansible module used by all the ironic-* roles
depends on the keystone roles so we need to make use of them even
though they do not affect the end result. This fixes the following
OPNFV CI problem due to not having a clouds.yaml file present to
be consumed by the os_client_config Ansible module.
fatal: [controller00]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_ApkCUQ/ansible_module_os_client_config.py", line 75, in <module>
main()
File "/tmp/ansible_ApkCUQ/ansible_module_os_client_config.py", line 63, in main
for cloud in config.get_all_clouds():
File "/usr/lib/python2.7/site-packages/os_client_config/config.py", line 798, in get_all_clouds
cloud, region_name=region['name']))
File "/usr/lib/python2.7/site-packages/os_client_config/config.py", line 1071, in get_one_cloud
auth_plugin = loader.load_from_options(**config['auth'])
File "/usr/lib/python2.7/site-packages/keystoneauth1/loading/base.py", line 162, in load_from_options
raise exceptions.MissingRequiredOptions(missing_required)
keystoneauth1.exceptions.auth_plugins.MissingRequiredOptions: Auth plugin requires parameters which were not given: auth_url
fatal: [opnfv]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
Moreover, we cleanup the ~/openstack directory which may contain some
bifrost artifacts such as a clouds.yaml file.
Finally, we use 'sudo -H' because for the keystone roles we need the HOME
variable to be set properly.
Change-Id: I45b08bd33dd8ea9505fe10eb4b2b10956b3b683c
|
|
|
|
Variable 'i' does not exist. It should be 'try_to_rm' instead.
Change-Id: Ic2aa5a1115715851379e2c7ba5c11699cb8e7407
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
XCI has different jobs/loops to run
- patchset verification jobs (currently bifrost and osa in future)
- periodic jobs (bifrost and osa)
- daily jobs (for OPNFV platform deployment and testing)
The same scripts/playbooks used by XCI will also be used by developers.
We need to do different things depending on the context the scripts
and playbooks are executed.
- periodic jobs will use latest of everything to find working versions
of the components. (periodic osa will use unpinned role requirements
for example)
- daily jobs will use pinned versions in order to bring up the platform
and run OPNFV testing against it. (daily deployment will use pinned
versions and role requirements for example)
- developers might choose to use pinned versions or latest
Depending on what loop we are running, we need to do things differently
in scripts and playbooks. This variable will help us to do this in easy way.
We can of course do pattern matching of the job name but it will not
work if the scripts are used outside of Jenkins.
The default loop for non-Jenkins execution is set to daily as we want
developers to use working versions unless they change it to something
else intentionally.
Change-Id: Iff69c77ae3d9db2c14de1783ce098da9e9f0c83d
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|