Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-29981 Describe how to handle MintMaker updates during release
  3. ROX-30215

Document how to handle Renovate during release

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Rox Sprint 4.9C - Global, Rox Sprint 4.9D - Global, Rox Sprint 4.9E - Global, Rox Sprint 4.9F - Global, Rox Sprint 4.9G - Global, Rox Sprint 4.9H - Global, Rox Sprint 4.9I - Global

      Renovate updates in Scanner & Collector in master branch auto-merge. For release branches, the downstream release engineer does the following before a new release candidate is created by the upstream release engineer:

      • check if there are MintMaker changes open and request to merge them,
      • check if there are merged MintMaker changes, tag them,
      • open PR bumping SCANNER_VERSION and COLLECTOR_VERSION.

      This is also required for the first RC. 

       

      There are no automatic merges configured in the Stackrox repositories, ie the downstream release engineer must handle open MintMaker changes by

      • check if there are MintMaker changes open and request to merge them to the release branch.

              rh-ee-tmartens Tom Martensen
              rh-ee-tmartens Tom Martensen
              ACS Automation
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: