-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins Version: 2.303.2
Gerrit Version: 3.4.1
Gerrit Trigger Version : 2.35.2
After upgrading to gerrit-trigger-plugin version 2.35.2, the specific builds that used to only trigger on merge commits no longer do. This is because, previously, the './MERGE_LIST' file was added to the list of interesting file which would trigger a particular build to run on a gerrit merge commit. However, since 2.35.2 it looks like this file is explicitly excluded from the list of interesting files.
There is a workaround where a commit message's text can be used to determine if a commit is a merge commit, but it's doesn't support all the functionality that using './MERGE_LIST' did (for example, rerunning particular merge commit checks on a particular gerrit change using a keyword in the comments).
It would be great if this file could be added back to the list of files to be considered when triggering builds, unless there is a better alternative.
[JENKINS-67304] './MERGE_LIST' file is no longer considered interesting
Alexander
added a comment - I wanted to add another use case that I can't get to work without this feature: Trigger build for Files in `FolderA/` and for merges.
Detailed setup:
Build A, should trigger for changes in "JenkinsFile", "FolderA/", and for (potentially empty) merge commits.
Build B, should trigger for changes in "JenkinsFile", "FolderB/", and for (potentially empty) merge commits.
Background: one build is responsible for "FolderA", the other for "FolderB". Both should trigger if both folders change.
Currently, no build is triggered for a clean merge commit (the merge commit merges changes from both folders, but is itself a clean empty merge). However, both builds should be triggered.
Without having access to the MERGE_LIST I don't know how this could be achieved.
Alexander
added a comment - I wanted to add another use case that I can't get to work without this feature: Trigger build for Files in `FolderA/` and for merges.
Detailed setup:
Build A, should trigger for changes in "JenkinsFile", "FolderA/", and for (potentially empty) merge commits.
Build B, should trigger for changes in "JenkinsFile", "FolderB/", and for (potentially empty) merge commits.
Background: one build is responsible for "FolderA", the other for "FolderB". Both should trigger if both folders change.
Currently, no build is triggered for a clean merge commit (the merge commit merges changes from both folders, but is itself a clean empty merge). However, both builds should be triggered.
Without having access to the MERGE_LIST I don't know how this could be achieved. 
Oliver Sayer
added a comment - This issue is starting to cause workflow problems with a few of my projects - would it be possible to get an environment variable to override the magic file exclusions!? 
Oliver Sayer
added a comment - This issue is starting to cause workflow problems with a few of my projects - would it be possible to get an environment variable to override the magic file exclusions!? 
This was changed with Github
"Fix excessive triggers for a change with forbidden files only"
Our project also heavily relies on Merge Commits to trigger a Build. It would be great if we could have Checkboxes in the project, to include those Files on demand.