From 15a5806bcee550dae3189ecea4875e17161a57e9 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Thu, 30 May 2019 15:57:48 +0200 Subject: [PATCH] Follow opendev renames The sandbox repos moved from openstack-dev to opendev, the zone-opendev.org and zone-zuul-ci.org as well. Follow the rename in this repo. Depends-On: https://review.opendev.org/657277 Change-Id: I31097568e8791cc49c623fc751bcc575268ad148 --- .zuul.yaml | 4 ++-- doc/source/third_party.rst | 12 ++++++------ launch/README | 4 ++-- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/.zuul.yaml b/.zuul.yaml index 6176e9d7cd..163f0b93e7 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -479,8 +479,8 @@ description: | Run the playbook for dns. required-projects: - - openstack-infra/zone-opendev.org - - openstack-infra/zone-zuul-ci.org + - opendev/zone-opendev.org + - opendev/zone-zuul-ci.org nodeset: nodes: - name: bridge.openstack.org diff --git a/doc/source/third_party.rst b/doc/source/third_party.rst index c298430cf6..39d5a1c370 100644 --- a/doc/source/third_party.rst +++ b/doc/source/third_party.rst @@ -339,14 +339,14 @@ For example: .. code-block:: yaml projects: - - name: openstack-dev/ci-sandbox + - name: opendev/ci-sandbox check: - my-sandbox-check test: - my-sandbox-test -In this case, any Gerrit event generated from the ``openstack-dev/ci-sandbox`` project, that matched +In this case, any Gerrit event generated from the ``opendev/ci-sandbox`` project, that matched the ``check`` pipeline would run the ``my-sandbox-check`` job in Jenkins. If the Gerrit event also matched the ``test`` pipeline, Zuul would also invoke the ``my-sandbox-test`` Jenkins job. @@ -375,7 +375,7 @@ set of YAML files and job templating rules. These references provide more detail Testing your CI setup --------------------- -You can use the ``openstack-dev/ci-sandbox`` project to test your external CI +You can use the ``opendev/ci-sandbox`` project to test your external CI infrastructure with OpenStack's Gerrit. By using the sandbox project you can test your CI system without affecting regular OpenStack reviews. @@ -389,11 +389,11 @@ Permissions on your Third Party System When you create your CI account it will have no special permissions. This means it can comment on changes but generally not vote +/-1 Verified on any changes. The exception to this is on the -``openstack-dev/ci-sandbox`` project. Any account is able to vote +/-1 +``opendev/ci-sandbox`` project. Any account is able to vote +/-1 Verified on that account and it provides a way to test your CI's voting abilities before you vote on other projects. -.. _openstack-dev/ci-sandbox: https://opendev.org/openstack-dev/ci-sandbox +.. _opendev/ci-sandbox: https://opendev.org/opendev/ci-sandbox The OpenStack Infrastructure team disables mis-behaving third-party ci accounts at its discretion. This documentation endeavours to outline specific @@ -409,7 +409,7 @@ getting your system re-enabled. You are also welcome to join us in the #openstack-infra irc channel on freenode to discuss your situation. In order to get your Third Party CI account to have voting permissions on -repos in gerrit in addition to ``openstack-dev/ci-sandbox`` you have a greater +repos in gerrit in addition to ``opendev/ci-sandbox`` you have a greater chance of success if you follow these steps: * Set up your system and test it according to "Testing your CI setup" outlined diff --git a/launch/README b/launch/README index 63f0914a44..e2c3382a47 100644 --- a/launch/README +++ b/launch/README @@ -17,7 +17,7 @@ Manually add the hostname to DNS (the launch script does not do so automatically, but it prints the commands to run). Note that for *.opendev.org hosts you'll only be able to add the reverse dns records via the printed commands. Forward A and AAAA records should -be added to openstack-infra/zone-opendev.org/zones/opendev.org/zone.db. +be added to opendev/zone-opendev.org/zones/opendev.org/zone.db. In order for Ansible to be able to send out the Puppet updates, you also need the puppetmaster to accept the root SSH key for the @@ -30,7 +30,7 @@ Then you can log out. Finally we need to add the host to our static inventory file so that the periodic ansible runs (which can run puppet) see the new host. -Update openstack-infra/system-config/inventory/openstack.yaml to +Update opendev/system-config/inventory/openstack.yaml to include the appropriate hostname and IP address details. Add DNS Records