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

Configurable merge message

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
    • Environment:
      Linux Ubuntu 3.2.0-58-generic x86_64
      Jenkins ver. 1.546
      Git Plugin 2.0
      Git server plugin 1.3
      Jenkins GIT client plugin 1.6.2
    • Similar Issues:

      Description

      I am using the "automatic merging" functionality as described here: "Using Git, Jenkins and pre-build branch merging" ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures ). The merging is working well. What I wanted is to have some readable information about which two branches are integratet within a commited merge result. The current comments look like:

      "Merge commit '6cb5a448d66ab30aca2257123e7c0396fa9fddac' into HEAD"

      I would be very useful if more informative commit/push comments could be written like:

      "Merged branch 'release/2.4.7' into branch 'develop'. Merge commit '6cb5a448d66ab30aca2257123e7c0396fa9f8dac' into HEAD"

      I have not found any customize functionality for this. And using the tag function for this would be an overhead, since "tons" of tags would be created.

      Regards

        Attachments

          Activity

          Hide
          mikenicholson Mike Nicholson added a comment -

          Our team has run into this same issue. When merging manually we use branch names so the merge message is automatically populated as

          "Merge <feature-branch> into develop"

          The feature branch name is very useful in large projects since it provides significant context around what was merged. We would be happy with either a customized message where we could insert our own message or if the default merge message was changed to use branch names.

          Show
          mikenicholson Mike Nicholson added a comment - Our team has run into this same issue. When merging manually we use branch names so the merge message is automatically populated as "Merge <feature-branch> into develop" The feature branch name is very useful in large projects since it provides significant context around what was merged. We would be happy with either a customized message where we could insert our own message or if the default merge message was changed to use branch names.
          Hide
          dhartrampf Dennis Hartrampf added a comment -

          We have the same problem here. I totally agree with Mike Nicholson
          It would be of a great benefit to us.

          Show
          dhartrampf Dennis Hartrampf added a comment - We have the same problem here. I totally agree with Mike Nicholson It would be of a great benefit to us.
          Hide
          robertberta Robert Berta added a comment -

          Please solve this , I like Mike Nicholson suggestion.

          Show
          robertberta Robert Berta added a comment - Please solve this , I like Mike Nicholson suggestion.

            People

            • Assignee:
              Unassigned
              Reporter:
              olibolib m r
            • Votes:
              10 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated: