From my point of view it would allow scripting that I can't do now. Tried even EnvInject with little success.

Our setup is a bit unique:

  • Multiple git repos (master and team repos)
  • Release branches with version numbers embedded (release-1.0, release-1.1, release-2.0, ...)
  • Team release branches (possibly across repos) - (team1-1.0, team1-1.1, team2-1.0,...)

There are several use-cases I am trying to automate.

Here is one of them:

  • We monitor release-* branches (yes, wildcard in the job configuration).
  • I need to push that release-* branch into team1-* branch with the same version number. Basically expand the wildcard and do search/replace.

Other possible use case:

  • Merging release-* branch into a later release as part of automation. (release-1.0.1 => release-1.1 or release 2.0)
    This presents a possible conditional step. Lets say that we don't push 1.0 release changes upstream anymore, so then we can create an exclusion rule to exclude 1.0 from the release "upgrade" merge/push.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to