From e8f8eb377c5bb841edaa1418af618ed8055c1617 Mon Sep 17 00:00:00 2001 From: Ross Date: Fri, 14 Nov 2025 22:48:22 -0500 Subject: [PATCH 1/3] Update link for jenkins --- jenkins/getting-started.rst | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/jenkins/getting-started.rst b/jenkins/getting-started.rst index 627b40ce..c616f78a 100644 --- a/jenkins/getting-started.rst +++ b/jenkins/getting-started.rst @@ -1,28 +1,28 @@ ########################################### -Jenkins rubin-ci.slac.stanford.edu Overview +Jenkins ci.lsst.cloud Overview ########################################### -Data Management operates a Jenkins continuous integration cluster at https://rubin-ci.slac.stanford.edu. +Data Management operates a Jenkins continuous integration cluster at https://ci.lsst.cloud. You will typically use Jenkins to run the ``stack-os-matrix`` job to build and run unit tests in the LSST Stack as part of `DM's development workflow `_. See :doc:`/stack/jenkins-stack-os-matrix` for details. Logging in ========== -Log into Jenkins by visiting https://rubin-ci.slac.stanford.edu/blue and authenticate with your GitHub credentials. -Any member of the `lsst`_, `lsst-dm`_, or `lsst-sqre`_ GitHub organizations is authorized to use https://rubin-ci.slac.stanford.edu. +Log into Jenkins by visiting https://ci.lsst.cloud/blue and authenticate with your GitHub credentials. +Any member of the `lsst`_, `lsst-dm`_, or `lsst-sqre`_ GitHub organizations is authorized to use https://ci.lsst.cloud. See the :doc:`/team/onboarding` for more information. Using the Jenkins dashboard =========================== -This section summarizes how to use the Jenkins dashboard, which is the first view you see when browsing to https://rubin-ci.slac.stanford.edu/blue. +This section summarizes how to use the Jenkins dashboard, which is the first view you see when browsing to https://ci.lsst.cloud/blue. `Jenkins's own dashboard documentation `_ provides additional information. Browsing Jenkins jobs --------------------- -From https://rubin-ci.slac.stanford.edu/blue, you see a listing of Jenkins jobs. +From https://ci.lsst.cloud/blue, you see a listing of Jenkins jobs. Each job fulfills a different purpose, see :ref:`jenkins-jobs`. To access a job, click on the job's name. @@ -31,7 +31,7 @@ This takes you to a page where you can run the job and review past runs. Favoriting Jenkins jobs ----------------------- -From the https://rubin-ci.slac.stanford.edu/blue dashboard, you can click on the star icon next to any job. +From the https://ci.lsst.cloud/blue dashboard, you can click on the star icon next to any job. This will favorite the Job. Favorited jobs appear at the top of the homepage, before other jobs. @@ -40,7 +40,7 @@ We recommend that you favorite the ``stack-os-matrix`` job. Searching for Jenkins jobs -------------------------- -From the https://rubin-ci.slac.stanford.edu/blue dashboard, you can filter the listing of jobs by using the search box at the top of the page. +From the https://ci.lsst.cloud/blue dashboard, you can filter the listing of jobs by using the search box at the top of the page. Jenkins jobs are organized in directories, so it's helpful to search by directory prefix to find the right job. The directories are: @@ -186,13 +186,13 @@ More resources .. _`lsst`: https://github.com/lsst .. _`lsst-dm`: https://github.com/lsst-dm .. _`lsst-sqre`: https://github.com/lsst-sqre -.. _`stack-os-matrix`: https://rubin-ci.slac.stanford.edu/blue/organizations/jenkins/stack-os-matrix/activity -.. _`science-pipelines/lsst_distrib`: https://rubin-ci.slac.stanford.edu/blue/organizations/jenkins/science-pipelines%2Flsst_distrib/activity -.. _`qserv/dax_webserv`: https://rubin-ci.slac.stanford.edu/blue/organizations/jenkins/qserv%2Fdax_webserv/activity -.. _`qserv/qserv_distrib`: https://rubin-ci.slac.stanford.edu/blue/organizations/jenkins/qserv%2Fqserv_distrib/activity +.. _`stack-os-matrix`: https://ci.lsst.cloud/blue/organizations/jenkins/stack-os-matrix/activity +.. _`science-pipelines/lsst_distrib`: https://ci.lsst.cloud/blue/organizations/jenkins/science-pipelines%2Flsst_distrib/activity +.. _`qserv/dax_webserv`: https://ci.lsst.cloud/blue/organizations/jenkins/qserv%2Fdax_webserv/activity +.. _`qserv/qserv_distrib`: https://ci.lsst.cloud/blue/organizations/jenkins/qserv%2Fqserv_distrib/activity .. _`Jenkins documentation`: https://jenkins.io/doc/book/blueocean/ .. _`Jenkins dashboard documentation`: https://jenkins.io/doc/book/blueocean/dashboard/ .. _`lsst-dm/jenkins-dm-jobs`: https://github.com/lsst-dm/jenkins-dm-jobs -.. _`#dm-jenkins`: https://lsstc.slack.com/messages/C2NCSTY3A +.. _`#dm-jenkins`: https://rubin-obs.slack.com/archives/C07Q45N5SDV .. _`search the channel listing`: https://get.slack.help/hc/en-us/articles/205239967-Browse-and-join-channels .. _`mute the channel`: https://get.slack.help/hc/en-us/articles/204411433-Mute-a-channel From 9862afc241cb03f85f93a4366b63ec04096ff45b Mon Sep 17 00:00:00 2001 From: Ross Date: Fri, 14 Nov 2025 22:51:53 -0500 Subject: [PATCH 2/3] Update link for eups.lsst.codes to eups.lsst.cloud --- stack/conda.rst | 2 +- stack/eups-tutorial.rst | 6 +++--- work/backports.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/stack/conda.rst b/stack/conda.rst index d623e974..9c019812 100644 --- a/stack/conda.rst +++ b/stack/conda.rst @@ -183,6 +183,6 @@ New builds of ``rubin-env`` (without updating its version) can always be used to "Exact" environments -------------------- -The conda environments used by Jenkins to build nightly, weekly, and official release tarballs are preserved as ``conda list --explicit`` outputs in ``eups.lsst.codes``. +The conda environments used by Jenkins to build nightly, weekly, and official release tarballs are preserved as ``conda list --explicit`` outputs in ``eups.lsst.cloud``. These can be used in place of the ``rubin-env`` metapackage to exactly reproduce a build for consistency in production or for debugging. Both ``newinstall`` and ``lsstsw`` allow specification of an eups tag to retrieve the exact environment used when that tag was published. diff --git a/stack/eups-tutorial.rst b/stack/eups-tutorial.rst index 30b40c8a..7d8f92ef 100644 --- a/stack/eups-tutorial.rst +++ b/stack/eups-tutorial.rst @@ -359,11 +359,11 @@ shares many concepts. :command:`eups distrib` reads details about available packages from a remote server. The appropriate location for finding LSST software is -https://eups.lsst.codes/stack/src. We can use :command:`eups distrib list` to +https://eups.lsst.cloud/stack/src. We can use :command:`eups distrib list` to list available software, and :command:`eups distrib install` to install it:: % eups distrib path - https://eups.lsst.codes/stack/src + https://eups.lsst.cloud/stack/src % eups distrib list lsst_apps lsst_apps generic 8.0.0.1+2 @@ -375,7 +375,7 @@ list available software, and :command:`eups distrib install` to install it:: Note that :command:`eups distrib list` does not list tags, even though :command:`eups distrib install` accepts a tag as a command line option (``-t v11_0``). The most convenient way to see a list of available tags is to visit -the distribution server (https://eups.lsst.codes/stack/src/tags) in a web +the distribution server (https://eups.lsst.cloud/stack/src/tags) in a web browser. Further Information diff --git a/work/backports.rst b/work/backports.rst index fda4dec3..495d344f 100644 --- a/work/backports.rst +++ b/work/backports.rst @@ -57,7 +57,7 @@ What next? Check that it cleanly builds via scons. There should be a latest shared v23.0.0.rcN stack on lsst-devl. Run Jenkins. When running Jenkins, build against the release branch and rc1 even if later rcNs exist. The default ``SPLENV_REF`` value (the rubin-env conda metapackage version) may no longer be appropriate for ``v23.0.x``. - If you are unsure of the recommended env for the release, see the :external+pipelines:ref:`release documentation page `, the `release tag files `__. or the ``env_name`` files nested under ``/sdf/group/rubin/sw/tag/`` at USDF. + If you are unsure of the recommended env for the release, see the :external+pipelines:ref:`release documentation page `, the `release tag files `__. or the ``env_name`` files nested under ``/sdf/group/rubin/sw/tag/`` at USDF. .. code-block:: bash From ef050efc201d74570b28212fc1110616bda5a9e7 Mon Sep 17 00:00:00 2001 From: Ross Date: Fri, 14 Nov 2025 23:03:13 -0500 Subject: [PATCH 3/3] Update rubin-env version --- stack/conda.rst | 8 ++++---- team/drp.rst | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/stack/conda.rst b/stack/conda.rst index 9c019812..957f94fc 100644 --- a/stack/conda.rst +++ b/stack/conda.rst @@ -45,8 +45,8 @@ To change the ``rubin-env``: .. code-block:: bash conda deactivate # make sure you do not run this inside an existing conda environment - ./bin/deploy -v 8.0.0 # or any other rubin env - source bin/envconfig -n lsst-scipipe-8.0.0 + ./bin/deploy -v 12.0.0 # or any other rubin env + source bin/envconfig -n lsst-scipipe-12.0.0 rebuild lsst_apps # This could be any branch or product you want to use @@ -71,8 +71,8 @@ To change the ``rubin-env``: conda deactivate # make sure you do not run this inside an existing conda environment # adding conda-forge/label/rubin-env_dev allows to install rubin-env_dev export LSST_CONDA_CHANNELS="nodefaults conda-forge/label/rubin-env_dev conda-forge" - ./bin/deploy -v 9.0.0dev # or any other rubin env - source bin/envconfig -n lsst-scipipe-9.0.0dev + ./bin/deploy -v 12.0.0dev # or any other rubin env + source bin/envconfig -n lsst-scipipe-12.0.0dev rebuild lsst_apps # This could be any branch or product you want to use .. _rubin-env-dependency-versioning: diff --git a/team/drp.rst b/team/drp.rst index beb4ec3d..ca53a9c6 100644 --- a/team/drp.rst +++ b/team/drp.rst @@ -98,7 +98,7 @@ If you wish to use a different Rubin Environment, you can do so by first setting .. code-block:: shell - export LSST_CONDA_ENV_NAME="lsst-scipipe-9.0.0" + export LSST_CONDA_ENV_NAME="lsst-scipipe-12.0.0" source /scratch/gpfs/LSST/stack/loadLSST.sh setup lsst_distrib -t