Skip to content

DM-52833: Update link for jenkins #734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roceb merged 3 commits into from
Nov 16, 2025
Merged

DM-52833: Update link for jenkins #734

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e8f8eb3
Update link for jenkins
Nov 15, 2025
9862afc
Update link for eups.lsst.codes to eups.lsst.cloud
Nov 15, 2025
ef050ef
Update rubin-env version
Nov 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions jenkins/getting-started.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 <processes/workflow.rst>`_.
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 <https://jenkins.io/doc/book/blueocean/dashboard/>`_ 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.
Expand All @@ -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.

Expand All @@ -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:
Expand Down Expand Up @@ -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
10 changes: 5 additions & 5 deletions stack/conda.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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


Expand All @@ -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:
Expand Down Expand Up @@ -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.
6 changes: 3 additions & 3 deletions stack/eups-tutorial.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down
2 changes: 1 addition & 1 deletion team/drp.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <old_version_tag>

Expand Down
2 changes: 1 addition & 1 deletion work/backports.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <release-history>`, the `release tag files <https://eups.lsst.codes/stack/src/tags/>`__. 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 <release-history>`, the `release tag files <https://eups.lsst.cloud/stack/src/tags/>`__. or the ``env_name`` files nested under ``/sdf/group/rubin/sw/tag/`` at USDF.

.. code-block:: bash

Expand Down