[JIRA] (JENKINS-57370) Error in Jenkinsfile causes infinite build loop with polling trigger

2019-05-08 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57370  
 
 
  Error in Jenkinsfile causes infinite build loop with polling trigger   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Issue Type: 
 New Feature Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199151.1557318781000.20742.1557318960143%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57370) Error in Jenkinsfile causes infinite build loop with polling trigger

2019-05-08 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57370  
 
 
  Error in Jenkinsfile causes infinite build loop with polling trigger   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Vincent Latombe  
 
 
Components: 
 pollscm-plugin  
 
 
Created: 
 2019-05-08 12:33  
 
 
Environment: 
 AWS ECS  Jenkins v2.150.3  BlueOcean v1.16.0  All plugins up-to-date  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jonathan Kuleff  
 

  
 
 
 
 

 
 I had an error in my Jenkinsfile today were I was missing a closing bracket, causing my builds to fail and a new build triggered for the same commit every 2 minutes which I suspect is due to a poll trigger in the pipeline configuration 

 

triggers { 
   // poll repo every 2 minute for changinges 
   pollSCM('*/2 * * * *') 
}
 

  the pipeline logs were 

 

Started by an SCM change
Obtained Jenkinsfile from 7c608f6019a2de1e1db0fd32ffa48fc915be13c7
Running in Durability level: PERFORMANCE_OPTIMIZED
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 974: expecting '}', found '' @ line 974, column 1.
1 error

	at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
	at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:150)
	at org.codehaus.groovy.control.ErrorCo

[JIRA] (JENKINS-53167) Add ability to always run particular stages when restarting

2019-05-05 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-53167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ability to always run particular stages when restarting
 

  
 
 
 
 

 
 I would really like this feature too. I have 2 use cases for this feature, the first is I would like to send a notification when a pipeline starts regardless of how it was triggered, there is no real nice way to do this currently for stage restarts. The second use case is I want to load some config/metadata that was generated from a skipped stage allowing me to restart from any stage, however because I can't know which will be the restarted stage I need to try load it in every stage and this just makes my Jenkinsfile look unnecessarily cluttered. In both cases having a pipeline pre stage would simplify my Jenkinsfile and declutter it making it easier to read and maintain  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-47179) Can't use milestone with parallel stages in Declarative

2019-03-21 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff edited a comment on  JENKINS-47179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use milestone with parallel stages in Declarative   
 

  
 
 
 
 

 
 Any chance we could do something similar to locks? i.e. ``` {code} stage('Parent')  \ {  options {milestone()  }  stages {stage('first child') {  options  \ {milestone()}  ...}stage('second child') {{   options  \ {milestone()}  ...}  }} ``` {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-47179) Can't use milestone with parallel stages in Declarative

2019-03-21 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff edited a comment on  JENKINS-47179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use milestone with parallel stages in Declarative   
 

  
 
 
 
 

 
 Any chance we could do something similar to locks? i.e. ``` stage('Parent') \{  options {milestone()  }  stages {stage('first child') {  options \{ milestone() }  ...}stage('second child') {   options \{ milestone() }  ...}  }} ```  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-47179) Can't use milestone with parallel stages in Declarative

2019-03-21 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-47179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use milestone with parallel stages in Declarative   
 

  
 
 
 
 

 
 Any chance we could do something similar to locks? i.e. stage('Parent') { options  { milestone() }  stages { stage('first child')  { options \{ milestone() }  ... } stage('second child')  { options \{ milestone() }  ... } } }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-49717) no token field in Openshift OAuth token credential type

2018-08-15 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-49717  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: no token field in Openshift OAuth token credential type   
 

  
 
 
 
 

 
 you can easily reproduce this but running the docker version of jenkins and installing the kubernetes plugin. 

 

docker run -u root -d -p 8080:8080 jenkinsci/blueocean
 

 after restarting jenkins after installing the plugin, try to create an 'OpenShift OAuth Token' credential. there will only be scope drop down visible, no input for the token, id, etc  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-49717) no token field in Openshift OAuth token credential type

2018-08-15 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-49717  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: no token field in Openshift OAuth token credential type   
 

  
 
 
 
 

 
 I am experience this issue as well  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-08-09 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-50886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
 Mark Waite this has mostly fixed itself up. We are using AWS EFS to back our container cluster that Jenkins is running on and it turns out it didn't have enough IOPS credits, a recently feature that allows us to provision IOPS has seems to fix this up for us bar the occasional double build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-50857) Docker agent on windows fails with Cannot run program "id"

2018-08-09 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-50857  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
 thank you Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-52957) Workspace not cleaned up when using skipDefaultCheckout option

2018-08-09 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52957  
 
 
  Workspace not cleaned up when using skipDefaultCheckout option   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-08-09 10:13  
 
 
Environment: 
 Jenkins 2.121.1  Blue Ocean 1.7.0  agent:  Windows Server 2016  Remoting 3.15  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Kuleff  
 

  
 
 
 
 

 
 I'm using declarative pipeline and have recently noticed that a stage using `skipDefaultCheckout()` option is not cleaning up the workspace on a windows agent. I'm not sure if pipeline is meant to automatically do this but I was expected it to. It would be nice if the declarative pipeline syntax supported specifying if a stage should clean the workspace and if it should be at the beginning or end of the stage.   For the time being I have worked around it by using `DeleteDir()`      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

   

[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-05-12 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-50886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
 Mark Waite thanks for looking at that. I'll try to reproduce with a simplified jenkinsfile for you.   Here is what I did to try reproduce it: 
 
Created Bitbucket as a private repo 
Created a `feature/JENKINS-50886` branch and added the Jenkinsfile (declarative pipeline) and README.md (nothing special) 
Created a new pipeline in BlueOcean 
Jumped out to classic and turned on `Scan Multibranch Pipeline Triggers -> Periodically if not otherwise run` with an interval of 5 minutes, so new branches are picked up automatically 
   This is were I have hit a road block, for some reason polling is not picking up changes, even though there are some.   

 
Poll Log

Started on May 12, 2018 3:48:31 PM
Done. Took 0 ms
No changes 

     

 
Scan Multibranch Pipeline Log

Started by timer
[Sat May 12 15:49:00 GMT 2018] Starting branch indexing...
Connecting to https://bitbucket.org using builder/** (Bitbucket server credentials)
Repository type: Git
Looking up repo/jenkins-bug for branches
Checking branch feature/JENKINS-50886 from repo/jenkins-bug
  ‘Jenkinsfile’ found
Met criteria
Changes detected: feature/JENKINS-50886 (dc08795440200d86ee6dfe67b9f1bcefa44f2e40 → 5dbf835960f9b4a599fed8b4dd2903795e334194)
Scheduled build for branch: feature/JENKINS-50886
Checking branch master from repo/jenkins-bug
  ‘Jenkinsfile’ found
Met criteria
No changes detected: master (still at 5883611d9e07b7595051a9aca1227920b42e747d)

  2 branches were processed
Looking up repo/jenkins-bug for pull requests

  0 pull requests were processed
[Sat May 12 15:49:26 GMT 2018] Finished branch indexing. Indexing took 25 sec
Finished: SUCCESS 

   Any idea why polling is not working or recommendations on where to look? One thing I noticed is that this new pipeline has `Polling Log` while existing have `Git Polling Log`  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"

2018-05-10 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-50857  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
 Andrew Bayer not sure if you are the right person to get this looked at by someone but would really appreciate if someone can look at this as docker agent for declarative pipeline is broken for windows containers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50857) Docker agent on windows fails with Cannot run program "id"

2018-05-10 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Environment: 
 Windows Server  Code  Core  2016Jenkins 2.89.4Pipeline: Declarative 1.2.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-05-10 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff commented on  JENKINS-50886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
 Mark Waite Andrew Bayer the build does not complete in less then 2 minutes. Excuse me if I have misunderstood how this feature is meant to work but I am assuming that when a scan runs and it detects a new commit, it triggers a build for the commit and records the commit hash as being triggered/seen. 2 minutes later it scans again if no new commits nothing happens, however if there is a new commit is triggers for that commit. From Mark's comment it sounds like the build has to be finished before the next poll.   If there is any other information I can provide to get to the bottom of this, please let me know.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50857) Docker agent on windows fails with Cannot run program "id"

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Environment: 
 Windows  Server Code  2016 ,   Jenkins 2.89.4 Pipeline: Declarative 1.2.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50886  
 
 
  Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50886  
 
 
  Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 

  
 
 
 
 

 
 I have a multibranch declarative pipeline with a pollSCM trigger to poll every 2 minutes. Whenever there is a change to the branch in BitBucket it triggers correctly but about 2 minutes later it triggers again. I'm not sure if this is a bug or some configuration error on my behalf. I've attached a screenshot of the duplicate builds and poll log for one of the duplicate builds. Below is the top of  me  my  declarative pipeline for reference to how I am setting it up.{code:java}pipeline {   agent none   environment {  APPVERSION = '0.1.0'  NUGET_API_KEY = credentials('build-server-nuget-id-readonly')   }   triggers {   // poll repo every 2 minute for changes   pollSCM('*/2 * * * *')   }   options {   // add timestamps to output   timestamps()   overrideIndexTriggers(false)   buildDiscarder(logRotator(numToKeepStr: '10'))   skipStagesAfterUnstable()   durabilityHint('PERFORMANCE_OPTIMIZED')   }...}{code}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 


[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Priority: 
 Minor Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50886  
 
 
  Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Labels: 
 bitbucket declarative pipeline, pollscm  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50886) Declarative pipeline with pollSCM triggers 2 builds

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50886  
 
 
  Declarative pipeline with pollSCM triggers 2 builds   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Vincent Latombe  
 
 
Attachments: 
 jenkins polling log.txt, jenkins-duplicate-example.png  
 
 
Components: 
 bitbucket-plugin, pipeline, pollscm-plugin  
 
 
Created: 
 2018-04-19 01:58  
 
 
Environment: 
 Official Jenkins Container (on AWS ECS)  Jenkins 2.89.4  Pipeline: Declarative 1.2.8,  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Kuleff  
 

  
 
 
 
 

 
 I have a multibranch declarative pipeline with a pollSCM trigger to poll every 2 minutes. Whenever there is a change to the branch in BitBucket it triggers correctly but about 2 minutes later it triggers again. I'm not sure if this is a bug or some configuration error on my behalf.   I've attached a screenshot of the duplicate builds and poll log for one of the duplicate builds. Below is the top of me declarative pipeline for reference to how I am setting it up. 

 

pipeline {
   agent none
   environment {
  APPVERSION = '0.1.0'
  NUGET_API_KEY = credentials('build-server-nuget-id-readonly')
   }
   triggers {
   // poll repo every 2 minute for changes
   pollSCM('*/2 * * * *')
   }
   options {
   // add timestamps to output
   timestamps()
   overrideIndexTriggers(false)
   buildDiscarder(logRotator(numToKeepStr: '10'))
   skipStagesAfterUnstable()
   durabilityHint('PERFORMANCE_OPTIMIZED')

[JIRA] (JENKINS-50857) Docker agent on windows fails with Cannot run program "id"

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows fails with Cannot run program "id"   
 

  
 
 
 
 

 
Change By: 
 Jonathan Kuleff  
 
 
Summary: 
 Docker agent on windows  fails  with Cannot run program "id"  
 
 
Environment: 
 Windows 2016, Jenkins 2.89.4  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-50857) Docker agent on windows with Cannot run program "id"

2018-04-18 Thread jonathankuleff+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Kuleff created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50857  
 
 
  Docker agent on windows with Cannot run program "id"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-04-18 07:42  
 
 
Labels: 
 pipeline declarative docker  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Kuleff  
 

  
 
 
 
 

 
 I'm trying to use a docker agent on windows in declarative pipeline. I can see the image is pulled but then fails as below 

 

[ply-widgets-project-pipelin-GORWBIPVPM5EWBJECA7BVJBSR5OVNCYISONJIELJYMXAG4YTMWPQ] Running shell script
sh: sleep: command not found
sh: sleep: command not found
sh: sleep: command not found
sh: sleep: command not found
sh: sleep: command not found
+ docker inspect -f . 1234567.dkr.ecr.us-west-2.amazonaws.com/builds/jenkins-agent-node:windows-npm-5.8.0
.
Cannot run program "id": CreateProcess error=2, The system cannot find the file specified
 

   I'm using the following in my jenkinsfile for a stage 

 

agent {
docker { 
image '1234567.dkr.ecr.us-west-2.amazonaws.com/builds/jenkins-agent-node:windows-npm-5.8.0' 
label 'windows&&docker' 
}
}
 

 While I don't think it matters in this case my registry is actually AWS ECR and the agent is a windows s