Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-29348

Release Nuxeo Server version in JIRA



    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 11.x
    • Component/s: CI/CD


      When releasing a new version of the Nuxeo Server, we want that version to be automatically released in JIRA also.


      As there is not only the Server in NXP, but also other components such as Retention, Glacier, Explorer, ... that follow their own versioning, we want to have dedicated versions for each component.
      For the Server, we will end up with server-11.2, server-11.3, ...
      Explorer for instance will have its own versions, such as explorer-20.0.0, ...

      A server-next JIRA version is created and available. All issues fixed for the next release have server-next as fix version.

      Release Flow

      When we release a new version with the CI pipeline:

      • Create the new version on JIRA: server-X.Y.
      • Retrieve all NXP issues that are on this release (through git commit messages).
      • Update all NXP issues fix version from server-next to server-X.Y.
      • Release the server-X.Y version in JIRA with the current date as release date.

      Notes about Updating NXP Issues Fix Version

      As we are promoting a given build to be a release, all NXP issues resolved with server-next as fix version are not necessarily in the release, they could have been merged and resolved after the promoted build.

      With git we need to find all commits between the latest release and the build we promote to extract all NXP issues. Only those issues will have their fix version updated, other issues will keep server-next.




            • Assignee:
              troger Thomas Roger
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:


                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.