Update listed jobs to be close to master dashboard when relevant and add
some stable-specific jobs
Add master dashboard enhancements like TIMED_OUT count
Fix dashboards description formatting and content
Change-Id: I22cf934898dd357f5e96eb068d6eed6e2fa987ce
Local testing passed, but when run in the gate, script execution failed
on the sed expression not being preceded by '-e'.
Change-Id: I02545e1f976f220f197556bdfa6e6225d9bd8d36
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Missed in Id58f439052b4ea6b092b87682576a746433dcc27 that the branch name
passed in when determining the next series name will be of the form
'stable/series', resulting in not finding the next name and job update
logic being skipped. This adjusts the branch name to properly match the
series name.
Change-Id: Ie4102ceb0d12b7d98919ddb89b8e17df1859fa6a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Currently, we need to update jobs manually after a branch is
created.
When a project is branched, the master branch should then
be pointing to the new named python3 tests.
This should do it.
Change-Id: Id58f439052b4ea6b092b87682576a746433dcc27
The install- roles have been renamed to ensure-*, follow the rename.
Depends-On: https://review.opendev.org/716698/
Change-Id: I2522028e9091efdbe292529474de7cce2cf29039
The job runs dependent on some other infra playbooks, but when
it's just the zonefile changing, we don't need to update
system-config for base.
Change-Id: I59551be29d34246177a54193ff6502f555cdb773
These are being triggered by the zones repos, not the system-config
repo, so the file matchers aren't right.
Change-Id: Ibdc3690c644bd505abc7aeccda89ad8db667391b
As both repo_build and pip_install roles have been succesfully replaced
with python_venv_build role, we have no need in it's futher maintaining
and releasing them.
Needed-By: https://review.opendev.org/717717
Needed-By: https://review.opendev.org/716389
Change-Id: I3901963eab6845e302feb3d3bca5ee47697a5658
This is particularly important for debuntu where we need working gpg for
apt and a missing gpg-agent is fatal. We install it globally so that
consistent tooling is available across systems.
Note everyone but suse seems to have a gnupg2 package. Suse calls it
gpg2.
Change-Id: I6c56e85db501f2c9d7c648e614f1efbaadc213a2
This is independent + change-merged. With files matchers, promote
is actually problematic because we'd elide sets of different
changes potentially missing triggers.
Use deploy pipeline for project-config deployments
These all have files matchers which makes using them in promote
problematic due to deduplication.
Change-Id: Ic77cdb2aab359b20b9c8b3a66ee031d24f7c95a0
The previous patch fixed the promote job for running nodepool
ansible. This should trigger it to run, which was skipped in the
previous patch.
Change-Id: I301750a91039311675fbb0c5fa2a76349f547b62
The release-approval pipeline uses a username filter in the
comment-added trigger so that comments from 'zuul' username would
not trigger it. Unfortunately, the regexp also matched usernames
which contained a dot, like 'rico.lin'.
Fix the regexp so that it matches 'ttx', 'rico.lin', 'zuulfoo' and
'zuul.bar', but not 'zuul'.
See tests for the old and new regexp at:
http://paste.openstack.org/show/791583/
Change-Id: I6834f71b52570310735f202984af8f7f6ce701a1
Until we can trigger jobs when zuul publishes new images, we should
run a few of our infra-prod playbooks on an hourly cron to keep up
with changes.
Change-Id: I08525729ec30b5f565f1858a357591503dd2a215
We've got the keys in place, and the zone file repos are, for now,
owned by infra-root, so this should be safe.
Depends-On: https://review.opendev.org/716764
Change-Id: I050464cc4ad896342ffc9125d12af73058791438
When we change nodepool config files, we should roll them out.
Depends-On: https://review.opendev.org/716770
Change-Id: I01c7770d8dc310f5da8aa7ee349b58dd0b88d1e0
As a follow-on to I811aa3f796e3d1a3a17832bdc038853537f48497; fedora-31
is now built and working on nb04, images are uploaded. Add it to the
main config file, but paused, so the launchers know about it.
Change-Id: I1688b4eb60e35e47d086a3be6c6476aa413497d7
As part of [1] we are removing pip-and-virtualenv. dib 2.35.0 merged
an accidental breakage for Fedora [2]. We might as well use this as
an opportunity to have this as a "bare" test platform; where we leave
configuration of pip/virtualenv up to jobs. This will be alongside
the ubuntu-bionic-plain images (see
I85438baf5bb31790a56fe5b38327361f0a2398e9).
[1] https://docs.opendev.org/opendev/infra-specs/latest/specs/cleanup-test-node-python.html
[2] https://review.opendev.org/716795
Change-Id: I56a2495e9c768d744ac39073c42a5a1754612f70
With the previous change, we stopped having pipeline configuration
loaded inside the vexxhost tenant, this restores the pipelines.
Change-Id: I8fa6160b4694b93434d269973f95de8ed3ccd180
Inside the VEXXHOST tenant, we have a need to be able to use build
Docker images in many different places. Therefore, we need the
ability to have secrets inside of a repository which other repos
can just use the jobs for, avoiding the need of encrypting the
Docker credentials for every single repository.
However, due to the current limitation in Zuul, it's not possible
to accomplish this without having a config-project, and by being
a config-project, that provides an elevated set of access. As
an interim solution until Zuul has the ability to do this without
using a config-project, this change makes the project a config
project however changes the ACLs to include project-config-core.
The rationale was that I (mnaser) is already part of that group
and therefore this wouldn't be providing me any more access to
make changes to config projects. This would be an interim solution
until we're able to do this natively with Zuul and the ACLs can
return to VEXXHOST.
In this change, we also move opendev/project-config to only load
jobs, secrets and nodesets and to avoid loading the project so we
don't end up reporting to changes to opendev/project-config.
Change-Id: I6baefcae3e23767aeeaa2d572b1a17fd2aa5ebe6
