(Git plugin) Build trigger when branch is deleted in GitHub?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

(Git plugin) Build trigger when branch is deleted in GitHub?

Alejandro Villarreal

I noticed that the github service/integration for the Jenkins Git Plugin triggers builds when branches are deleted in Github. Those builds fail because they try to checkout a SHA1 that just got deleted from the repository, and they're "polluting" my Jenkins dashboard, since I'm seeing projects with failed builds when the actual code builds just fine.


Is that expected? That a branch deletion in Github triggers a build in Jenkins? I'm thinking that if anything needs to change, or at least be more configurable, it's probably the Github integration. If it didn't send notifications for branch deletions, this problem would go away.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bbd05bc3-315a-4264-9937-26ac710ade07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: (Git plugin) Build trigger when branch is deleted in GitHub?

Mark Waite-2
I have never seen a case where a job is triggered by branch deletion.

The GitHub Branch Source plugin will (correctly) disable a job associated with a branch when branch deletion is detected, and will (correctly) remove the job according to the settings for that repository.

If the GitHub webhooks are notifying Jenkins of a branch deletion, that seems like a good thing, not a bad thing.

Mark Waite

On Thu, Apr 12, 2018 at 2:26 PM Alejandro Villarreal <[hidden email]> wrote:

I noticed that the github service/integration for the Jenkins Git Plugin triggers builds when branches are deleted in Github. Those builds fail because they try to checkout a SHA1 that just got deleted from the repository, and they're "polluting" my Jenkins dashboard, since I'm seeing projects with failed builds when the actual code builds just fine.


Is that expected? That a branch deletion in Github triggers a build in Jenkins? I'm thinking that if anything needs to change, or at least be more configurable, it's probably the Github integration. If it didn't send notifications for branch deletions, this problem would go away.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bbd05bc3-315a-4264-9937-26ac710ade07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEo1mMq-kgCSeEpQShoJb%3DOSgG6i2ruee0U89ubT6Sw9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.