Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-475

Automate built artifacts release to GitHub Releases

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Out of Date
    • None
    • None
    • None
    • None

    Description

      The current setup of the suite of our multi-platform Jenkins jobs builds all the release artifacts without pushing them anywhere.

      The person doing the release has to download all these built artifacts and upload them to the jboss.org. Next, one has to adjust Magnolia Release pages, Release notes and links. It is tedious, it involves extensive Magnolia and Docbook hacking and we should get rid of it in order to streamline the release process.

      MODCLUSTER-474 introduced GitHub Releases, e.g. 1.3.1.Final on GitHub. This particular "demo" was uploaded manually, although it could be nicely automated either with ghr or github-release. The only possible downside is the exposure of our GitHub keys to the build environment. It could be easily addressed by having the mod_cluster-release Jenkins job tied to a one and only one specific private slave. Other suggestions are welcome though.

      Also, let's avoid https://xkcd.com/1319/

      Attachments

        Activity

          People

            rhn-engineering-jclere Jean-Frederic Clere
            mbabacek1@redhat.com Michal Karm
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: