Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-13695

Should update documentation in regard to Jenkins way to create and publish eups tags for third-party packages

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: DM
    • Labels:
    • Team:
      SQuaRE

      Description

      This page mentions 'lsstsw' user required for logging into lsst-dev01: 

      https://developer.lsst.io/build-ci/third_party.html

      then a few steps beyond.

      The Jenkins way is much easier, and should be added to our documention:

      https://ci.lsst.codes/job/release/job/build-publish/build?delay=0sec

       

       

       

        Attachments

          Issue Links

            Activity

            Hide
            jsick Jonathan Sick added a comment -

            Joshua Hoblitt is suggesting we delete everything below git push --tags on that page and replace it with “Contact the release manager/Josh” rather than directing developers to run build-publish.

            Show
            jsick Jonathan Sick added a comment - Joshua Hoblitt is suggesting we delete everything below git push --tags on that page and replace it with “Contact the release manager/Josh” rather than directing developers to run build-publish .
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            +1

            Show
            jhoblitt Joshua Hoblitt added a comment - +1
            Hide
            fritzm Fritz Mueller added a comment -

            Okay, I guess? As long as there is a commitment to rapid response on such requests so developers don't become blocked on something they could do self-serve?

            Out of curiosity, though: the existing self-serve tooling seems awesome and completely functional – why not document it?

            Show
            fritzm Fritz Mueller added a comment - Okay, I guess? As long as there is a commitment to rapid response on such requests so developers don't become blocked on something they could do self-serve? Out of curiosity, though: the existing self-serve tooling seems awesome and completely functional – why not document it?
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            I don't want to encourage its use by anyone that doesn't truly need to use such functionality.  There aren't currently any safety mechanisms... such as any release tag could be written over by accident.

            Show
            jhoblitt Joshua Hoblitt added a comment - I don't want to encourage its use by anyone that doesn't truly need to use such functionality.  There aren't currently any safety mechanisms... such as any release tag could be written over by accident.
            Hide
            fritzm Fritz Mueller added a comment -

            Okay, I see

            Show
            fritzm Fritz Mueller added a comment - Okay, I see
            Hide
            tjenness Tim Jenness added a comment -

            Closing this because it looks like the work was done by Kian-Tat Lim on DM-13263 (or at least all the text discussed above was removed then).

            Show
            tjenness Tim Jenness added a comment - Closing this because it looks like the work was done by Kian-Tat Lim on DM-13263 (or at least all the text discussed above was removed then).

              People

              Assignee:
              jsick Jonathan Sick
              Reporter:
              kennylo Kenny Lo
              Watchers:
              Fritz Mueller, Jonathan Sick, Joshua Hoblitt, Kenny Lo, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins Builds

                  No builds found.