Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51658

Plugin POM should automatically run reincrementalify after the release

XMLWordPrintable

      Proposal:

      • After the completion of maven-release-plugin, run
        • the reincrementalify goal
        • commit POM changes as new commit
        • Do another push to SCM

      Everything can be implemented as a single Maven Mojo (e.g. "incrementals-release")

      There is a risk of some edge cases, but it would help plugin developers a lot to keep their master branches release-ready at any time. It's also important for all CD-alike flows which may break if they do not reincrementalify.

          [JENKINS-51658] Plugin POM should automatically run reincrementalify after the release

          Jesse Glick added a comment -

          Was suggested in PR 2 to use a completionGoals configuration parameter. Needs evaluation.

          Jesse Glick added a comment - Was suggested in PR 2 to use a completionGoals configuration parameter. Needs evaluation.

          Joseph Petersen (old) added a comment - - edited

          `completionGoals` avoids the extra commit and push and makes it part of the `[maven-release-plugin] prepare for next development iteration` commit which seems like the best of both worlds

          See https://github.com/jenkinsci/kotlin-v1-stdlib-jdk8-plugin/commit/afc674665f767aeec664536c8b6fb64961fda48f

          Joseph Petersen (old) added a comment - - edited `completionGoals` avoids the extra commit and push and makes it part of the ` [maven-release-plugin] prepare for next development iteration` commit which seems like the best of both worlds See  https://github.com/jenkinsci/kotlin-v1-stdlib-jdk8-plugin/commit/afc674665f767aeec664536c8b6fb64961fda48f

          Jesse Glick added a comment -

          All PRs now merged. I am not inclined to bother trying to consume the jenkinsci/pom update yet, as it should have no practical impact (only jenkinsci/jenkins is incrementalified using it, and kohsuke already runs reincrementalification in his release script); the important part was to get a plugin-pom release cut which uses it, and that has happened.

          Jesse Glick added a comment - All PRs now merged. I am not inclined to bother trying to consume the jenkinsci/pom update yet, as it should have no practical impact (only jenkinsci/jenkins is incrementalified using it, and kohsuke already runs reincrementalification in his release script); the important part was to get a plugin-pom release cut which uses it, and that has happened.

            jetersen Joseph Petersen
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: