Skip to content

Commit

Permalink
Update Conda job instructions to include naming convention.
Browse files Browse the repository at this point in the history
  • Loading branch information
rbovill committed Oct 16, 2024
1 parent cedf331 commit ea92dbb
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions doc/development-guidelines/conda/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,12 @@ Adding the Job

Add the job by creating a new item on the Jenkins server and selecting Multibranch Pipeline.

The Daily Workflows assume that Conda packaging jobs follow a very specific naming convention. The name should begin with a meaningful string, usually the package name, with NO special character. The rest of the job name should just be the string ``_conda_package``, i.e.

``<PackageName>_conda_package``

This ensures the job is displyed in the ``Conda Jobs`` view in Jenkins, as well being included in the Daily Workflows, once the broker job is updated to add this new Conda packaging build. Simply make a request to the build engineer to get the job added properly.

.. image:: /images/jenkins-conda-adding-the-job-0.png

In ``Branch Sources`` click the github source selection and type in the path of the repo into the ``Respository HTTPS URL``.
Expand Down

0 comments on commit ea92dbb

Please sign in to comment.