This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I6c126f7e724249741403a87733f546c1642f7f25
Currently the default is to use gitea green which looks a little weird
on our site when using mobile browsers. I don't see an easy way to
revert to the browsers default color but there may be some magic like
using a 'default' string? That may be an alternative option we can
consider.
Change-Id: Ia4e3d25b75bba169c3b7cc60c52c0de791e6be21
I ran our global gitea project sync playbook across all eight gitea
hosts and one failed with a 404 against a specific project. Rerunning
the playbook against that one gitea server worked fine.
Until we sort out why this might happen lets retry our HTTP POSTs up to
3 times until they succeed.
Some numbers: We have ~2k repos and 8 servers and make two http requests
per repo for a total of 32k requests. If one fails out of that the
success rate is very high so retrying a few times should be fine.
Change-Id: I937a4f852f6713a419c03a17c3b4984a97eae0d8
This is calling tools/cloud-to-env.py without a full path, which fails
when it's called from the run_all_script which hasn't cd'd to
/opt/system-config. Use the old "cd to my parent dir" at the start of
the script.
Change-Id: I54a97c6942edd8a047ac679f6b0b08f0e5595f1f
After we reboot the lockfile directory disappears. Recreate it before
running the puppet that would create it anyway.
Change-Id: Ia0779240b9e516090237dfbe61404fab114c6d4a
In roughly lexicographical order, upgrade a batch of servers to puppet
4. We skip ask-staging because although it is in the futureparser group
it was temporarily disabled in puppet and so hasn't actually gone
through the futureparser validation stage yet.
Depends-On: https://review.openstack.org/643465
Change-Id: I3971ffb9800e95aaaba0076ec3bd6a05cd92a750
We've been upgrading many of our nodes to xenial from trusty. Remove the
manifests/site.pp trusty test flags from nodes that don't run on trusty
any longer.
Change-Id: I2ee9754d8b30f120d375cb6ff554c107f4a750d5
Some projects use storyboard and some use launchpad as their issue
tracker. Handle this dynamically based on the projects.yaml content when
we create projects and set the appropriate urls.
Change-Id: Ie1d79bf1a662c00078689f2c752231e610610eda
Story: 2004627
Task: 29849
We were previously creating zuul status backups for http and https
endpoints. We really only need them for the https endpoint. Additionally
backup our kata-containers tenant.
Depends-On: https://review.openstack.org/642896
Change-Id: I35a58b2faf3234aa0f3c04e5a682c8f9f9111898
The Xenial-based wiki-dev02.openstack.org server will replace
Trusty-based wiki-dev01 once completed. Include it in the inventory
so configuration management can be applied before the CNAME RR for
wiki-dev is changed to refer to it.
Change-Id: I4bc08c3e204219bcc99c51f3154d89813a6d55ab
Currently there are no plans to integrate the existing wiki services
into OpenDev, so for clarity we're limiting the inventory globbing
and global site manifest node regular expressions to the
openstack.org domain specifically.
Change-Id: Ifdc86f7cc5d6a865e1d5f76828ad8b52f2ee75fe
As part of the move to Gitea, we're creating compatibility redirects
from our old Cgit and Git HTTP backend sites to opendev.org. This
introduces Apache vhosts for each of git.airshipit.org,
git.openstack.org, git.starlingx.io and git.zuul-ci.org which all
serve the same docroot on the files.openstack.org server. This
docroot houses a single .htaccess file with the relevant redirect
rules.
Change-Id: I729fe39bcbe0a0cae237e9036ed8fa980f897e68
Co-Authored-By: James E. Blair <jeblair@redhat.com>
Task: #29705
There's no real need to tie these together into a multi-stage
Dockerfile as they don't really share anything. Split them.
Change-Id: Ifd7ccadcd8048eeb57797d60356aec2f9f0d2c80
Depends-On: https://review.openstack.org/641805
When we run the run-gitea job, make sure that it runs *after*
the gitea image build job, if the build job ran at all. If
it didn't, we don't need to worry about it.
This has to happen in the project pipeline config because the
job dependency is different in check and gate.
Change-Id: I7cb069a6cd40a4ae8d5cbcdf23e7686b301493a1
These now only run a registry if there isn't already one running
in the buildset, so we can use them here in that configuration.
They also take care of the provides/requires for us, so we can
remove those.
Change-Id: I3b6d825df8d658adcae51ed20a5335c612b7d9f2
Depends-On: https://review.openstack.org/642151
We call the bridge playbook from run-base.yaml to bootstrap bridge,
so that's really where we need to disable the cron installation.
Change-Id: I5f3d604feaca5c1d577636c2d1130eec82a35961
The stacked opendev logo is added to the home page as an svg.
A 120x120 ping is added as the gitea icon. It appears in several
places throughout gitea source code, and therefore it's easier to
just replace it using the same filename and format rather than
updating the templates with a new filename.
Change-Id: I888b8913c7b6a1045975f10240d744d09b9355b0
