date:20170221

2017-02-21 Thread stephen.alan.conno...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-42140  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow using 'emailext' step in pipeline without 'node'/workspace context   
 

  
 
 
 
 

 
 David van Laatum: Thanks for the extremely quick implementation!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-39207) "RSS for all" shows only a few builds

2017-02-21 Thread ronny.borch...@muehlbauer.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-39207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "RSS for all" shows only a few builds   
 

  
 
 
 
 

 
 We have jobs with more than 1200 build executions. There is under the link http:// ro-soft3- srv. ger here . muehlbauer comp . de org :8080/job/JobName/rssAll more than in table viewed but not all. Same for failed builds. It seems there is somewhere a break, which prefents that really all builds are shown. I looks like just the last 5 or 7 days are shown.  Please find attached anonymouse generated rssAll file: [^rssAll.txt]   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-36121  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Branch Source plugin trips api rate limit   
 

  
 
 
 
 

 
 Paul Chubatyy thanks for that, my anon scan completed just fine (after 4 hours) so I guess I got lucky with where the org repos fell. The anon access token is probably going to be most problematic with this as 60 is really not much and you need to wait an hour between tests if they fail (or hop VPNs  )  I expect that the -SNAPSHOT should work much better when given a real rate limit (i.e. 5000/hr)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38984) Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä

2017-02-21 Thread r.baeris...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Baeriswyl commented on  JENKINS-38984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä   
 

  
 
 
 
 

 
 I'm facing the same issue. Can this be addressed sometime soon?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"

2017-02-21 Thread d.wilmer.1...@googlemail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Wilmer commented on  JENKINS-27170  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install"   
 

  
 
 
 
 

 
 Yes, I have EnvInject installed. So I will stay on 0.2.2 until JENKINS-26583 is fixed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42213) Changes in POM

2017-02-21 Thread egutier...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42213  
 
 
  Changes in POM   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Evaristo Gutierrez  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2017/Feb/21 9:05 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Evaristo Gutierrez  
 

  
 
 
 
 

 
 
 
Update baseline according to plugin dependencies. 
Check java.level is set to correct version. 
Bump and include plugins to fix PCT for 2.32.2 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-42196) Eliminate overly-eager SSE ping request

2017-02-21 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42196  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Eliminate overly-eager SSE ping request   
 

  
 
 
 
 

 
 Code changed in jenkins User: Tom Fennelly Path: package.json src/main/js/SSEConnection.js http://jenkins-ci.org/commit/sse-gateway-plugin/c225bf976b0b0b42aadea1135eef7392e8dcd721 Log: [FIX JENKINS-42196] Eliminate overly-eager SSE ping request (#18) 
 
Only ping after giving the connection a chance to heal itself 
 
 
0.0.19-tf-JENKINS-42196-1 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-35352) unclassified field org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper result when trying to call setResult on wrong type

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-35352  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unclassified field org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper result when trying to call setResult on wrong type   
 

  
 
 
 
 

 
 Sergey Kovin and Jesse Glick: I think there are two "problems": 
 
The line currentBuild.result = hudson.model.Result.FAILURE actually fails, because currently (unfortunately) the result can only be set based on String. See org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper#setResult(...): 

 

@Whitelisted
public void setResult(String result) throws AbortException {
if(!this.currentBuild) {
throw new SecurityException("can only set the result property on the current build");
} else {
this.build().setResult(Result.fromString(result));
}
}
 

 
 
=> So you could use currentBuild.result = hudson.model.Result.FAILURE.toString(), I guess. 
=> Jesse Glick would it be possible to also allow using hudson.model.Result (directly), which would be type/typo-safe? (For backwards compatibility of course the old String based approach needs to be kept, I assume.) 
  
After this change, however, I think the second problem should pop up: namely that hudson.model.Result.FAILURE is not whitelisted either. 
 
=> Jesse Glick Would it be possible to whitelist all static result states from hudson.model.Result, e.g.: staticField hudson.model.Result FAILURE? 
  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"

2017-02-21 Thread nfalc...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27170  
 
 
  "Provide Node & npm bin/ folder to PATH" not working for "npm install"   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38984) Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä

2017-02-21 Thread r.baeris...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Baeriswyl commented on  JENKINS-38984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch Indexing / Folder Computation fails if branch name contains german umlauts like ü, ö or ä   
 

  
 
 
 
 

 
 I think a possible fix would be to UrlEncoder.encode the branch variable in checkPathExists (and possibly other places) in BitbucketServerAPIClient.java. Unfortunately I do not have experience with jenkins plugins so I cannot really test this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-31899) plugin Dashboard View does not recognizes job names from mutli-branch-project-plugin

2017-02-21 Thread lj.morito...@web.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Moritz Wirger commented on  JENKINS-31899  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: plugin Dashboard View does not recognizes job names from mutli-branch-project-plugin   
 

  
 
 
 
 

 
 I just fixed this issue in my Pullrequest  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42213) Changes in POM

2017-02-21 Thread egutier...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated  JENKINS-42213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42213  
 
 
  Changes in POM   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42213) Changes in POM

2017-02-21 Thread egutier...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez started work on  JENKINS-42213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42204) Scan of git pipeline fails with NPE due to recent GitSCMSource change

2017-02-21 Thread j...@caraldi.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 jbq commented on  JENKINS-42204  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scan of git pipeline fails with NPE due to recent GitSCMSource change   
 

  
 
 
 
 

 
 See https://github.com/jenkinsci/git-plugin/pull/475 NOTE: instructions were slightly off, I had to issue a `git lfs checkout` before `docker build`. Never used `git lfs` before but I could figure out by myself as the plugin files only contained git commit references.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins

2017-02-21 Thread christian07.schnei...@conti.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Schneider commented on  JENKINS-31464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-client uses proxy from plugins section of jenkins   
 

  
 
 
 
 

 
 withEnv does not help. I think, because "These are available to any external processes spawned within that scope." (and they are available to the external processes already). Even setting env.http_proxy directly in the pipeline does not help. The question would probably be which EnvVars is passed to CliGitAPIImpl in the first place. But I can't afford the time for setting up a complete debug environment for this. Seems I will need to checkout via command line without using the git plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 Since the "that then needs to be caught by whatever does the registering" is already happening, maybe the currently working approach should just be officially documented: 

 

try {
  ... // Something that could also throw a RejectedAccessException
} catch (e) {
	... // Do something due to the failure or based on the failure like sending a notification email

	// While there would be no need to re-throw the exception to propagate the error (because the build result must be set
	// to failure for email-ext anyhow before), re-throw it for e.g. script approval requests:
	throw e
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder edited a comment on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 Since the "_that then needs to be caught by whatever does the registering_" is already happening, maybe the currently working approach should just be officially documented:{code}try {  ... // Something that could also throw a RejectedAccessException} catch (e) { ... // Do something due to the failure or based on the failure like sending a notification email // While there would be no need to re-throw the exception to propagate the error (because the build result must be set // to failure for email-ext anyhow before), re-throw it for e.g. script approval requests: throw e}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

2017-02-21 Thread tom.fenne...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
 

should just be officially documented
 Who reads documentation? (Tongue in cheek)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38751) run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job

2017-02-21 Thread tom.fenne...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY started work on  JENKINS-38751  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42214) Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42214  
 
 
  Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 script-security-plugin  
 
 
Created: 
 2017/Feb/21 10:09 AM  
 
 
Environment: 
 Jenkins 2.46, Script Security Plugin 1.26  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Reinhold Füreder  
 

  
 
 
 
 

 
 Since hudson.scm.EditType implementation has not changed in the last 10 years, I think either the white listing never ever worked, or (less likely?) the white listing syntax changed and in the past there was no differentiation between static and non-static fields. Anyway, could you please change the following in "org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/jenkins-whitelist": 
 
From old: 

 
field hudson.scm.EditType ADD
field hudson.scm.EditType DELETE
field hudson.scm.EditType EDIT
 

 
=> New: 

 
staticField hudson.scm.EditType ADD
staticField hudson.scm.EditType DELETE
staticField hudson.scm.EditType EDIT

[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-34973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RejectedAccessException thrown but no pending script approval added   
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42164) Exceptions during Jenkins#cleanup() should not block the restart logic

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Yes, released in 2.47  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42164  
 
 
  Exceptions during Jenkins#cleanup() should not block the restart logic   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-39550) "Pipe not connected" with parallel steps

2017-02-21 Thread j...@goyeau.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joan Goyeau commented on  JENKINS-39550  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Pipe not connected" with parallel steps   
 

  
 
 
 
 

 
 Hi, Is there any update on this issue? At least why does this happen? Maybe we can help... Cheers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41397) API to validate Git credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41397  
 
 
  API to validate Git credentials   
 

  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Assignee: 
 pamidu jayaranga Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41397) API to validate Git credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga assigned an issue to pamidu jayaranga  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41397  
 
 
  API to validate Git credentials   
 

  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Assignee: 
 Vivek Pandey pamidu jayaranga  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41841) Liquibase runner pipeline support for Oracle engine

2017-02-21 Thread piotr.minkow...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Piotr Minkowski commented on  JENKINS-41841  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Liquibase runner pipeline support for Oracle engine   
 

  
 
 
 
 

 
 I tried to set that configuration: 

 

liquibaseUpdate changeLogFile: 'src/main/script/changelog-master.xml', url: 'jdbc:oracle:thin:@10.10.99.9:1521:PSDB', credentialsId: 'BSA_PREPROD', classpath: "/home/cicdadm/ojdbc7-12.1.0.1.jar", driverClassname: 'oracle.jdbc.driver.OracleDriver'
 

 And I get following exception: java.lang.RuntimeException: Error registering database driver oracle.jdbc.driver.OracleDriver at org.jenkinsci.plugins.liquibase.evaluator.AbstractLiquibaseBuilder.createJdbcConnection(AbstractLiquibaseBuilder.java:243) at org.jenkinsci.plugins.liquibase.evaluator.AbstractLiquibaseBuilder.createLiquibase(AbstractLiquibaseBuilder.java:164) at org.jenkinsci.plugins.liquibase.evaluator.AbstractLiquibaseBuilder.perform(AbstractLiquibaseBuilder.java:129) at org.jenkinsci.plugins.liquibase.workflow.LiquibaseUpdateExecution.run(LiquibaseUpdateExecution.java:45) at org.jenkinsci.plugins.liquibase.workflow.LiquibaseUpdateExecution.run(LiquibaseUpdateExecution.java:15) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:40) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:109) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1280) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1174) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1024) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:812) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1280) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1174) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1024) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:16) at WorkflowScript.run(WorkflowScript:15) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:48) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor542.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor539.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invo

[JIRA] (JENKINS-41397) API to validate Git credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41397  
 
 
  API to validate Git credentials   
 

  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Assignee: 
 pamidu jayaranga Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42135) Pipeline Creation last steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga stopped work on  JENKINS-42135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41397) API to validate Git credentials

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga assigned an issue to pamidu jayaranga  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41397  
 
 
  API to validate Git credentials   
 

  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Assignee: 
 Vivek Pandey pamidu jayaranga  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42135) Pipeline Creation last steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga started work on  JENKINS-42135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42196) Eliminate overly-eager SSE ping request

2017-02-21 Thread tom.fenne...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated  JENKINS-42196  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42196  
 
 
  Eliminate overly-eager SSE ping request   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42135) Pipeline Creation last steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga started work on  JENKINS-42135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42135) Pipeline Creation last steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga stopped work on  JENKINS-42135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-39922) Upgrade Jenkins Docker Agent images to Remoting 3

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39922  
 
 
  Upgrade Jenkins Docker Agent images to Remoting 3
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Nicolas De Loof Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-39922) Upgrade Jenkins Docker Agent images to Remoting 3

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-39922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42135) Pipeline Creation last steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga stopped work on  JENKINS-42135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42135) Pipeline Creation last steps

Title: Message Title


 
 
 
 

 
 
 

 
   
 pamidu jayaranga started work on  JENKINS-42135  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 pamidu jayaranga  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-39922) Upgrade Jenkins Docker Agent images to Remoting 3

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade Jenkins Docker Agent images to Remoting 3
 

  
 
 
 
 

 
 Created https://github.com/jenkinsci/docker-slave/pull/3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-39922) Upgrade Jenkins Docker Agent images to Remoting 3

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-39922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39922  
 
 
  Upgrade Jenkins Docker Agent images to Remoting 3
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42215) vSphere-cloud-plugin add feature to Delete/Rename Template

2017-02-21 Thread bryanhund...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bryan Hundven created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42215  
 
 
  vSphere-cloud-plugin add feature to Delete/Rename Template   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 vsphere-cloud-plugin  
 
 
Created: 
 2017/Feb/21 11:18 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bryan Hundven  
 

  
 
 
 
 

 
 I have a pipeline that creates a new vm with packer.io. At the end of the process, I have a final stage that converts the vm to a template with the vsphere cloud plugin. It would be nice to delete or rename the previous template before I convert the vm to a template.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis commented on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createItem in View not working when posting xml   
 

  
 
 
 
 

 
 +1 this is a blocker for moving from 1.6 to 2.x series for us. The issue exists in both: 2.3 and 2.4 (jenkins:latest and jenkinsci/jenkins on Docker Hub). Is there a workaround? Markus Winter  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis edited a comment on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createItem in View not working when posting xml   
 

  
 
 
 
 

 
 +1 this is a blocker for moving from 1.6 to 2.x series for us. The issue exists in both: 2.3 and 2.4 (jenkins:latest and jenkinsci/jenkins on Docker Hub).Is there a workaround? [~mawinter69] Related: https://issues.jenkins-ci.org/browse/JENKINS-9264  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis commented on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createItem in View not working when posting xml   
 

  
 
 
 
 

 
 Also pinging Vincent Latombe  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createItem in View not working when posting xml   
 

  
 
 
 
 

 
 Yep, it seems to be a valid regression for this API  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev edited a comment on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createItem in View not working when posting xml   
 

  
 
 
 
 

 
 Yep, it seems to be a valid regression for this API . Explicit JENKINS-9264 fix would be really nice  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41128  
 
 
  createItem in View not working when posting xml   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 jenkins2.0 regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-9264) Create a new job into a view via REST API

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis commented on  JENKINS-9264  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create a new job into a view via REST API   
 

  
 
 
 
 

 
 This feature was implemented (fixed) and working, then unfortunately regression was introduced in 2.x see also: https://issues.jenkins-ci.org/browse/JENKINS-41128  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42127) SAML plugin crashes with Maximum Authentication Lifetime set to greater then 24 days

2017-02-21 Thread ifernandezca...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-42127  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML plugin crashes with Maximum Authentication Lifetime set to greater then 24 days   
 

  
 
 
 
 

 
 It is planned to upgrade this library on JENKINS-39602  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-19142) Don't add jobs to a view

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Causes regression in createItem by view in Jenkins 2.0 and onwards. Please consider reverting changes or making the code which expects a form submission optional, not mandatory. See related bug notes for more details.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-19142  
 
 
  Don't add jobs to a view   
 

  
 
 
 
 

 
Change By: 
 Alex Ellis  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiv

[JIRA] (JENKINS-41200) Developer can see ANSI color in log file

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-41200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can see ANSI color in log file   
 

  
 
 
 
 

 
 I just wanted to file a more general Jenkins Blue Ocean issue to support hudson.console.ConsoleNote (and all sub-classes), although admittedly at the moment HyperlinkNote and the ANSI color are my only actual usages.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-19142) Don't add jobs to a view

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe commented on  JENKINS-19142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Don't add jobs to a view   
 

  
 
 
 
 

 
 Please don't reopen this issue because it caused a regression. There is already JENKINS-41128 opened to track the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-19142) Don't add jobs to a view

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-19142  
 
 
  Don't add jobs to a view   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-19142) Don't add jobs to a view

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis edited a comment on  JENKINS-19142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Don't add jobs to a view   
 

  
 
 
 
 

 
 Technically  it  the code contributed for this fix  will have to change to accommodate the breakage , so . So  it may need to be re-opened for re-testing. Also does it make sense to request a regression test from the original fixer? Does the project have any regression tests on top of the unit tests?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-19142) Don't add jobs to a view

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Ellis commented on  JENKINS-19142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Don't add jobs to a view   
 

  
 
 
 
 

 
 Technically it will have to change to accommodate the breakage, so it may need to be re-opened for re-testing. Also does it make sense to request a regression test from the original fixer? Does the project have any regression tests on top of the unit tests?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-35099) Jenking not able to build project resides on Virtual Drive

2017-02-21 Thread lionel.cabas...@laposte.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lionel Cabasson closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35099  
 
 
  Jenking not able to build project resides on Virtual Drive   
 

  
 
 
 
 

 
Change By: 
 Lionel Cabasson  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 kdsweeney Lionel Cabasson  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding

2017-02-21 Thread lionel.cabas...@laposte.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lionel Cabasson reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-24132  
 
 
  MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding   
 

  
 
 
 
 

 
Change By: 
 Lionel Cabasson  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Resolved Reopened  
 
 
Assignee: 
 kdsweeney Lionel Cabasson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding

2017-02-21 Thread lionel.cabas...@laposte.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lionel Cabasson resolved as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Provided by chichimotsu in PR #29 and included in release 1.27  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-24132  
 
 
  MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding   
 

  
 
 
 
 

 
Change By: 
 Lionel Cabasson  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit

[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException

2017-02-21 Thread juha.tiensy...@arm.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Juha Tiensyrjä commented on  JENKINS-42048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot Connect, PID NumberFormatException   
 

  
 
 
 
 

 
 I could probably find some time for debugging this week. Just let me know what to do.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException

2017-02-21 Thread ioca...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Canellos commented on  JENKINS-42048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot Connect, PID NumberFormatException   
 

  
 
 
 
 

 
 Can you set the `workingDir` on the jnlp container and tell me if that makes any difference?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-37392) Add @Symbol("msbuild") to MSBuild's ToolDescriptor

2017-02-21 Thread lionel.cabas...@laposte.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lionel Cabasson updated  JENKINS-37392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released in 1.27  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37392  
 
 
  Add @Symbol("msbuild") to MSBuild's ToolDescriptor   
 

  
 
 
 
 

 
Change By: 
 Lionel Cabasson  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36385) Cannot use MSbuild in loop to build multiple projects in single action

2017-02-21 Thread lionel.cabas...@laposte.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lionel Cabasson resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36385  
 
 
  Cannot use MSbuild in loop to build multiple projects in single action   
 

  
 
 
 
 

 
Change By: 
 Lionel Cabasson  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding

2017-02-21 Thread mark.zieg...@rakekniven.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 rake kniven commented on  JENKINS-24132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding   
 

  
 
 
 
 

 
 Hello,  does the new chcp call has any impact on binary build output? Will my exe differ after calling chcp? I have a Delphi build slave and it omplains about not finding chcp command. I know how to fix this and thought about any side effects. Cheers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe commented on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: createItem in View not working when posting xml   
 

  
 
 
 
 

 
 I agree this is a regression however adding a job to a view programmatically was not documented (at least in the embedded documentation). If you check out /api/, you'll see a Create Job section, which you don't see if you go to /view//api/. A workaround is to add the job without using the view, then use the view API /view//addJobToView to add it to the view.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42214) Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I apologize for the direct assignment to you, Jesse, but I dared to do that, because (a) you seem to be the official maintainer of the plugin (see https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin) and (b) I hope this is a low hanging fruit   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42214  
 
 
  Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static   
 

  
 
 
 
 

 
Change By: 
 Reinhold Füreder  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, vis

[JIRA] (JENKINS-40849) Script security should whitelist Result classes

2017-02-21 Thread benjamin.ru...@conducta.endress.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-40849  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Script security should whitelist Result classes   
 

  
 
 
 
 

 
 Kind of related to JENKINS-35352  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding

2017-02-21 Thread lionel.cabas...@laposte.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lionel Cabasson commented on  JENKINS-24132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding   
 

  
 
 
 
 

 
 Hello, This change won't impact the binary built by msbuild. However, it changes the encoding of the log generated by msbuild. If anything in your build process parses this output, it will be impacted and might behave differently. I hope this answers your question. Regards  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException

2017-02-21 Thread juha.tiensy...@arm.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Juha Tiensyrjä commented on  JENKINS-42048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot Connect, PID NumberFormatException   
 

  
 
 
 
 

 
 I tried that, the problem seems to be the same: 

 
[Pipeline] node
Running on test-55f1b2f811564473b115b8af4962a8ad-1b98a80d910eec in /var/tmp/workspace/Playground/test-JENKINS-42048
[Pipeline] {
[Pipeline] sh
[test-JENKINS-42048] Running shell script
+ echo Foo
Foo
+ sleep 10
[Pipeline] container
[Pipeline] {
[Pipeline] sh
[test-JENKINS-42048] Running shell script
Executing shell script inside container [jnlp] of pod [test-55f1b2f811564473b115b8af4962a8ad-1b98a80d910eec]
Executing command: sh -c echo $$ > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/pid'; jsc=durable-51e972f92a0e472b7953c41703e464ca; JENKINS_SERVER_COOKIE=$jsc '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/script.sh' > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-log.txt' 2>&1; echo $? > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-result.txt' 
$ cd "/var/tmp/workspace/Playground/test-JENKINS-42048"
sh -c echo $$ > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/pid'; jsc=durable-51e972f92a0e472b7953c41703e464ca; JENKINS_SERVER_COOKIE=$jsc '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/script.sh' > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-log.txt' 2>&1; echo $? > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-result.txt' 
exit
$ + echo Bar
Bar
+ sleep 10
Cannot contact test-55f1b2f811564473b115b8af4962a8ad-1b98a80d910eec: java.io.IOException: corrupted content in /var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/pid: java.lang.NumberFormatException: For input string: ""
...
 

 The container and the directory is the same, only difference is that first I call it directly from within a node block, then I call it from within a container block.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-38268) Parallel step and closure scope

2017-02-21 Thread nadavgol...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nadav Goldin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38268  
 
 
  Parallel step and closure scope   
 

  
 
 
 
 

 
Change By: 
 Nadav Goldin  
 
 
Attachment: 
 pipeline_steps.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config

2017-02-21 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42216  
 
 
  Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2017/Feb/21 2:12 PM  
 
 
Environment: 
 Jenkins 2.32.2  Pipeline Groovy 2.27  TFS Plugin 5.3.1  
 
 
Labels: 
 stapler  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Beck  
 

  
 
 
 
 

 
 Possibly bug in CpsScmFlowDefinition, or a Stapler issue. Install Pipeline and TFS Plugin. Create a Pipeline job. TFVC is offered in the 'Pipeline from SCM' when it shouldn't be, as it's missing the checkout(Job) override (and doesn't override isApplicable(Job)). Configure 'Pipeline from SCM: None", Apply, and reload. It will select Git, as it's the only applicable one now (NullSCM isn't either).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-41626) Branch indexing on subversion repo does not work properly

2017-02-21 Thread j.fe...@virtalis.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Femia updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41626  
 
 
  Branch indexing on subversion repo does not work properly   
 

  
 
 
 
 

 
Change By: 
 James Femia  
 
 
Component/s: 
 subversion-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38268) Parallel step and closure scope

2017-02-21 Thread nadavgol...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nadav Goldin commented on  JENKINS-38268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel step and closure scope   
 

  
 
 
 
 

 
 Hi, I'm experiencing what I think is a symptom of the same issue, while trying to trigger parallel builds, take this pipeline job, assuming the dummy jobs 'job-1,2,3' exists: 

 

@NonCPS
def get_dummy_params(val)
{
return [string(name: 'dummy', value: "$val")]
}

@NonCPS
def create_jobs()
{
def jobs = [:]
(1..3).each { jobs["job-$it"] = { -> build([job: "job-$it", parameters: get_dummy_params(it) ]) } }
return jobs
}

stage ('triggering') {
parallel(create_jobs())
}
 

 I would expect it to trigger the 3 jobs in parallel, instead it 'nests' under 'job-1' branch all 3 jobs, and creates empty branches for 'job-2' and 'job-3', causing the job to never end. Console output: 

 

Started by user admin
[Pipeline] stage
[Pipeline] { (triggering)
[Pipeline] parallel
[Pipeline] [job-1] { (Branch: job-1)
[Pipeline] [job-1] build (Building job-1)
[job-1] Scheduling project: job-1
[Pipeline] [job-2] { (Branch: job-2)
[Pipeline] [job-1] build (Building job-2)
[job-1] Scheduling project: job-2
[Pipeline] [job-3] { (Branch: job-3)
[Pipeline] [job-1] build (Building job-3)
[job-1] Scheduling project: job-3 !pipeline_steps.png|thumbnail! 
[job-1] Starting building: job-3 #1
...
 

 I found only 2 workarounds: 1. Don't use any functions to generate data fed into 'parallel' function(i.e. create everything under the 'stage' step).  2. Feeding a newly created map to parallel and redefining the groovy closures with a '.call()' (frankly I have no idea how I came up with this).  I.e. replace the 'stage' in the previous example with: 

 

stage ('triggering') {
def jobs = create_jobs()
parallel([
'job-1': { jobs['job-1'].call() },
'job-2': { jobs['job-2'].call() },
'job-3': { jobs['job-3'].call() },
])
}
 

 Output as expected: 

 

Started by user admin
[Pipeline] stage
[Pipeline] { (triggering)
[Pipeline] parallel
[Pipeline] [job-1] { (Branch: job-1)
[Pipeline] [job-2] { (Branch: job-2)
[Pipeline] [job-3] { (Branch: job-3)
[Pipeline] [job-1] build (Building job-1)
[job-1] Scheduling project: job-1
[Pipeline] [job-2] build (Building job-2)
[job-2] Scheduling project: job-2
[Pipeline] [job-3] build (Building job-3)
[job-3] Scheduling project: job-3
[job-1] Starting building: job-1 #2
[job-2] Starting building: job-2 #2
[Pipeline] [job-2] }
[job-3] Starting building: job-3 #2
[Pipeline] [job-1] }
[Pipeline] [job-3] }
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] End of Pipeline
Finished: SUCCESS

[JIRA] (JENKINS-26004) Priority option in multijob projects

2017-02-21 Thread ronny.borch...@muehlbauer.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-26004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Priority option in multijob projects   
 

  
 
 
 
 

 
 Today, I had this issue, too. I have 5 build processors. It would be nice if the job start algorithm would, prefer jobs which are not a multi job, this should solve this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42217) Post-build-email directs to all-changes page instead of detailed build ID page

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Ruopp created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42217  
 
 
  Post-build-email directs to all-changes page instead of detailed build ID page   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 James Dumay  
 
 
Components: 
 display-url-api-plugin  
 
 
Created: 
 2017/Feb/21 2:32 PM  
 
 
Environment: 
 2.47  
 
 
Labels: 
 Post-build mails suffix page changes all-changes  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Ben Ruopp  
 

  
 
 
 
 

 
 Post-build mails suffixes "?page=changes" to the former detail URL. J2.47 See  Better See  As long it is not configurable it looks like a bug?!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException

2017-02-21 Thread mbtcoll...@hotmail.co.uk (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcus Collins commented on  JENKINS-41867  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scanning MultiBranchProject fails with IllegalStateException   
 

  
 
 
 
 

 
 Hello, I have found that if I leave the branch-api plugin at my current version (1.11.1), the issue does not occur in our normal system. I have also tested the above HPI file with the latest plugins in a sandbox Jenkins installation and this also fixed the issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException

2017-02-21 Thread lukas.gorn...@virtual-identity.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lukas Gorniak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41867  
 
 
  Scanning MultiBranchProject fails with IllegalStateException   
 

  
 
 
 
 

 
Change By: 
 Lukas Gorniak  
 
 
Comment: 
 Applied the attachment.At workspace creation got following:before:Building in workspace /var/lib/jenkins/workspace//after:Building in workspace /var/lib/jenkins/workspace/-4TOVGLFN5C3CTYYWFGKYLHKOU7QZGTMTJYJZQFYWXZ7XBF3GTW6A  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38508) git scm poll doesn't ignore changes with pipeline

2017-02-21 Thread ansgar.binnin...@ars.de (JIRA)

Title: Message Title

Ansgar B edited a comment on JENKINS-38508

Re: git scm poll doesn't ignore changes with pipeline

I have here a small Explanation on StackOverflow with the same/similar case. Maybe it could help you to understand what the problem with the polling is.[http://stackoverflow.com/questions/40017034/jenkins-pipeline-poll-scm-with-different-repo-for-jenkinsfile-and-application-re]I try to summarize the problem we have at our company.We have two repositories. One for the configuration of Jenkinsfiles (config-repo) and on for our Development (dev-repo) , which is included in the Jenkinsfile .In Jenkins we have 3 Jobs for deployment of the dev-repo. One for dev branch, one for hotfixe hotfix branch and one for release branch. --> Jenkinsfiles are located in the config-repo. the git step in the Jenkinsfile check out the dev-repo. If i check new code into the config-repo, the builds aren't triggered, but if we check new code into dev-repo after a checkin/change in the config-repo all jobs configured with the config-repo and using the dev-repo starts a build.The Jobs should never start a build after checkins into config-repo and only starts a build, if new code is checked into their specific branch at the dev-repo .

Add Comment

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe started work on  JENKINS-41128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41128) createItem in View not working when posting xml