# Please update the pipeline docs to reflect the single commit in DM-22027

XMLWordPrintable

#### Details

• Type: Story
• Status: Won't Fix
• Resolution: Done
• Fix Version/s: None
• Component/s:
• Labels:
None
• Team:
Architecture
• Urgent?:
No

#### Description

The changes I made in DM-22027 correct some documentation errors that are relevant for v19. It would be good if those changes were reflected in the version of the docs that are shown online at pipelines.lsst.io.

I don't know if it's possible to update the docs separately from the release, or if we need to issue a point release to do this.

#### Activity

Hide
Gabriele Comoretto added a comment -

I have created the ticket branch based on 19.0.0 and copied (cherry-pick) the changes into it.

I executed the run-rebuild job (job 1844, build-id 4636) but I got an error when publishing the eups-tag. the same error appears If I try to push a eups package using run-publish (job 2867).

Not sure if there are other ways to move forward.

Show
Gabriele Comoretto added a comment - I have created the ticket branch based on 19.0.0 and copied (cherry-pick) the changes into it. I executed the run-rebuild job (job 1844, build-id 4636) but I got an error when publishing the eups-tag. the same error appears If I try to push a eups package using run-publish (job 2867). Not sure if there are other ways to move forward.
Hide
Gabriele Comoretto added a comment -

It seems that the second build (run-publish 2867) managed to create the eups-tag.

However, the documenteer execution requires the existence of the corresponding lsst_distrib Docker image.

At this point, it is worth for the DM-CCB considering having a 19.0.1 patch, instead of applying manually all the steps.

The developer guide

https://developer.lsst.io/stack/building-pipelines-lsst-io-with-documenteer-job.html

also sais the following about the documenteer job:

 You can’t use this Jenkins CI job to test development branches of packages with the pipelines.lsst.io site build. This Jenkins CI job always uses packages corresponding to a released EUPS tag (such as a daily, weekly, or stable release). Only the branch of the pipelines_lsst_io repository can be modified.

Show
Gabriele Comoretto added a comment - It seems that the second build (run-publish 2867) managed to create the eups-tag. However, the documenteer execution requires the existence of the corresponding lsst_distrib Docker image. At this point, it is worth for the DM-CCB considering having a 19.0.1 patch, instead of applying manually all the steps. The developer guide https://developer.lsst.io/stack/building-pipelines-lsst-io-with-documenteer-job.html also sais the following about the documenteer job: You can’t use this Jenkins CI job to test development branches of packages with the pipelines.lsst.io site build. This Jenkins CI job always uses packages corresponding to a released EUPS tag (such as a daily, weekly, or stable release). Only the branch of the pipelines_lsst_io repository can be modified.
Hide
Gabriele Comoretto added a comment -

As discussed in the previous release, this issue will be closed as "Won't Fix".

Show
Gabriele Comoretto added a comment - As discussed in the previous release, this issue will be closed as "Won't Fix".

#### People

Assignee:
Gabriele Comoretto
Reporter:
John Parejko
Watchers:
Gabriele Comoretto, John Parejko, John Swinbank, Jonathan Sick, Kian-Tat Lim, Leanne Guy, Tim Jenness, Wil O'Mullane