From ac670dce6d2f99176306815dabaa65fe9e0de575 Mon Sep 17 00:00:00 2001 From: davyyy Date: Thu, 16 Nov 2017 21:27:03 +0800 Subject: [PATCH] Update URL from "http" to "https" Most of them can still be visited through http, but the following one is necessary to update, so I change them all by this chance. $ git clone http://git.openstack.org/openstack/tempest Change-Id: I2b4da0670b599666e7151bddfff0fa6655640bc4 --- HACKING.rst | 4 ++-- README.rst | 6 +++--- REVIEWING.rst | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/HACKING.rst b/HACKING.rst index 8407734d33..c942cb1432 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -84,7 +84,7 @@ For example ``self.assertIn`` can include the whole set. It is recommended to use testtools `matcher`_ for the more tricky assertions. You can implement your own specific `matcher`_ as well. -.. _matcher: http://testtools.readthedocs.org/en/latest/for-test-authors.html#matchers +.. _matcher: https://testtools.readthedocs.org/en/latest/for-test-authors.html#matchers If the test case fails you can see the related logs and the information carried by the exception (exception class, backtrack and exception info). @@ -178,7 +178,7 @@ negative testing should be handled with project function tests. All negative tests should be based on `API-WG guideline`_ . Such negative tests can block any changes from accurate failure code to invalid one. -.. _API-WG guideline: http://specs.openstack.org/openstack/api-wg/guidelines/http.html#failure-code-clarifications +.. _API-WG guideline: https://specs.openstack.org/openstack/api-wg/guidelines/http.html#failure-code-clarifications If facing some gray area which is not clarified on the above guideline, propose a new guideline to the API-WG. With a proposal to the API-WG we will be able to diff --git a/README.rst b/README.rst index c67362a781..c087f292c2 100644 --- a/README.rst +++ b/README.rst @@ -2,7 +2,7 @@ Team and repository tags ======================== -.. image:: http://governance.openstack.org/badges/tempest.svg +.. image:: https://governance.openstack.org/badges/tempest.svg :target: https://governance.openstack.org/tc/reference/tags/index.html .. Change things from this point on @@ -61,7 +61,7 @@ as it is simpler, and quicker to work with. #. You first need to install Tempest. This is done with pip after you check out the Tempest repo:: - $ git clone http://git.openstack.org/openstack/tempest + $ git clone https://git.openstack.org/openstack/tempest $ pip install tempest/ This can be done within a venv, but the assumption for this guide is that @@ -133,7 +133,7 @@ For more details refer to the library documentation here: :ref:`library` Release Versioning ------------------ -`Tempest Release Notes `_ +`Tempest Release Notes `_ shows what changes have been released on each version. Tempest's released versions are broken into 2 sets of information. Depending on diff --git a/REVIEWING.rst b/REVIEWING.rst index 7d28320b47..5e08a6b2fb 100644 --- a/REVIEWING.rst +++ b/REVIEWING.rst @@ -2,7 +2,7 @@ Reviewing Tempest Code ====================== To start read the `OpenStack Common Review Checklist -`_ +`_ Ensuring code is executed @@ -16,7 +16,7 @@ not be accepted. If a new test is added that depends on a new config option (like a feature flag), the commit message must reference a change in DevStack or DevStack-Gate that enables the execution of this newly introduced test. This reference could -either be a `Cross-Repository Dependency `_ or a simple link to a Gerrit review.