Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1878

Release optimize example repository when Optimize is released

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha2
    • Component/s: backend
    • Labels:
      None

      Description

      AT:

      • there are tags 2.2 and 2.3 for the optimize example repo
      • each tag is linked in the readme, similiar to how it's done in the camunda bpm example repo
      • when the Optimize release build is triggered it also releases the example repository for a minor release by:
        • adding the new branch entry in the readme file
        • creating a new branch for the released version, with the release version in the pom file
        • increasing the pom version to the snapshot version on master

      Hint:
      Use a second job to release the example repository and then after the original finished successfully you trigger the release example repo. Have a look at how this can be achieved on Jenkins:
      https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.helpers.publisher.PublisherContext.downstream

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              johannes.heinemann Johannes Heinemann
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: