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

Push event web hook triggers all jobs regardless of Branch Specifier

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: gitlab-hook-plugin
    • Labels:
      None
    • Environment:
      AWS Linux AMI, Version 2015.03
    • Similar Issues:

      Description

      This started happening since 1.4.0.

      I have had to downgrade to 1.3.1 as this is a blocker.
      We have 2 jobs for each repository.
      The 2 jobs have the following Branch Specifiers:

      • origin/feature/*
      • origin/master

      Jenkins 1.613 is running on Amazon Linux Image. This issue seems related to the plugin itself rather than Jenkins, but please let me know if you need any more details if you cannot replicate.

      Thanks,
      Michael

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          10 older comments
          Hide
          Permalink
          javiplx Javier Palacios added a comment -

          Yep, you're completely right. I'm working on selective removal of that kind of configuration items (even emailing can be annoying), but that's definitely not a matter of days ...

          Show
          javiplx Javier Palacios added a comment - Yep, you're completely right. I'm working on selective removal of that kind of configuration items (even emailing can be annoying), but that's definitely not a matter of days ...
          Hide
          Permalink
          mg_zpg Michael Giuliano added a comment -

          Heh, I bet! That's fine!
          As long as you're happy adding these features to your roadmap, I'm happy to wait for them.

          Thanks

          Show
          mg_zpg Michael Giuliano added a comment - Heh, I bet! That's fine! As long as you're happy adding these features to your roadmap, I'm happy to wait for them. Thanks
          Hide
          Permalink
          javiplx Javier Palacios added a comment -

          If you want to give another chance, try the latest snapshot. It allows to configure whether triggering is done also for merged branches, and defaults to false, which should cause less surprises.
          I've done a fast test and seems to work, although it is not yet fully merged because I want to add some acceptance test for this.

          Show
          javiplx Javier Palacios added a comment - If you want to give another chance, try the latest snapshot . It allows to configure whether triggering is done also for merged branches, and defaults to false, which should cause less surprises. I've done a fast test and seems to work, although it is not yet fully merged because I want to add some acceptance test for this.
          Hide
          Permalink
          rlagoue rlagoue added a comment -

          Hello

          When do you expect to publish the next release. Since I am waiting this fix for long time now

          Thanks for the great work

          Show
          rlagoue rlagoue added a comment - Hello When do you expect to publish the next release. Since I am waiting this fix for long time now Thanks for the great work
          Hide
          Permalink
          javiplx Javier Palacios added a comment -

          I sould fix write permission on the plugins store, but 1.4.1 will be available in a few days.

          Show
          javiplx Javier Palacios added a comment - I sould fix write permission on the plugins store, but 1.4.1 will be available in a few days.

            People

            Assignee:
            javiplx Javier Palacios
            Reporter:
            mg_zpg Michael Giuliano
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: