You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our organisation have implemented a Jenkins pipeline library. This library perform a JIRA integration. We implement a check at build time to force commit message template to refer issues of type defect or story. All issue types (Epic and subtasks) other could not be referred by commit for specific reason.
So in general we have commit that respect a precise template but we are using bitbucket and to close a PR it propose:
use a Merge commit, commit respect the template message except the merge commit that Start with Merged pull request.... and the PR title could refers to subtask or EPIC (here the problem)
Fastforward, every commit message was already check
Squash commit let developer choose the message (they usually dont care too much and will use the proposed message that is equals to the Merge commit)
I would to be able to exclude the merge commits to gather JIRA issues. If I use ignoreCommitsIfMessageMatches that start with Merged also PR merged with squash strategy are ignore.
For our scrum merge commit are not important to determinate which issue are in a release.
The merge commit information is already there so it should be possible performa simple filter.
The best thing would be able to pass a callable (this is possible also in jenkins pipeline) to filter on Commit fields. Otherwise I have to ignore gathered issues and filter commit to get issue using the issue pattern.
The text was updated successfully, but these errors were encountered:
Our organisation have implemented a Jenkins pipeline library. This library perform a JIRA integration. We implement a check at build time to force commit message template to refer issues of type defect or story. All issue types (Epic and subtasks) other could not be referred by commit for specific reason.
So in general we have commit that respect a precise template but we are using bitbucket and to close a PR it propose:
I would to be able to exclude the merge commits to gather JIRA issues. If I use ignoreCommitsIfMessageMatches that start with Merged also PR merged with squash strategy are ignore.
For our scrum merge commit are not important to determinate which issue are in a release.
The merge commit information is already there so it should be possible performa simple filter.
The best thing would be able to pass a callable (this is possible also in jenkins pipeline) to filter on Commit fields. Otherwise I have to ignore gathered issues and filter commit to get issue using the issue pattern.
The text was updated successfully, but these errors were encountered: