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

Add Path filtering to triggers in multibranchPipelineJob branchSources

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

      in a `multibranchPipelineJob`, we can currently ONLY select branches that we want to include and exclude in our triggers.

       

      We have some use cases where we would ALSO need builds NOT triggered, when commits only include files under certain paths/folders in a repo.

       

      This seems like it is supported already through the git-plugin's "polling ignores commits in certain paths" advanced option (see screenshot), so I was wondering if there are any plans to extend support for this to the `multibranchPipelineJob`'s `branchSources`.

       

      Thanks,

      Yorgos

          [JENKINS-56771] Add Path filtering to triggers in multibranchPipelineJob branchSources

          Removing the job-dsl-plugin component as this feature needs to be implemented by the git-plugin. It will then be available in Job DSL automatically through Dynamic DSL.

          Daniel Spilker added a comment - Removing the job-dsl-plugin component as this feature needs to be implemented by the git-plugin. It will then be available in Job DSL automatically through Dynamic DSL .

          Yorgos Saslis added a comment -

          daspilker thanks for reviewing.

           

          Tbh, I am not sure I understood what feature needs to be implemented by the git-plugin. As I wrote in the description and as is shown in the screenshot, the "Additional Behaviours" already DO show this feature as being available.

          ...Sounds like I'm missing something?

          Yorgos Saslis added a comment - daspilker thanks for reviewing.   Tbh, I am not sure I understood what feature needs to be implemented by the git-plugin. As I wrote in the description and as is shown in the screenshot, the "Additional Behaviours" already  DO show this feature as being available. ...Sounds like I'm missing something?

          Ben Middleton added a comment -

          I would also like to see the multibranchPipelineJob support this on bitbucket sources. Right now I have multiple multibranchPipelineJob that point to the same repository, and any commits to that repository trigger all related jobs. Ideally I would like to be able to only trigger a job if certain files within the commit are changed.

          Ben Middleton added a comment - I would also like to see the multibranchPipelineJob support this on bitbucket sources. Right now I have multiple multibranchPipelineJob that point to the same repository, and any commits to that repository trigger all related jobs. Ideally I would like to be able to only trigger a job if certain files within the commit are changed.

            Unassigned Unassigned
            yorgos Yorgos Saslis
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: