diff mbox series

[yocto-docs,v2,1/2] Update autobuilder URLs to valkyrie

Message ID 20250117-update-autobuilder-link-v2-1-3ca2d22ab24a@bootlin.com
State Under Review
Headers show
Series Update the autobuilder links to valkyrie | expand

Commit Message

Antonin Godard Jan. 17, 2025, 10:08 a.m. UTC
We have moved to Valkyrie which is hosted on
https://autobuilder.yoctoproject.org/valkyrie. Update the URL in the
documentation.

Also, the YOCTO_AB_URL macro was used in a single location in the
documentation so replace it by the :yocto_ab: custom extlink and remove
the macro.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/poky.yaml.in                           | 1 -
 documentation/ref-manual/release-process.rst         | 2 +-
 documentation/test-manual/reproducible-builds.rst    | 8 ++++----
 documentation/test-manual/test-process.rst           | 2 +-
 documentation/test-manual/understand-autobuilder.rst | 2 +-
 5 files changed, 7 insertions(+), 8 deletions(-)

Comments

Quentin Schulz Jan. 17, 2025, 10:14 a.m. UTC | #1
Hi Antonin,

On 1/17/25 11:08 AM, Antonin Godard via lists.yoctoproject.org wrote:
> We have moved to Valkyrie which is hosted on
> https://autobuilder.yoctoproject.org/valkyrie. Update the URL in the
> documentation.
> 
> Also, the YOCTO_AB_URL macro was used in a single location in the
> documentation so replace it by the :yocto_ab: custom extlink and remove
> the macro.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin
diff mbox series

Patch

diff --git a/documentation/poky.yaml.in b/documentation/poky.yaml.in
index 0933cbbd351985899ecaea94ae42748bd7ba1753..d045ff596e6d7d7d46be373078e8bb8b38483267 100644
--- a/documentation/poky.yaml.in
+++ b/documentation/poky.yaml.in
@@ -12,7 +12,6 @@  DISTRO_REL_TAG : "yocto-5.1"
 DOCCONF_VERSION : "dev"
 BITBAKE_SERIES : ""
 YOCTO_DL_URL : "https://downloads.yoctoproject.org"
-YOCTO_AB_URL : "https://autobuilder.yoctoproject.org"
 YOCTO_RELEASE_DL_URL : "&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;"
 MIN_PYTHON_VERSION : "3.8.0"
 MIN_TAR_VERSION : "1.28"
diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst
index c4452228a70268649f56ed3ecfde1f7418926fc6..639921b9f65fe3908e26ae69569eddc677efa322 100644
--- a/documentation/ref-manual/release-process.rst
+++ b/documentation/ref-manual/release-process.rst
@@ -190,7 +190,7 @@  effort has been made to automate the tests so that more people can use
 them and the Yocto Project development team can run them faster and more
 efficiently.
 
-The Yocto Project's main Autobuilder (&YOCTO_AB_URL;) publicly tests each Yocto
+The Yocto Project's main :yocto_ab:`Autobuilder <>` publicly tests each Yocto
 Project release's code in the :oe_git:`openembedded-core </openembedded-core>`,
 :yocto_git:`poky </poky>` and :oe_git:`bitbake </bitbake>` repositories. The
 testing occurs for both the current state of the "master" branch and also for
diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst
index d581155eb2a45e36c4d54fb1ad8b5d15980bc508..7769a85d515d3fd4b06ad2ef76239aa774eb8af3 100644
--- a/documentation/test-manual/reproducible-builds.rst
+++ b/documentation/test-manual/reproducible-builds.rst
@@ -121,10 +121,10 @@  The project's current reproducibility status can be seen at
 
 You can also check the reproducibility status on supported host distributions:
 
--  CentOS: :yocto_ab:`/typhoon/#/builders/reproducible-centos`
--  Debian: :yocto_ab:`/typhoon/#/builders/reproducible-debian`
--  Fedora: :yocto_ab:`/typhoon/#/builders/reproducible-fedora`
--  Ubuntu: :yocto_ab:`/typhoon/#/builders/reproducible-ubuntu`
+-  CentOS: :yocto_ab:`/valkyrie/#/builders/reproducible-centos`
+-  Debian: :yocto_ab:`/valkyrie/#/builders/reproducible-debian`
+-  Fedora: :yocto_ab:`/valkyrie/#/builders/reproducible-fedora`
+-  Ubuntu: :yocto_ab:`/valkyrie/#/builders/reproducible-ubuntu`
 
 ===============================
 Can I test my layer or recipes?
diff --git a/documentation/test-manual/test-process.rst b/documentation/test-manual/test-process.rst
index 7bec5ba8285cda1d6b0157c38eb693fde7d0e557..945b56830fc3f7368a73b4655f8ea325a2d780a7 100644
--- a/documentation/test-manual/test-process.rst
+++ b/documentation/test-manual/test-process.rst
@@ -20,7 +20,7 @@  helps review and test patches and this is his testing tree).
 We have two broad categories of test builds, including "full" and
 "quick". On the Autobuilder, these can be seen as "a-quick" and
 "a-full", simply for ease of sorting in the UI. Use our Autobuilder
-:yocto_ab:`console view </typhoon/#/console>` to see where we manage most
+:yocto_ab:`console view </valkyrie/#/console>` to see where we manage most
 test-related items.
 
 Builds are triggered manually when the test branches are ready. The
diff --git a/documentation/test-manual/understand-autobuilder.rst b/documentation/test-manual/understand-autobuilder.rst
index 6b4fab4f0b2be5a6806db0982e257b9059d15fa7..7f4d1be3cd477cfe759a44efe67d65c97422a7ed 100644
--- a/documentation/test-manual/understand-autobuilder.rst
+++ b/documentation/test-manual/understand-autobuilder.rst
@@ -10,7 +10,7 @@  Execution Flow within the Autobuilder
 The "a-full" and "a-quick" targets are the usual entry points into the
 Autobuilder and it makes sense to follow the process through the system
 starting there. This is best visualized from the :yocto_ab:`Autobuilder
-Console view </typhoon/#/console>`.
+Console view </valkyrie/#/console>`.
 
 Each item along the top of that view represents some "target build" and
 these targets are all run in parallel. The 'full' build will trigger the