[JIRA] [gitlab-hook-plugin] (JENKINS-29318) Support deleting multiple jobs on branch delete
Title: Message Title Vladimir Sitnikov commented on JENKINS-29318 Re: Support deleting multiple jobs on branch delete This is an additional feature to JENKINS-29317. In other words, it might make sense to configure things like "trigger jobs A,B on push, C,D on delete, etc". However, I would be fine if the same job is triggered on push/delete provided there is a parameter that identifies the source event (push, deleted branch, etc). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-29318) Support deleting multiple jobs on branch delete
Title: Message Title Javier Palacios commented on JENKINS-29318 Re: Support deleting multiple jobs on branch delete Can I assume this is the counter part of JENKINS-29283 ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-29318) Support deleting multiple jobs on branch delete
Title: Message Title Vladimir Sitnikov created an issue Jenkins / JENKINS-29318 Support deleting multiple jobs on branch delete Issue Type: New Feature Assignee: Javier Palacios Components: gitlab-hook-plugin Created: 09/Jul/15 4:45 PM Priority: Major Reporter: Vladimir Sitnikov A build configuration for a single branch can easily consist of more than one job. It would be nice if gitlab-hook could delete all the parts on branch removal. I think call parametrized job on branch delete would do the trick, so each project can create relevant cleanup job. Does that make sense? Add Comment