[JIRA] [github-plugin] (JENKINS-32252) Possible issue with how triggers are started

2016-02-07 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-32252 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 
 
Not a github-plugin issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-plugin] (JENKINS-32252) Possible issue with how triggers are started

2015-12-30 Thread mjdetul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32252 
 
 
 
  Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 
 
 
 
 
 
 
 Original reporter [~pascalw]I noticed that when creating projects with this plugin the Github plugin doesn't create webhooks like it normally does on regular projects.I've debugged this issue a bit and noticed that on multi branch projects the Github trigger `start` method is always called with `newInstance = false` whereas on regular projects the it's called with newInstance = true. Looking at the code I think this could possibly originate from  [here]( https://github.com/mjdetullio/multi-branch-project-plugin/blob/54d7e5ebde04a13469d96b883cb81ce11351164f/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/FreeStyleMultiBranchProject.java#L964 )  where the start method is indeed called with  `  {{ newInstance=false ` }} .What I'm confused about however is whether the triggers should be started from the parent project at all or if they should be started on each child project. In any case the behavior of starting triggers seems to be different in multi branch projects vs regular projects.  @  [~ mjdetullio ]  can you help me understand this issue? If this is an actual issue I would like to fix it but I first want to make sure I fully understand the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [github-plugin] (JENKINS-32252) Possible issue with how triggers are started

2015-12-30 Thread mjdetul...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew DeTullio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32252 
 
 
 
  Possible issue with how triggers are started  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew DeTullio 
 
 
 

Component/s:
 
 github-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.