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

XMLWordPrintable

    • Type: Task
    • Resolution: Won't Do
    • Priority: L3 - Default
    • 2.7.0-alpha2, 2.7.0
    • Affects Version/s: None
    • Component/s: 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

            Assignee:
            Unassigned
            Reporter:
            Michael
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: