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

"Release optimize/example repo" build pipeline version setting refactoring

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: L3 - Default L3 - Default
    • 2.7.0-alpha2, 2.7.0
    • None
    • backend
    • None

      Context:
      in the Release Optimize and Release Example Repo jenkins build pipelines the versions are set via shell, using e.g. 

      sed -i "s/<\\/upgrade.versions>/,${params.RELEASE_VERSION}<\\/upgrade.versions>/g" pom.xml

      This should be set via maven directly instead of externally in a "magical" way.

      AT:

      • the versions are correctly set on release
      • the version params are passed via maven instead of externally through the shell

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              michael.wagner Michael
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: