[JIRA] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.

2016-12-01 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld commented on  JENKINS-39092  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline branches SCM polling properties for multibranch has broken behaviour.   
 

  
 
 
 
 

 
 Hrm just witnessed this behaviour again today. Haven't had a chance to install a fresh jenkins install to try to find a test case yet.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.

2016-11-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39092  
 
 
  Pipeline branches SCM polling properties for multibranch has broken behaviour.   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 workflow-multibranch-plugin  
 
 
Labels: 
 multibranch  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.

2016-11-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Either track down the root cause or provide a PR with an @Ignore functional test demonstrating the symptom.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39092  
 
 
  Pipeline branches SCM polling properties for multibranch has broken behaviour.   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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 

[JIRA] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.

2016-10-18 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39092  
 
 
  Pipeline branches SCM polling properties for multibranch has broken behaviour.   
 

  
 
 
 
 

 
Change By: 
 Nick Sonneveld  
 

  
 
 
 
 

 
 We're attempting to configure a pipeline multibranch folder such that 'default' is always built but feature branches are only built daily.   We did this by suppressing automatic SCM triggering for all branches except 'default', then configuring a separate pollSCM in the jenkinsfile for each branch. However we're seeing issues where feature branches that have changes are not built for days while sometimes a branch will be triggered many times for the same changeset.Multiple jobs for the same changeset are triggered.  The first by "Branch indexing" and the later ones by "Started by an SCM change".  The logs show "Dependent changes detected"No other polling is configured. Removing the pipelineTriggers/pollSCM property seems to stop repeat builds (but won't give you daily builds)   Our Jenkinsfile starts with this:{noformat}def alwaysBuild = (env.BRANCH_NAME == "default" || env.BRANCH_NAME ==~ /CompanyName-.*/);properties([overrideIndexTriggers(alwaysBuild), pipelineTriggers([pollSCM('@daily')])]);{noformat}Multibranch folder is configured with properties overrides:- "named branches get different properties" exceptions: "default": no properties "us*,d*,ts*": Suppess automatic SCM triggering.And every commit will notify jenkins via {noformat}curl -v  http://jenkins:8080/mercurial/notifyCommit?url="">{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was 

[JIRA] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.

2016-10-18 Thread nick.sonnev...@smartward.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Sonneveld created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39092  
 
 
  Pipeline branches SCM polling properties for multibranch has broken behaviour.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 build 125 Screen Shot 2016-10-19 at 4.11.14 PM.png, build 126 Screen Shot 2016-10-19 at 4.11.28 PM.png, job config - Screen Shot 2016-10-19 at 4.09.04 PM.png, multibranch config Screen Shot 2016-10-19 at 4.10.24 PM.png, multiple builds - Screen Shot 2016-10-19 at 4.10.53 PM.png  
 
 
Components: 
 mercurial-plugin, pipeline, workflow-multibranch-plugin  
 
 
Created: 
 2016/Oct/19 5:28 AM  
 
 
Environment: 
 Jenkins 2.26  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Nick Sonneveld  
 

  
 
 
 
 

 
 We're attempting to configure a pipeline multibranch folder such that 'default' is always built but feature branches are only built daily. However we're seeing issues where feature branches that have changes are not built for days while sometimes a branch will be triggered many times for the same changeset. Multiple jobs for the same changeset are triggered. The first by "Branch indexing" and the later ones by "Started by an SCM change". The logs show "Dependent changes detected" No other polling is configured. Our Jenkinsfile starts with this: 

 
def alwaysBuild = (env.BRANCH_NAME == "default" || env.BRANCH_NAME ==~ /CompanyName-.*/);
properties([overrideIndexTriggers(alwaysBuild), pipelineTriggers([pollSCM('@daily')])]);