date:20160504

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 kishorerp created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34620 
 
 
 
  COPYARTIFACT_BUILD_NUMBER_SUFFIX in workflow jobs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 copyartifact-plugin 
 
 
 

Created:
 

 2016/May/05 5:22 AM 
 
 
 

Environment:
 

 jenkins 1.655 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 kishorerp 
 
 
 
 
 
 
 
 
 
 
Does the COPYARTIFACT_BUILD_NUMBER_SUFFIX work on expected lines in workflow/pipeline jobs? copy artifact command am using is 
step([$class: 'CopyArtifact', filter: '*.rpm', fingerprintArtifacts: true, projectName: 'test_pkg', resultVariableSuffix: 'testsuffix', selector: [$class: 'ParameterizedBuildSelector', parameterName: 'testparam'], target: 'test_packages']) 
when i do 
println COPYARTIFACT_BUILD_NUMBER_TESTSUFFIX 
am getting the below error 
groovy.lang.MissingPropertyException: No such property: COPYARTIFACT_BUILD_NUMBER_TESTSUFFIX for class: WorkflowScript 
println env.COPYARTIFACT_BUILD_NUMBER_TESTSUFFIX gives me null

[JIRA] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
Interesting. 
 

Is your keystone/identity url https one?
 

How about other endpoints (Access & security > API Access).
 
 
My best guess is that keystone URL uses http (that is why test connection works) but advertise other endpoints using https (so it fails when you start using openstack). Please attach full stacktrace so we know for sure. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-build-status-notifier-plugin] (JENKINS-34619) Report test results to bitbucket build status

2016-05-04 Thread djehr...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Ninnes started work on  JENKINS-34619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jeremy Ninnes 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-build-status-notifier-plugin] (JENKINS-34619) Report test results to bitbucket build status

2016-05-04 Thread djehr...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Ninnes created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34619 
 
 
 
  Report test results to bitbucket build status  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jeremy Ninnes 
 
 
 

Attachments:
 

 test_result.png, test_result_2.png 
 
 
 

Components:
 

 bitbucket-build-status-notifier-plugin 
 
 
 

Created:
 

 2016/May/05 4:38 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jeremy Ninnes 
 
 
 
 
 
 
 
 
 
 
Support reporting test results into bitbucket so that the reason for build failure can be seen at a glance from a pull request or branch. Eg: 
test_result.png 
test_result_2.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [active-choices-plugin] (JENKINS-34618) Active Choice reactive parameter gives an exception in the following scenario

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 kishorerp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34618 
 
 
 
  Active Choice reactive parameter gives an exception in the following scenario  
 
 
 
 
 
 
 
 
 

Change By:
 
 kishorerp 
 
 
 
 
 
 
 
 
 
 I have a jenkins workflow/pipeline job in which i use the Active choices plugin in  parent child modeThis pipeline job is the downstream job for another jobMy script is attachedcreate a sample pipeline job with the attached script(Job1)Create pipeline Job2-->Snippet Generator-->build:Build a Job-->Give Job1, Observe that  child  CHILD field throws an exception and goes to fall back scriptScript is attached(active_choice_issue.groovy)and  error is attachedChrome being the browser(latest edition on windows 10) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-choices-plugin] (JENKINS-34618) Active Choice reactive parameter gives an exception in the following scenario

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 kishorerp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34618 
 
 
 
  Active Choice reactive parameter gives an exception in the following scenario  
 
 
 
 
 
 
 
 
 

Change By:
 
 kishorerp 
 
 
 

Environment:
 
 Jenkins 1. 652 655 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-choices-plugin] (JENKINS-34618) Active Choice reactive parameter gives an exception in the following scenario

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 kishorerp created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34618 
 
 
 
  Active Choice reactive parameter gives an exception in the following scenario  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Attachments:
 

 activchoicebug.txt, active_choice_issue.groovy 
 
 
 

Components:
 

 active-choices-plugin 
 
 
 

Created:
 

 2016/May/05 4:26 AM 
 
 
 

Environment:
 

 Jenkins 1.652 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 kishorerp 
 
 
 
 
 
 
 
 
 
 
I have a jenkins workflow/pipeline job in which i use the Active choices plugin in parent child mode This pipeline job is the downstream job for another job My script is attached create a sample pipeline job with the attached script(Job1) Create pipeline Job2-

>Snippet Generator


>build:Build a Job
->Give Job1, Observe that child CHILD field throws an exception and goes to fall back script

[JIRA] [warnings-plugin] (JENKINS-30551) Make Warnings Plugin compatible with parallel Workflow

2016-05-04 Thread teemu.murt...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Teemu Murtola updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30551 
 
 
 
  Make Warnings Plugin compatible with parallel Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Teemu Murtola 
 
 
 

Labels:
 
 workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [s3-plugin] (JENKINS-14470) S3 Plugin switches credential profiles

2016-05-04 Thread abrookew...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antony Brooke-Wood commented on  JENKINS-14470 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: S3 Plugin switches credential profiles  
 
 
 
 
 
 
 
 
 
 
I'm logging what may be a related bug. I have noticed that the plugin does not like mixed profiles: i.e. some created that rely on an IAM role and others that rely on an Access Key & Secret Key. It will only display all profiles when they are the same. If they are mixed, it shows the first one, but none after that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

2016-05-04 Thread zxi...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thanh Ha commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 
Great the additional logging helps. 
Openstack call failed ConnectionException {message=sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, status=0} 
Looks like the problem is that our ssl certificate has some issues. The JClouds plugin actually fails the test and tells us this issue rather than telling us it succeeded. I think the OpenStack plugin should do the same when this happens as telling the user that connection test was successful seems misleading in this case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-34550) Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.

2016-05-04 Thread jason.b.mar...@nordstrom.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Marzan updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34550 
 
 
 
  Remote Command Execution - running a job on Windows machines, it is possible to escape parameters by adding “ before string and execute commands on target system.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Marzan 
 
 
 

Component/s:
 
 security 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [kubernetes-plugin] (JENKINS-34380) kubernetes plugin creates an unbounded number of Netty I/O threads

2016-05-04 Thread giu...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Giuseppe Valente commented on  JENKINS-34380 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: kubernetes plugin creates an unbounded number of Netty I/O threads  
 
 
 
 
 
 
 
 
 
 
There is only one newer release for Netty and it was a very minor patch release so I'm certain that upgrading Netty wouldn't help. AFAIK the kubernetes-client lib comes from the plugin itself, so how do I upgrade it? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookies to be saved

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25917 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Spaces in URL (from project name or view) cause invalid cookies to be saved  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/GraphConfigurationView.java src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/b3691320192217d8a2d5e7e60e65119f3b13ea7f Log: Added a test case that checks trend configuration via cookie. 
Basically a test the checks that JENKINS-25917 and JENKINS-32377 are resolved in Jenkins 2.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-34002 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Means of declaring a Pipeline's plugin requirements  
 
 
 
 
 
 
 
 
 
 
Again -1 on a general require. Particular things that might be needed are better handled with dedicated steps or system. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-32377) Upgrade Jetty to fix bugs in cookies

2016-05-04 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in Jenkins 2.x. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32377 
 
 
 
  Upgrade Jetty to fix bugs in cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ulli Hafner 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookies to be saved

2016-05-04 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner assigned an issue to Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25917 
 
 
 
  Spaces in URL (from project name or view) cause invalid cookies to be saved  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ulli Hafner 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookies to be saved

2016-05-04 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in Jenkins 2.x. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-25917 
 
 
 
  Spaces in URL (from project name or view) cause invalid cookies to be saved  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ulli Hafner 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-32377) Upgrade Jetty to fix bugs in cookies

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32377 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Upgrade Jetty to fix bugs in cookies  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/GraphConfigurationView.java src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/b3691320192217d8a2d5e7e60e65119f3b13ea7f Log: Added a test case that checks trend configuration via cookie. 
Basically a test the checks that 

JENKINS-25917
 and JENKINS-32377 are resolved in Jenkins 2.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [extended-choice-parameter-plugin] (JENKINS-34617) Make extended-choice-parameter-plugin pipeline compatibility easier

2016-05-04 Thread ow...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34617 
 
 
 
  Make extended-choice-parameter-plugin pipeline compatibility easier  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 vimil 
 
 
 

Components:
 

 extended-choice-parameter-plugin 
 
 
 

Created:
 

 2016/May/04 11:11 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Owen Wood 
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/extended-choice-parameter-plugin/blob/master/src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java#L427 
should implement @DataboundConstructor to support snippet generator. Or a new constructor should be supplied allowing for some sensible defaults. Just an idea. 
Usage with pipeline is currently possible but not very practical. The number of parameters required for the current constructor is pretty huge. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [authorize-project-plugin] (JENKINS-34616) delivery-pipeline (snippet generator) - fails to create script using Project Based Security

2016-05-04 Thread mev...@parchment.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Evans updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34616 
 
 
 
  delivery-pipeline (snippet generator) - fails to create script using Project Based Security  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matt Evans 
 
 
 

Summary:
 
 Enable Project Based Security doesn't work using delivery-  pipeline  (  snippet generator ) - fails to create script using Project Based Security 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [authorize-project-plugin] (JENKINS-34616) Enable Project Based Security doesn't work using pipeline snippet generator

2016-05-04 Thread mev...@parchment.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Evans created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34616 
 
 
 
  Enable Project Based Security doesn't work using pipeline snippet generator  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Patrik Boström 
 
 
 

Attachments:
 

 job properties.PNG 
 
 
 

Components:
 

 authorize-project-plugin, delivery-pipeline-plugin 
 
 
 

Created:
 

 2016/May/04 10:49 PM 
 
 
 

Environment:
 

 docker run --rm -p : -p 8080:8080 -p 8081:8081 -p 9418:9418 -ti jenkinsci/workflow-demo 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Matt Evans 
 
 
 
 
 
 
 
 
 
 
receive error when trying to create a snippet using the snippet generator (properties > enable project based security). 
Receive the following error: 

 

May 04, 2016 10:42:04 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn
Error while serving http://localhost:8080/workflow-cps-snippetizer/generateSnippet
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

[JIRA] [workflow-plugin] (JENKINS-34596) Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34596 
 
 
 
  Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 Add a way to know if the revision of the Set visible flag when  Jenkinsfile is  not the same  taken from a trusted revision rather  than  the branch tip  PR head 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline

2016-05-04 Thread michael.ne...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34615 
 
 
 
  Global error handler for pipeline  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Neale 
 
 
 
 
 
 
 
 
 
 in a pipeline script it is common to catch errors and take action: notifications, gathering test reports of results thus far. This requires a dance around some variants of try/catch or try/finally, sometimes even rethrowing error, setting the currentBuild.result, checking of the currentBuild.result (to see if set previously). Othertimes you tell the test runner to not fail on test failures and set the build result to unstable (which then requires that you use more if/then or throwing exceptions as it will continue on if unstable for the rest of the pipeline script). Would this be better to have a top level event handler?  This could clarify the control throw without littering the script with non pipeline related flow controls for the case where there is a failure (and you want to exit but do some things). Likewise for notifications.  {noformat} onFailure {   ... archive junit results   ... notify teams}onSuccess {... notify teams} {noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline

2016-05-04 Thread michael.ne...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34615 
 
 
 
  Global error handler for pipeline  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Neale 
 
 
 
 
 
 
 
 
 
 in a pipeline script it is common to catch errors and take action: notifications, gathering test reports of results thus far. This requires a dance around some variants of try/catch or try/finally, sometimes even rethrowing error, setting the currentBuild.result, checking of the currentBuild.result (to see if set previously). Othertimes you tell the test runner to not fail on test failures and set the build result to unstable (which then requires that you use more if/then or throwing exceptions as it will continue on if unstable for the rest of the pipeline script) .  , and then accidentally deploy to production *cough*   Would this be better to have a top level event handler?    This could clarify the control throw without littering the script with non pipeline related flow controls for the case where there is a failure (and you want to exit but do some things). Likewise for notifications. {noformat}onFailure {   ... archive junit results   ... notify teams}onSuccess {... notify teams}{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline

2016-05-04 Thread michael.ne...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34615 
 
 
 
  Global error handler for pipeline  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/May/04 10:42 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Neale 
 
 
 
 
 
 
 
 
 
 
in a pipeline script it is common to catch errors and take action: notifications, gathering test reports of results thus far.  
This requires a dance around some variants of try/catch or try/finally, sometimes even rethrowing error, setting the currentBuild.result, checking of the currentBuild.result (to see if set previously). Othertimes you tell the test runner to not fail on test failures and set the build result to unstable (which then requires that you use more if/then or throwing exceptions as it will continue on if unstable for the rest of the pipeline script).  
Would this be better to have a top level event handler?  This could clarify the control throw without littering the script with non pipeline related flow controls for the case where there is a failure (and you want to exit but do some things). Likewise for notifications.  
onFailure  { ... archive junit results ... notify teams } 
onSuccess  { ... notify teams }

[JIRA] [acceptance-test-harness] (JENKINS-34614) ATH ftpd container doesn't seem to be opening port 21 (or running?)

2016-05-04 Thread andrew.ba...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34614 
 
 
 
  ATH ftpd container doesn't seem to be opening port 21 (or running?)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/04 10:40 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
The ATH Docker ftpd container doesn't seem to be opening port 21 - I can't tell whether that's due to some issue in port mapping or if vsftpd just isn't running. But the result is the tests don't work. =) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [junit-plugin] (JENKINS-27395) distinguish test reports filed from different parts of workflow

2016-05-04 Thread andre...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez edited a comment on  JENKINS-27395 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: distinguish test reports filed from different parts of workflow   
 
 
 
 
 
 
 
 
 
 For anyone interested in this functionality, here is a small hack I use to achieve something similar:{code:java}def setJUnitPackageName(packageName, inFile, outFile) {// Prepend the testName as the package name so that we get sorted output in the// Jenkins test results page. The packageName is extracted from the classname// attribute of the testcase tag.// WARNING: the package attribute of the testcase tag is igonred by Jenkinssh "sed \"s/\\(classname=['\\\"]\\)/\\1${packageName}./g\" ${inFile} > ${outFile}"}{code}With this you can set packageName of a junit file to a string of your choice, we usually use " { test-name } - { platform } " for example. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [junit-plugin] (JENKINS-27395) distinguish test reports filed from different parts of workflow

2016-05-04 Thread andre...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez commented on  JENKINS-27395 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: distinguish test reports filed from different parts of workflow   
 
 
 
 
 
 
 
 
 
 
For anyone interested in this functionality, here is a small hack I use to achieve something similar: 

 

def setJUnitPackageName(packageName, inFile, outFile) {
// Prepend the testName as the package name so that we get sorted output in the
// Jenkins test results page. The packageName is extracted from the classname
// attribute of the testcase tag.
// WARNING: the package attribute of the testcase tag is igonred by Jenkins
sh "sed \"s/\\(classname=['\\\"]\\)/\\1${packageName}./g\" ${inFile} > ${outFile}"
}
 

 
With this you can set packageName of a junit file to a string of your choice, we usually use " {test-name} 
- {platform} 
" for example. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-34396) Gitlab plugin does not work with jenkins pipeline plugin

2016-05-04 Thread o...@nerdnetworks.org (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Mehegan commented on  JENKINS-34396 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gitlab plugin does not work with jenkins pipeline plugin  
 
 
 
 
 
 
 
 
 
 
The current version of the plugin, 1.2.2, works fine with Pipeline jobs. See the README on the plugin's GitHub page for information about how to configure it. However, as Jesse notes, the plugin currently does not support Pipeline Multibranch projects. We'll take that as an item to address ASAP. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2016-05-04 Thread alex.zy...@willjin.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Zykov edited a comment on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 HiI've got the same issueCloning repository ssh://root@192.168.0.20:22/srv/repos/git/root-module.gitClone of 'ssh://r...@xxx.xxx.xxx.xxx:Y/srv/repos/git/sub-module.git' into submodule path 'marksman-c' failedPermission denied (publickey,password).I think plugin doesn't use the original credentialsBRAlexZ P.S.I'm using ssh user name with private key authentication Scope is Global 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2016-05-04 Thread alex.zy...@willjin.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Zykov edited a comment on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 HiI've got the same issueCloning repository ssh://root@192.168.0.20:22/srv/repos/git/root-module.gitClone of 'ssh://r...@xxx.xxx.xxx.xxx:Y/srv/repos/git/sub-module.git' into submodule path 'marksman-c' failedPermission denied (publickey,password).I think plugin doesn't use the original credentialsBRAlexZP.S.I 'm using  use  ssh user name with private key authentication Scope is Global 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-26056) Workflow build step for Ant

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26056 
 
 
 
  Workflow build step for Ant  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-26056) Workflow build step for Ant

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Jesse Glick 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26056 
 
 
 
  Workflow build step for Ant  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated

2016-05-04 Thread alex.zy...@willjin.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Zykov commented on  JENKINS-20941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stored git credentials not used when submodule is updated  
 
 
 
 
 
 
 
 
 
 
Hi I've got the same issue 
Cloning repository ssh://root@192.168.0.20:22/srv/repos/git/root-module.git Clone of 'ssh://r...@xxx.xxx.xxx.xxx:Y/srv/repos/git/sub-module.git' into submodule path 'marksman-c' failed Permission denied (publickey,password). 
I think plugin doesn't use the original credentials 
BR AlexZ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 
 
Update! Use the two EC2-gpedit.png files for reference. Group Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management -> Client & Server. (See screenshot for each.) 
I did this, restarted and it worked. Why these work vs. the command line settings, i have no idea. But that's it. If you have questions post here, i can respond. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 

Attachment:
 
 EC2-gpedit2.png 
 
 
 

Attachment:
 
 EC2-gpedit1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-organization-folder-plugin] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."

2016-05-04 Thread karlmda...@java.net (JIRA)

Title: Message Title

karlmdavis commented on JENKINS-34612

Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."

Blargh, I just figured out what the problem was. Hat tip to this fine fellow for the clue I needed: https://github.com/juretta/hudson-github-plugin/issues/4#issuecomment-56458604. The bug is actually a case-sensitivity issue.
The log entries I included in my issue description were a red herring: a webhook was automatically created (I just missed it), and was being fired from GitHub as expected, and was even being received by Jenkins. Unfortunately, though, Jenkins was ignoring the hook events, because my organization name in Jenkins was cased as HHSIDEALab, rather than as HHSIDEAlab (which is how it's cased in GitHub and in the hook events).
Hilariously, this blew a whole day for me. I know it's a super minor problem in the grand scheme of things, but if you folks could fix the issue, or at least add a useful error/warning in the logs, that'd be super helpful to "future me"s.

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] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 Hello All,I've been trying to run this plugin with Windows 2012 and i'm stuck in some WinRM loop where it cannot connect. I tried setting the launch delay up to 600 seconds to ensure my instance is up before trying any WinRM commands. No luck. Here is what i'm seeing:{code:java}May 04, 2016 4:42:34 PM FINE hudson.plugins.ec2.win.winrm.WinRMClientopening winrm shell to: http://172.31.202.208:5985/wsmanMay 04, 2016 4:42:34 PM FINEST hudson.plugins.ec2.win.winrm.WinRMClientRequest:POST http://172.31.202.208:5985/wsmanhttp://172.31.202.208:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:D6FA9229-05D6-4199-B7B6-ACFA6D195CBEPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderrMay 04, 2016 4:42:35 PM FINEST hudson.plugins.ec2.win.winrm.WinRMClientResponse:http://schemas.xmlsoap.org/ws/2004/09/transfer/CreateResponseuuid:792A9FDE-030D-4646-89A5-8432A425C947http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymousuuid:D6FA9229-05D6-4199-B7B6-ACFA6D195CBEhttp://172.31.202.208:5985/wsmanhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd96758FBF-0CF8-4E59-9E41-FF96E16903AC96758FBF-0CF8-4E59-9E41-FF96E16903AChttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdJENKINSSLAVE\Administrator172.31.202. 242 241 PT7200.000Sstdinstdout stderrP0DT0H0M0SP0DT0H0M0SMay 04, 2016 4:42:35 PM FINER hudson.plugins.ec2.win.winrm.WinRMClientshellid: 96758FBF-0CF8-4E59-9E41-FF96E16903ACMay 04, 2016 4:42:35 PM FINE hudson.plugins.ec2.win.winrm.WinRMClientclosing winrm shell 96758FBF-0CF8-4E59-9E41-FF96E16903ACMay 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svcWaiting for WinRM to come up. Sleeping 10s.etcetc{code}I know WinRM is setup and working correctly, i can connect over Telnet. And I've run the commands suggested from the plugin:{code:java}winrm

[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 Hello All,I've been trying to run this plugin with Windows 2012 and i'm stuck in some WinRM loop where it cannot connect. I tried setting the launch delay up to 600 seconds to ensure my instance is up before trying any WinRM commands. No luck. Here is what i'm seeing:{code:java} May 04, 2016 4:42:34 PM FINE hudson.plugins.ec2.win.winrm.WinRMClientopening winrm shell to: http://172.31.202.208:5985/wsmanMay 04, 2016 4:42:34 PM FINEST hudson.plugins.ec2.win.winrm.WinRMClient Request:POST http://172. 16 31 . 0 202 . 255 208 :5985/wsmanhttp://172. 16 31 . 0 202 . 252 208 :5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid: 24BD995E D6FA9229 - DFCC 05D6 - 4B42 4199 - AF00 B7B6 - E5C85B66445B ACFA6D195CBE PT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderr May 04, 2016 4:42:35 PM FINEST hudson.plugins.ec2.win.winrm.WinRMClient  Response:http://schemas.xmlsoap.org/ws/2004/09/transfer/CreateResponseuuid:792A9FDE-030D-4646-89A5-8432A425C947http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymousuuid:D6FA9229-05D6-4199-B7B6-ACFA6D195CBEhttp://172.31.202.208:5985/wsmanhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd96758FBF-0CF8-4E59-9E41-FF96E16903AC96758FBF-0CF8-4E59-9E41-FF96E16903AChttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdJENKINSSLAVE\Administrator172.31.202.242PT7200.000Sstdinstdout stderrP0DT0H0M0SP0DT0H0M0S May  04, 2016  4 :42:35 PM FINER hudson.plugins.ec2.win.winrm.WinRMClientshellid: 96758FBF-0CF8-4E59-9E41-FF96E16903ACMay 04 , 2016 4: 42:35 PM FINE hudson.plugins.ec2.win.winrm.WinRMClientclosing winrm shell 96758FBF-0CF8-4E59-9E41-FF96E16903ACMay 4, 2016 4: 20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svcWaiting for WinRM to come up. Sleeping 10s.etcetc{code}I know WinRM is setup and working correctly, i can connect over Telnet.

[JIRA] [github-organization-folder-plugin] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."

2016-05-04 Thread karlmda...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 karlmdavis updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34612 
 
 
 
  Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."  
 
 
 
 
 
 
 
 
 

Change By:
 
 karlmdavis 
 
 
 
 
 
 
 
 
 
 When creating a new job for a GitHub org, I'm seeing the following in the Jenkins logs:{code}WARNING: Failed to register GitHub Org hook to https://github.com/karlmdavis (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}May 04, 2016 8:03:46 PM org.jenkinsci.plugins.orgfolder.github.MainLogic applyOrgWARNING: Failed to register GitHub Org hook to https://github.com/HHSIDEAlab (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}{code}I did confirm that the personal access token I'm using has the {{admin:repo_hook}} permission, as well as {{admin:org_hook}}. Not sure what else to check.The plugin seems to work correctly aside from this: it finds projects with {{Jenkinsfile}}s and builds them when asked. Just no webhook triggers. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 
 
Let me answer part of my own question, i tried the AMI with the administrator user. No difference. So this is surely a bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cmakebuilder-plugin] (JENKINS-34613) Set default value of BuildType in Java instead of jelly, for improved usability in pipeline plugin

2016-05-04 Thread fifteenknots...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34613 
 
 
 
  Set default value of BuildType in Java instead of jelly, for improved usability in pipeline plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Martin Weber 
 
 
 

Components:
 

 cmakebuilder-plugin 
 
 
 

Created:
 

 2016/May/04 8:34 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Martin Weber 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You

[JIRA] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory

2016-05-04 Thread jacob.kel...@gmail.com (JIRA)

Title: Message Title

Jacob Keller commented on JENKINS-32479

Re: multiple git repositories sometimes fail to checkout some of them into subdirectory

Can we get some input from developers of Git plugin and Multiple-SCM plugin?
The issue stems from ordering of repositories since the Git Plugin's "clone" operation calls a full delete of the current workspace. I have a possible solution revolving around making the Git Plugin report its actual sub directory using the getModuleRoot() interface, and then having Multiple-SCM "sort"/"order" the repositories in such a way as to avoid checking out into a sub directory first.
Another option would be for Multiple SCM to implement for itself "checkout to a sub directory" instead of relying on the plugins to do so themselves. I believe this would be preferred since it would be much more universal, and allow easier correct access since my fix requires both a change to the git plugin and the multiple SCM plugin.
Finally it may be possible to not need to remove the working directory when implementing clone() in the Git plugin. However, this requires continued use of the init+fetch setup, which currently breaks other uses such as Git-LFS and should be returned back to clone. There does not appear to be a good way to make git-clone behave correctly and allow cloning into a non-empty directory.

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory

2016-05-04 Thread jacob.kel...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Keller assigned an issue to Craig Rodrigues 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32479 
 
 
 
  multiple git repositories sometimes fail to checkout some of them into subdirectory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jacob Keller 
 
 
 

Assignee:
 
 Craig Rodrigues 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [swarm-plugin] (JENKINS-34593) provide an option to delete existing slaves with the same name

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34593 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: provide an option to delete existing slaves with the same name  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Nico Mommaerts Path: client/src/main/java/hudson/plugins/swarm/Options.java client/src/main/java/hudson/plugins/swarm/SwarmClient.java plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/63e43077c2a6bbd994574f618372e3963b2d49e9 Log: JENKINS-34593 add an option to delete existing clients 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [swarm-plugin] (JENKINS-34593) provide an option to delete existing slaves with the same name

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34593 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: provide an option to delete existing slaves with the same name  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Peter Jönsson Path: client/src/main/java/hudson/plugins/swarm/Options.java client/src/main/java/hudson/plugins/swarm/SwarmClient.java plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/9a62abb48b68ef2447af387b9ad6b195bb33dce7 Log: Merge pull request #40 from mrdfuse/JENKINS-34593 
JENKINS-34593 add an option to delete existing clients 
Compare: https://github.com/jenkinsci/swarm-plugin/compare/74f4bbf329eb...9a62abb48b68 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory

2016-05-04 Thread jacob.kel...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Keller assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32479 
 
 
 
  multiple git repositories sometimes fail to checkout some of them into subdirectory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jacob Keller 
 
 
 

Assignee:
 
 Jacob Keller 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 Hello All,I've been trying to run this plugin with Windows 2012 and i'm stuck in some WinRM loop where it cannot connect. I tried setting the launch delay up to 600 seconds to ensure my instance is up before trying any WinRM commands. No luck. Here is what i'm seeing:{code:java}Request:POST http://172.16.0.255:5985/wsmanhttp://172.16.0.252:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:24BD995E-DFCC-4B42-AF00-E5C85B66445BPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderrMay 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svc Waiting for WinRM to come up. Sleeping 10s.etcetc {code}I know WinRM is setup and working correctly, i can connect over Telnet. And I've run the commands suggested from the plugin:{code:java}winrm quickconfigwinrm set winrm/config/service/Auth @{Basic="true"}winrm set winrm/config/service @{AllowUnencrypted="true"}winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}{code}I do have a question in addition to the bug and that is: *Do we just need to specify and administrative user, not precisely "Administrator" ?*I've spent the entire day working on this and I'm simply out of options. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [github-organization-folder-plugin] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."

2016-05-04 Thread karlmda...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 karlmdavis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34612 
 
 
 
  Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 github-organization-folder-plugin 
 
 
 

Created:
 

 2016/May/04 8:14 PM 
 
 
 

Environment:
 

 Jenkins 2.1, github-organization-folder 1.3, github-api 1.75 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 karlmdavis 
 
 
 
 
 
 
 
 
 
 
When creating a new job for a GitHub org, I'm seeing the following in the Jenkins logs: 

 

WARNING: Failed to register GitHub Org hook to https://github.com/karlmdavis (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
May 04, 2016 8:03:46 PM org.jenkinsci.plugins.orgfolder.github.MainLogic applyOrg
WARNING: Failed to register GitHub Org hook to https://github.com/HHSIDEAlab (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
 

 
I did confirm that the personal access token I'm using has the admin:repo_hook permission, as well as admin:org_hook. Not sure what else to check.

[JIRA] [jigomerge-plugin] (JENKINS-12993) Propagate relevant SVN user to UI in case of merge conflicts

2016-05-04 Thread jfill...@calliduscloud.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Fillmore edited a comment on  JENKINS-12993 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Propagate relevant SVN user to UI in case of merge conflicts  
 
 
 
 
 
 
 
 
 
 I have a little work around for this:# Excute shell command  --  {noformat}  grep -R conflictingFiles ../builds/${BUILD_NUMBER}/log | sed -n -e 's/^return : .* conflictingFiles={\(.*\)}}/\1/' -e 's/.*=\(.*\)2[0-9][0-9].*/name=\1/p' > ../builds/${BUILD_NUMBER}/conflict.txt {noformat} # Inject environment variables  --  {noformat}  ../builds/${BUILD_NUMBER}/conflict.txt  {noformat} #  Now you can use environment variable  *  $name *  in any additional  sets  steps .  We use it with the hipchat  notification   notifications 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jigomerge-plugin] (JENKINS-12993) Propagate relevant SVN user to UI in case of merge conflicts

2016-05-04 Thread jfill...@calliduscloud.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Fillmore commented on  JENKINS-12993 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Propagate relevant SVN user to UI in case of merge conflicts  
 
 
 
 
 
 
 
 
 
 
I have a little work around for this: 
 

Excute shell command – grep -R conflictingFiles ../builds/$ {BUILD_NUMBER}/log | sed -n -e 's/^return : .* conflictingFiles={(.)}}/\1/' -e 's/.=(.)2[0-9][0-9]./name=\1/p' > ../builds/${BUILD_NUMBER} 
/conflict.txt
 

Inject environment variables – ../builds/$ {BUILD_NUMBER} 
/conflict.txt
 

Now you can use environment variable $name in any additional sets. We use it with the hipchat notification
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-34611) SEVERE: Unexpected executor death; java.lang.IllegalStateException: /var/lib/jenkins/builds/myproject/2 already existed;

2016-05-04 Thread michelene.c...@am.sony.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 M Chon created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34611 
 
 
 
  SEVERE: Unexpected executor death; java.lang.IllegalStateException: /var/lib/jenkins/builds/myproject/2 already existed;   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/04 7:58 PM 
 
 
 

Environment:
 

 Ubuntu 14.04  Jenkins 1.642.4 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 M Chon 
 
 
 
 
 
 
 
 
 
 
We have been getting this error for the past day or so. Per instructions at https://wiki.jenkins-ci.org/display/JENKINS/Dead+Executor, am filing a JIRA bug. 
May 04, 2016 11:49:24 AM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running May 04, 2016 11:49:33 AM javax.jmdns.impl.DNSStatefulObject$DefaultImplementation waitForAnnounced WARNING: Wait for announced timed out: DNS: JSERVER07.local. state: announcing 1 task: Announcer(JSERVER07.local.) state: announcing 1 May 04, 2016 11:49:39 AM javax.jmdns.impl.DNSStatefulObject$DefaultImplementation waitForAnnounced WARNING: Wait for announced timed out: DNS: JSERVER07.local. state: probing 1 task: Prober(JSERVER07.local.) state: probing 1 May 04, 2016 11:49:45 AM javax.jmdns.impl.DNSStatefulObject$DefaultImplementation waitForAnnounced WARNING: Wait for announced timed out: DNS: JSERVER07.local. state: probing 1 task: Prober(JSERVER07.local.) state: probing 1 May 04, 2016 11:51:07 AM

[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 Hello All,I've been trying to run this plugin with Windows 2012 and i'm stuck in some WinRM loop where it cannot connect. I tried setting the  launch  delay up to  360  600  seconds to ensure my instance is up before trying any WinRM commands. No luck. Here is what i'm seeing:{code:java}Request:POST http://172.16.0.255:5985/wsmanhttp://172.16.0.252:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:24BD995E-DFCC-4B42-AF00-E5C85B66445BPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderrMay 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svc{code}I know WinRM is setup and working correctly, i can connect over Telnet. And I've run the commands suggested from the plugin:{code:java}winrm quickconfigwinrm set winrm/config/service/Auth @{Basic="true"}winrm set winrm/config/service @{AllowUnencrypted="true"}winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}{code}I do have a question in addition to the bug and that is: *Do we just need to specify and administrative user, not precisely "Administrator" ?*I've spent the entire day working on this and I'm simply out of options. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 Hello All,I've been trying to run this plugin with Windows 2012 and i'm stuck in  some WinRM loop where it cannot connect. I tried setting  the  delay up to 360 seconds to ensure my instance is up before trying any WinRM commands. No luck. Here is what i'm seeing  :{code:java}Request:POST http://172.16.0.255:5985/wsmanhttp://172.16.0.252:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:24BD995E-DFCC-4B42-AF00-E5C85B66445BPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderrMay 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svc{code}I know WinRM is setup and working correctly, i  can connect over Telnet. And I 've run the commands suggested from the plugin:{code:java}winrm quickconfigwinrm set winrm/config/service/Auth @{Basic="true"}winrm set winrm/config/service @{AllowUnencrypted="true"}winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}{code}I 'm using  do have  a  service user like BLA.AWS\svcService, which is an admin on  question in addition to  the  box  bug  and  can log into any slave AMI. Could this possibly be the reason for this issue  that is: *Do we just need to specify and administrative user, not precisely "Administrator" ? *  Otherwise i'm at a loss.  I've  configured  spent the entire day working on  this  thing like mad  and  i  I 'm  starting to rip  simply  out  my hair  of options . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [cloudbees-folder-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev assigned an issue to Jesse Glick 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34458 
 
 
 
  POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 

Assignee:
 
 Kirill Merkushev Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cloudbees-folder-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-34458 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 
 

 


"cloudbees-folder@5.8">
  H H * * *
  8640

  
 

 
You have no any enabled push triggers. So you really use simple polling with near 1 minute interval. But why it not triggers - i don't know. Seems you should adress issue to cloudbees-folder 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.

[JIRA] [cloudbees-folder-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34458 
 
 
 
  POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 

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.

[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 {code:java} Hello All,  I've been trying to run this plugin with Windows 2012 and i'm stuck in the :  {code:java}  Request:POST http://172.16.0.255:5985/wsmanhttp://172.16.0.252:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:24BD995E-DFCC-4B42-AF00-E5C85B66445BPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderrMay 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svc{code}I know WinRM is setup and working correctly, i've run the commands suggested from the plugin: {code:java} winrm quickconfigwinrm set winrm/config/service/Auth @{Basic="true"}winrm set winrm/config/service @{AllowUnencrypted="true"}winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"} {code}   I'm using a service user like BLA.AWS\svcService, which is an admin on the box and can log into any slave AMI. Could this possibly be the reason for this issue?Otherwise i'm at a loss. I've configured this thing like mad and i'm starting to rip out my hair. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 {code:java} Hello All,  I've been trying to run this plugin with Windows 2012 and i'm stuck in the : {code:java}   Request:POST http://172.16.0.255:5985/wsmanhttp://172.16.0.252:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:24BD995E-DFCC-4B42-AF00-E5C85B66445BPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderrMay 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequestwinrm returned 401 - shouldn't happen though - retrying in 2 minutesWaiting for WinRM to come up. Sleeping 10s.Connecting to ec2-windows-host.compute-1.amazonaws.com(<>) with WinRM as svc {code}   I know WinRM is setup and working correctly, i've run the commands suggested from the plugin:winrm quickconfigwinrm set winrm/config/service/Auth @{Basic="true"}winrm set winrm/config/service @{AllowUnencrypted="true"}winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}I'm using a service user like BLA.AWS\svcService, which is an admin on the box and can log into any slave AMI. Could this possibly be the reason for this issue?Otherwise i'm at a loss. I've configured this thing like mad and i'm starting to rip out my hair. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [ec2-plugin] (JENKINS-34610) Windows AMI in endless loop

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34610 
 
 
 
  Windows AMI in endless loop  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Francis Upton 
 
 
 

Attachments:
 

 JenkinsEC2Setup1.png, JenkinsEC2Setup2.png 
 
 
 

Components:
 

 ec2-plugin 
 
 
 

Created:
 

 2016/May/04 7:44 PM 
 
 
 

Environment:
 

 Jenkins 2.1, Windows Server 2012 R2, EC2 version 1.31. 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Brendan Stewart 
 
 
 
 
 
 
 
 
 
 
Hello All, 
I've been trying to run this plugin with Windows 2012 and i'm stuck in the : 
Request: POST http://172.16.0.255:5985/wsman  ="http://schemas.microsoft.com/wbem/wsman/1/wsman.xsd">http://172.16.0.252:5985/wsmanhttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous153600uuid:24BD995E-DFCC-4B42-AF00-E5C85B66445BPT60Shttp://schemas.xmlsoap.org/ws/2004/09/transfer/Createhttp://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmdFALSE437stdinstdout stderr 
May 4, 2016 4:20:46 PM WARNING hudson.plugins.ec2.win.winrm.WinRMClient sendRequest

[JIRA] [docker-workflow-plugin] (JENKINS-33063) Allow Image.run() etc to provide arguments to the container's command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33063 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow Image.run() etc to provide arguments to the container's command  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: vfarcic Path: src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy src/test/java/org/jenkinsci/plugins/docker/workflow/DockerDSLTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/8ac95891861bd5405265f9b410b2e6d02fcbeaac Log: 

JENKINS-33063
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-33063) Allow Image.run() etc to provide arguments to the container's command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33063 
 
 
 
  Allow Image.run() etc to provide arguments to the container's command  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-33063) Allow Image.run() etc to provide arguments to the container's command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33063 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow Image.run() etc to provide arguments to the container's command  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: vfarcic Path: src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy http://jenkins-ci.org/commit/docker-workflow-plugin/6a49c2225aa1d405179343a449590f84628a99da Log: 

JENKINS-33063
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-33063) Allow Image.run() etc to provide arguments to the container's command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33063 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow Image.run() etc to provide arguments to the container's command  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy src/main/resources/org/jenkinsci/plugins/docker/workflow/DockerDSL/help.jelly src/test/java/org/jenkinsci/plugins/docker/workflow/DockerDSLTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/153c70d5e863eb499b49d08d6992f3eff3ca586a Log: Merge pull request #37 from vfarcic/jenkins-33063 
[FIXED JENKINS-33063] Allow Image.run() to provide arguments to the container’s command 
Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/af5a6697a03f...153c70d5e863 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-33063) Allow Image.run() etc to provide arguments to the container's command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33063 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow Image.run() etc to provide arguments to the container's command  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: vfarcic Path: src/main/resources/org/jenkinsci/plugins/docker/workflow/DockerDSL/help.jelly http://jenkins-ci.org/commit/docker-workflow-plugin/8686313eabbb5b727607b0ef9b480ba64b7bdfbd Log: 

JENKINS-33063
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34578) Cloud Server Options dropdown menus all blank

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cloud Server Options dropdown menus all blank  
 
 
 
 
 
 
 
 
 
 

Which doesn't appear to be very useful.
 
Indeed. I am pushing 2.4 with relevant debug messages in FINEST level. Please, retry after upgrade and report the exceptions. Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34495 
 
 
 
  Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34495 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 
 
Fixed in 2.4. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34458) POST /github-webhook/ ignored if triggered within a minute

2016-05-04 Thread docw...@gerf.org (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Höltje updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34458 
 
 
 
  POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 
 
I'm using the GitHub Organization Folder, the details of the trigger are hidden from me. 
However, here is the config.xml for an Organization. The trigger section seems to only be about the folder itself, not the repository. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Höltje 
 
 
 

Attachment:
 
 config.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34458) POST /github-webhook/ ignored if triggered within a minute

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev edited a comment on  JENKINS-34458 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 
 Hmm, seems that you actually not using github-plugin to trigger your jobs. Can you show your trigger section (of job configuration) ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34458) POST /github-webhook/ ignored if triggered within a minute

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-34458 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 
 
Hmm, seems that you actually not using github-plugin to trigger your jobs. Can you show your trigger section (of job configuration) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [google-oauth-plugin] (JENKINS-34609) Google OAuth plugin should reaffirm auth on refresh

2016-05-04 Thread aa...@olark.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aaron Wilson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34609 
 
 
 
  Google OAuth plugin should reaffirm auth on refresh  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Andrey Stroilov 
 
 
 

Components:
 

 google-oauth-plugin 
 
 
 

Created:
 

 2016/May/04 6:29 PM 
 
 
 

Environment:
 

 Jenkins 1.648 
 
 
 

Labels:
 

 oauth authentication 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Aaron Wilson 
 
 
 
 
 
 
 
 
 
 
The access token provided by OAuth expires after a very short amount of time, but the acceptance is still cached, and simply clicking Login will reaffirm that acceptance and regenerate the auth token (and not present the full OAuth handshake). Rather than forcing the user to periodically click "Log In", the plugin should check that the access token is valid before the page render (and, if it already does that and is just reacting to short-lived access tokens, use a refresh token to acquire a new access token if the access token is no longer valid)

[JIRA] [github-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute

2016-05-04 Thread docw...@gerf.org (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Höltje commented on  JENKINS-34458 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POST /github-webhook/ ignored if triggered within a minute  
 
 
 
 
 
 
 
 
 
 
FYI: So I played around with commits and putting sleep between the pushes. It looks like the timing is pretty darn close to 60 seconds. 
Is it possible there is something preventing triggers if they happen too fast? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [other] (JENKINS-34608) Unable to save or to apply Configure System after upgrading to 2.1

2016-05-04 Thread baranets...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Basile Baranetskyy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34608 
 
 
 
  Unable to save or to apply Configure System after upgrading to 2.1  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 other 
 
 
 

Created:
 

 2016/May/04 6:21 PM 
 
 
 

Environment:
 

 jenkins-2.1  ubuntu 14.04LTS  java-OpenJDK-"1.7.0_95"(IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)  OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)  
 
 
 

Labels:
 

 jenkins configuration 2.0 exception 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Basile Baranetskyy 
 
 
 
 
 
 
 
 
 
 
After passing from 1.653 to 2.1 unable to apply or to save a new System Configuration And in the system logs I found: 
May 04, 2016 7:48:54 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info 
Started w.@7b7117d8 {/,file:/var/cache/jenkins/war/,AVAILABLE} {/var/cache/jenkins/war} 
May 04, 2016 7:48:54 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info

[JIRA] [ec2-plugin] (JENKINS-31641) Unclear error upon launching Windows build node

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-31641 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unclear error upon launching Windows build node  
 
 
 
 
 
 
 
 
 
 
I experience this issue as well, 6 months later. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-quality-center-plugin] (JENKINS-34606) The HP ALM Quality Center Plugin should use the Credentials Plugin

2016-05-04 Thread anthony.mastr...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Mastrean created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34606 
 
 
 
  The HP ALM Quality Center Plugin should use the Credentials Plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Michael Fazio 
 
 
 

Components:
 

 hp-quality-center-plugin 
 
 
 

Created:
 

 2016/May/04 5:44 PM 
 
 
 

Environment:
 

 hp-quality-center 1.2  jenkins 1.565.3 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Anthony Mastrean 
 
 
 
 
 
 
 
 
 
 
I would like to use this plugin, but I'd feel more comfortable with the administration/configuration if it used the Credentials plugin. 
https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [bitbucket-branch-source-plugin] (JENKINS-34607) Changes screens don't provide links to BitBucket screens

2016-05-04 Thread aherit...@apache.org (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34607 
 
 
 
  Changes screens don't provide links to BitBucket screens  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Antonio Muñiz 
 
 
 

Attachments:
 

 Screenshot 2016-05-04 19.36.50.png, Screenshot 2016-05-04 19.37.07.png, Screenshot 2016-05-04 19.44.16.png, Screenshot 2016-05-04 19.44.34.png 
 
 
 

Components:
 

 bitbucket-branch-source-plugin 
 
 
 

Created:
 

 2016/May/04 5:47 PM 
 
 
 

Environment:
 

 BitBucket Branch Source plugin 1.5 (and related scm/branch APIs) 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 
Unlike for GitHub integration with BitBucket doesn't provide links to browse changes/diffs in the BitBucket repository 
Ex with BitBucket   
Ex with GitHub   
In GitHub there is a decorator allowing to click on SHA1 and adding some githubweb entries

[JIRA] [clearcase-ucm-plugin] (JENKINS-34605) Delivery Pipeline shows "null" for activity descriptions from CC-UCM

2016-05-04 Thread evan.vand...@ngc.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evan Van Dyke created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34605 
 
 
 
  Delivery Pipeline shows "null" for activity descriptions from CC-UCM  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Praqma Support 
 
 
 

Components:
 

 clearcase-ucm-plugin, delivery-pipeline-plugin 
 
 
 

Created:
 

 2016/May/04 5:40 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Evan Van Dyke 
 
 
 
 
 
 
 
 
 
 
We have a ClearCase/ClearQuest environment, utilizing both the Clearcase-UCM and Delivery Pipeline plugins. When CC-UCM starts a new build, the "Activity log" shows all the correct change set detail for the job. However, when the Delivery Pipeline displays the activities, it shows "null" for all activity descriptions (though the activity ID and username are correct). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [scm-api-plugin] (JENKINS-34600) Improve the performance of scheduling a build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34600 
 
 
 
  Improve the performance of scheduling a build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 The current API in {{scm-api}} allows to re-index a branch source using the method {{SCMSourceOwner.onSCMSourceUpdated()}}.Currently we are using this method to force a reindexing when a webhook event is received:{code:java}for (final SCMSourceOwner owner : SCMSourceOwners.all()) {for (SCMSource source : owner.getSCMSources()) {if (source instanceof GitHubSCMSource) {GitHubSCMSource gitHubSCMSource = (GitHubSCMSource) source;if (gitHubSCMSource.getRepoOwner().equals(changedRepository.getUserName()) &&gitHubSCMSource.getRepository().equals(changedRepository.getRepositoryName())) {owner.onSCMSourceUpdated(gitHubSCMSource);}}}}{code}We need to improve this because when Jenkins receives an event from a webhook we want to be able to determinate:# if we have to re-index  all  my GitHub Organization# if we have to re-index all my branches and pull requests in a GitHub repository# Or simplify if we have to schedule a build because there is a new commit in a pull requests   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[JIRA] [scm-api-plugin] (JENKINS-34600) Improve the performance of scheduling a build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34600 
 
 
 
  Improve the performance of scheduling a build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [scm-api-plugin] (JENKINS-34600) Improve the performance of scheduling a build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34600 
 
 
 
  Improve the performance of scheduling a build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 The current API in {{scm-api}} allows to re-index a branch source using the method {{SCMSourceOwner.onSCMSourceUpdated()}}.Currently we are using this method to force a reindexing when a webhook event is received:{code:java}for (final SCMSourceOwner owner : SCMSourceOwners.all()) {for (SCMSource source : owner.getSCMSources()) {if (source instanceof GitHubSCMSource) {GitHubSCMSource gitHubSCMSource = (GitHubSCMSource) source;if (gitHubSCMSource.getRepoOwner().equals(changedRepository.getUserName()) &&gitHubSCMSource.getRepository().equals(changedRepository.getRepositoryName())) {owner.onSCMSourceUpdated(gitHubSCMSource);}}}}{code} We need to improve this because when Jenkins receives an event from a webhook we want to be able to determinate:# if we have to re-index all my GitHub Organization# if we have to re-index all my branches and pull requests in a GitHub repository# Or simplify if we have to schedule a build because there is a new commit in a pull requests    
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[JIRA] [all-changes-plugin] (JENKINS-34604) I updated Jenkins and this error appeared: I updated Jinkens this my job disappeared then I replaced the .war file and my jobs re-appeared but I got this er

2016-05-04 Thread sgardner...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Gardner created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34604 
 
 
 
  I updated Jenkins and this error appeared: I updated Jinkens this my job disappeared then I replaced the .war file and my jobs re-appeared but I got this error when trying to configure them  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 wolfs 
 
 
 

Components:
 

 all-changes-plugin 
 
 
 

Created:
 

 2016/May/04 5:28 PM 
 
 
 

Environment:
 

 Ubuntu 14.04 
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Steven Gardner 
 
 
 
 
 
 
 
 
 
 
I updated Jinkens this my job disappeared then I replaced the .war file and my jobs re-appeared but I got this error when trying to configure them 
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list

[JIRA] [workflow-plugin] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator

2016-05-04 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34590 
 
 
 
  Fail to generate correct input step with choice param syntax from snippet generator  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator

2016-05-04 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34590 
 
 
 
  Fail to generate correct input step with choice param syntax from snippet generator  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-34603) git scm poll not working with global environment variable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 smruti sahoo commented on  JENKINS-34603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git scm poll not working with global environment variable  
 
 
 
 
 
 
 
 
 
 
A similar issue raised earlier https://issues.jenkins-ci.org/browse/JENKINS-26315 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-34603) git scm poll not working with global environment variable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 smruti sahoo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34603 
 
 
 
  git scm poll not working with global environment variable  
 
 
 
 
 
 
 
 
 

Change By:
 
 smruti sahoo 
 
 
 
 
 
 
 
 
 
 Steps to reproduce -Manage Jenkins => Configure System => Global properties => Environment variables Add Name = GITHUB_HOSTValue = Name = GITHUB_REPOValue = Create a job Under job configuration define git repository as belowhttps://${GITHUB_HOST}/${GITHUB_REPO}provide user/pass for credential complete the job configuration Trigger SCM poll by using curl (Note - provide your Jenkins host in following command)curl http://${JENKINS_SERVER}/jenkins/git/notifyCommit?url="" />It'll poll the corresponding job but if you see Git SCM poll log, it's dumping the following error {color:red} In short - It's not able to expand the global variable {color} > /usr/bin/git --version # timeout=10 > /usr/bin/git -c core.askpass=true fetch --tags --progress https://${GITHUB_HOST}/${GITHUB_REPO} +refs/heads/*:refs/remotes/origin/*FATAL: hudson.plugins.git.GitException: Failed to fetch from https://${GITHUB_HOST}/${GITHUB_REPO}hudson.util.IOException2: hudson.plugins.git.GitException: Failed to fetch from https://${GITHUB_HOST}/${GITHUB_REPO} at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:573) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1468) at hudson.model.AbstractProject._poll(AbstractProject.java:1438) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:526) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:555) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: hudson.plugins.git.GitException: Failed to fetch from https://${GITHUB_HOST}/${GITHUB_REPO} at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:701) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:571) ... 14 moreCaused by: hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true fetch --tags --progress https://${GITHUB_HOST}/${GITHUB_REPO} +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: remote: Invalid username or password.

[JIRA] [git-plugin] (JENKINS-34603) git scm poll not working with global environment variable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 smruti sahoo edited a comment on  JENKINS-34603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git scm poll not working with global environment variable  
 
 
 
 
 
 
 
 
 
 If I'm triggering the job manually either individually or build pipeline - It's working as expectedIt's failing only  when  for  "Poll SCM"  Because But because  of this the notification mails are not getting triggered upon git commit  which is causing big 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] [git-plugin] (JENKINS-34603) git scm poll not working with global environment variable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 smruti sahoo edited a comment on  JENKINS-34603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git scm poll not working with global environment variable  
 
 
 
 
 
 
 
 
 
 If I'm triggering the job manually either individually or build pipeline - It's working as expectedIt's failing only when  for  "Poll SCM"  Because of this the notification mails are not getting triggered upon git commit   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-34603) git scm poll not working with global environment variable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 smruti sahoo commented on  JENKINS-34603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: git scm poll not working with global environment variable  
 
 
 
 
 
 
 
 
 
 
If I'm triggering the job manually either individually or build pipeline - It's working as expected It's failing only when for "Poll SCM"  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-34603) git scm poll not working with global environment variable

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 smruti sahoo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34603 
 
 
 
  git scm poll not working with global environment variable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 2016/May/04 4:53 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 smruti sahoo 
 
 
 
 
 
 
 
 
 
 
Steps to reproduce - 
Manage Jenkins => Configure System => Global properties => Environment variables  Add  Name = GITHUB_HOST Value =  
Name = GITHUB_REPO Value =  
Create a job  Under job configuration define git repository as below https://$ {GITHUB_HOST}/${GITHUB_REPO} provide user/pass for credential  complete the job configuration   Trigger SCM poll by using curl (Note - provide your Jenkins host in following command)  curl http://${JENKINS_SERVER}/jenkins/git/notifyCommit?url="">"{GITHUB_HOST}"/\$"{GITHUB_REPO}"  It'll poll the corresponding job but if you see Git SCM poll log, it's dumping the following error  It's not able to expand the global variable   > /usr/bin/git --version # timeout=10 > /usr/bin/git -c core.askpass=true fetch --tags --progress https://${GITHUB_HOST} 
/$ {GITHUB_REPO} +refs/heads/:refs/remotes/origin/ FATAL: hudson.plugins.git.GitException: Failed to fetch from https://${GITHUB_HOST}/${GITHUB_REPO} 
hudson.util.IOException2: hudson.plugins.git.GitException: Failed to fetch from https://$ {GITHUB_HOST}/${GITHUB_REPO} at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:573) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at

[JIRA] [ec2-plugin] (JENKINS-4995) Support windows AMI's in EC2 plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-4995 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support windows AMI's in EC2 plugin  
 
 
 
 
 
 
 
 
 
 
Another plus vote here to get this working by default. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [scm-api-plugin] (JENKINS-34600) Improve the performance of scheduling a build

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34600 
 
 
 
  Improve the performance of scheduling a build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 Improve the performance of  schedule  scheduling  a build 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator

2016-05-04 Thread amu...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34590 
 
 
 
  Fail to generate correct input step with choice param syntax from snippet generator  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonio Muñiz 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator

2016-05-04 Thread amu...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-34590 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fail to generate correct input step with choice param syntax from snippet generator  
 
 
 
 
 
 
 
 
 
 
Right, duplicated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator

2016-05-04 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34590 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fail to generate correct input step with choice param syntax from snippet generator  
 
 
 
 
 
 
 
 
 
 
Patrick Wolf No, this one is specific to the ChoiceParameterDefinition type and inconsistency in its definition. Looks more like JENKINS-26143. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-34590) Fail to generate correct input step with choice param syntax from snippet generator

2016-05-04 Thread amu...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-34590 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fail to generate correct input step with choice param syntax from snippet generator  
 
 
 
 
 
 
 
 
 
 
Patrick Wolf I don't think so. This one is about the snippet generator picking up a wrong constructor. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Do not suppress unmergeable PRs  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/c6ac8156e5f5ba3e1e7277ba1d059ff515fe42e2 Log: Merge pull request #51 from recena/

JENKINS-34120
 


JENKINS-34120
 Mergeability is not a condition to add a new job linked to a PR 
Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/4970dbc528f0...c6ac8156e5f5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Do not suppress unmergeable PRs  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/df2fc42f25cd4f0f220c00b4a75d2e0c25633408 Log: 

JENKINS-34120
 Mergeability is not a condition to add a new job for a PR 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs