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

Parse branch name for JIRA issue

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • jira-plugin
    • None

      Right now Jenkins JIRA plugin has ability to parse commit logs for JIRA issues that are then linked to JIRA. Our workflow is based on per-branch approach, where we create separate branch for each JIRA issue, so the information about issue in this case is not in commit log but in branch name. This makes it impossible for JIRA plugin to know about the issue this build relates to.

      In release builds where several branches are merged into one this is not a problem because Stash pushes all issue keys (PROJ-1, PROJ-2 etc.) into a single commit log I think, but for building development branches where we don't put issue key into a commit message this makes it problematic to link JIRA with Jenkins.

          [JENKINS-33752] Parse branch name for JIRA issue

          Radek Antoniuk added a comment -

          I would say this is correct behavior - it is a standard and good practice to put the JIRA ID in the commit message.
          Branch naming is often different from actual JIRA IDs - i've seen XXX-123_xx, XXX_123_xx etc, which will create a mess in terms of regex matching.
          Additionally, the commit message can actually perform workflow actions (see JIRA's SmartCommits).
          For this reason I would say - "as designed"

          Radek Antoniuk added a comment - I would say this is correct behavior - it is a standard and good practice to put the JIRA ID in the commit message. Branch naming is often different from actual JIRA IDs - i've seen XXX-123_xx, XXX_123_xx etc, which will create a mess in terms of regex matching. Additionally, the commit message can actually perform workflow actions (see JIRA's SmartCommits). For this reason I would say - "as designed"

            Unassigned Unassigned
            noizex Kamil N
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: