Hi,

      I encountered difficulty in locating a method to effectively filter the pull requests and push operations for a specific branch.

      Thanks,

          [JENKINS-71682] Allow filtering of triggering per branch

          Dyon added a comment -

          Hi Assaf, 
          Implementation of the Pull Requests tab is being worked on here: https://issues.jenkins.io/browse/JENKINS-66581
          When released you will be able to filter pull requests using filter traits.

          Dyon added a comment - Hi Assaf,  Implementation of the Pull Requests tab is being worked on here: https://issues.jenkins.io/browse/JENKINS-66581 When released you will be able to filter pull requests using filter traits.

          Jose added a comment -

          I reviewed https://issues.jenkins.io/browse/JENKINS-66581 and I couldn't find if the suggestion from this ticket was actually implemented. Right now, the plugin configuration doesn't offer a way to configure a job to only discover Pull Requests that are targeting a specific branch. For example, to trigger a job on a Pull Requests from a feature-branch to the develop-branch.

          Example scenario:

          • Feature branch named: Feature/something-something
          • Create Pull Request from Feature/Something-something branch to develop branch with PR name "Feature/something-something"
          • Discover Pull Requests enabled.
          • Filter by name: Feature/*

          The expectation was to discover and run the job for that Pull Request. Instead, nothing happens. If "Filter by name" is removed, then the PR is discovered and it gets built.

          Jose added a comment - I reviewed https://issues.jenkins.io/browse/JENKINS-66581 and I couldn't find if the suggestion from this ticket was actually implemented. Right now, the plugin configuration doesn't offer a way to configure a job to only discover Pull Requests that are targeting a specific branch. For example, to trigger a job on a Pull Requests from a feature-branch to the develop-branch. Example scenario: Feature branch named: Feature/something-something Create Pull Request from Feature/Something-something branch to develop branch with PR name " Feature/something-something " Discover Pull Requests enabled. Filter by name: Feature/* The expectation was to discover and run the job for that Pull Request. Instead, nothing happens. If "Filter by name" is removed, then the PR is discovered and it gets built.

          Jose added a comment - - edited

          To add that the "Filter by name" when using against Discovered Pull Requests only works against the PR ID instead of against the PR's title. For example, PR-11 instead of Feature/Something-something would only match that PR if the filter is set to PR-*. The expectation was to match against the PR's title, not the PR ID.

          Jose added a comment - - edited To add that the "Filter by name" when using against Discovered Pull Requests only works against the PR ID instead of against the PR's title. For example, PR-11 instead of Feature/Something-something would only match that PR if the filter is set to PR-* . The expectation was to match against the PR's title, not the PR ID.

            Unassigned Unassigned
            assafkatz3b Assaf Katz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: