[JIRA] (JENKINS-36009) configure node not possible
Title: Message Title Jan-Hendrik Plogmann resolved as Fixed Thanks, updating the Credentials plugin solved the problem. Jockel Jenkins / JENKINS-36009 configure node not possible Change By: Jan-Hendrik Plogmann 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
[JIRA] (JENKINS-27350) "Performance Report" on each job don't have link text and the graph picture is missing.
Title: Message Title Hitesh Patel edited a comment on JENKINS-27350 Re: "Performance Report" on each job don't have link text and the graph picture is missing. Broken again with fix for when fixing JENKINS-28733 from commit 04537b112b440f29b0e87cccb7cf9bbb7edf7c6f. 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-36489) Fix potential NPE in MultiBranchPipelineImpl.getWeatherScore()
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36489 Fix potential NPE in MultiBranchPipelineImpl.getWeatherScore() Issue Type: Bug Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jul/07 5:30 AM Priority: Minor Reporter: Vivek Pandey In case where there are no runs across all branches, MultiBranchPipelineImpl.getWeaterScore() can generate NPE. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36487) Update code violation comments to Atlassian-hosted BitBucket Cloud
Title: Message Title Balaji Renganathan updated an issue Jenkins / JENKINS-36487 Update code violation comments to Atlassian-hosted BitBucket Cloud Change By: Balaji Renganathan Summary: Update code violation comments to Atlassian-hosted BitBucket Cloud 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-27350) "Performance Report" on each job don't have link text and the graph picture is missing.
Title: Message Title Hitesh Patel reopened an issue Broken again with fix for JENKINS-28733 from commit 04537b112b440f29b0e87cccb7cf9bbb7edf7c6f. Jenkins / JENKINS-27350 "Performance Report" on each job don't have link text and the graph picture is missing. Change By: Hitesh Patel Resolution: Fixed Status: Resolved Reopened Assignee: Manuel Carrasco Hitesh Patel Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36488) Fix Favorite URL path
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36488 Fix Favorite URL path Issue Type: Bug Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jul/07 5:25 AM Priority: Major Reporter: Vivek Pandey Favorited pipeline path is not generated correctly to account for nested folders. It should also follow the URL path generated by Link object. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36487) Update comments to Atlassian-hosted BitBucket Cloud
Title: Message Title Balaji Renganathan created an issue Jenkins / JENKINS-36487 Update comments to Atlassian-hosted BitBucket Cloud Issue Type: Task Assignee: peterkittreilly Components: violations-plugin Created: 2016/Jul/07 4:58 AM Environment: Jenkins 2.11, Windows 10 OS Labels: plugin jenkins plugins Priority: Major Reporter: Balaji Renganathan We need to update the code violations in Atlassian-hosted BitBucket Cloud. We have tried the below plugin, https://wiki.jenkins-ci.org/display/JENKINS/Violation+Comments+to+Bitbucket+Server+Plugin But we couldn't update the code violation comments to the Atalssian-hosted BiBucket cloud. Whether the above plugin is only for BitBucket Server (Stash) ? Could anyone please let us know how to update the static code violation comments in "Atlassian-hosted BitBucket Cloud" as same like "Build Status Notifier Plugin" (https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Cloud+Build+Status+Notifier+Plugin) ?
[JIRA] (JENKINS-36462) while pipeline list is loading it says "no pipelines"
Title: Message Title Michael Neale commented on JENKINS-36462 Re: while pipeline list is loading it says "no pipelines" This isn't an "empty state" so much as a "loading" interstitial? 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-9896) Trend report only displays the last build
Title: Message Title Hitesh Patel resolved as Not A Defect This doesn't appear to be a defect. Performance plugin is working as expected. Workaround is described in the previous comment if results are coming from Jenkins Jmeter plugin. Additionally, user can rename the file as a build step if necessary to meet performance plugin requirements. Reopen issue if necessary. Jenkins / JENKINS-9896 Trend report only displays the last build Change By: Hitesh Patel Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-9522) [Performance] - Display graph
Title: Message Title Hitesh Patel resolved as Fixed Cannot reproduce this issue anymore. Tested with latest Jenkins and latest performance plugin. Used a 60MB Jmeter test results file (jtl) and repeatedly (10+) ran Jenkins job that parses the 60MB file. This issue is fixed by other fixes as mentioned by Guus der Kinderen. Reopen if needed. Jenkins / JENKINS-9522 [Performance] - Display graph Change By: Hitesh Patel Status: Open Resolved Assignee: Manuel Carrasco Hitesh Patel Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36486) httpRequest executes from Jenkins Master node
Title: Message Title John Zila updated an issue Jenkins / JENKINS-36486 httpRequest executes from Jenkins Master node Change By: John Zila Summary: httpRequest executes from Jenkins Master node if URL 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title Mark Waite commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches I've created the branch JENKINS-34309 on my jenkins-bugs github repository. That branch includes an "ant" script (build.xml) which by default updates a file (build.number) and commits the update with a Ctrl+M embedded in the commit message. I have a freestyle job polling that repository and that branch and don't see the failure. I see an earlier reference to a pipeline job. Was your case using a pipeline job as well? If not, what job type were you using? 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-36075) Gitlab oauth does not display in Security Realm
Title: Message Title summer nguyen commented on JENKINS-36075 Re: Gitlab oauth does not display in Security Realm Sounds great . Waiting for the release 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-36486) httpRequest executes from Jenkins Master node if URL is fixed
Title: Message Title
John Zila created an issue
Jenkins / JENKINS-36486
httpRequest executes from Jenkins Master node if URL is fixed
Issue Type:
Bug
Assignee:
Janario Oliveira
Components:
http-request-plugin
Created:
2016/Jul/07 2:17 AM
Environment:
Jenkins 2.10, HTTP Request Plugin 1.8.11
Priority:
Minor
Reporter:
John Zila
We use the EC2 Metadata API to retrieve the local host IP. Creating a new URL() object and getting the text from the result showed that it was running on the queueing machine. Fair enough, understandable for the groovy script to initially get executed on that one first. However, I then installed the httpRequest plugin, hoping that it would solve that problem. Nope.
sh "curl -s http://169.254.169.254/latest/meta-data/public-ipv4 > public.txt"
sh "curl -s http://169.254.169.254/latest/meta-data/local-ipv4 > private.txt"
def nodePublicIP = readFile('public.txt')
def nodePrivateIP = readFile('private.txt')
sh "rm public.txt"
sh "rm private.txt"
def httpRequestPublicIP = httpRequest("http://169.254.169.254/latest/meta-data/public-ipv4").content
def httpRequestPrivateIP = httpRequest("http://169.254.169.254/latest/meta-data/local-ipv4").content
println "Running on host $nodePublicIP ($nodePrivateIP)"
println "httpRequest says host $httpRequestPublicIP ($httpRequestPrivateIP)"
Output:
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Title: Message Title apgray reopened an issue Jenkins / JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: apgray Resolution: Not A Defect Status: Closed 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 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-15751) Cannot escape dollar sign in Windows environment
Title: Message Title apgray commented on JENKINS-15751 Re: Cannot escape dollar sign in Windows environment See my comment on JENKINS-13157. It appears if it is a TRAILING $ then two $ characters doesn't work on Windows 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray commented on JENKINS-13157
Re: EnvInject cannot inject variables whose contents contain a dollar sign ($)
Jenkins Core: 2.12 EnvInject: 1.92.1 I tried the following evaluated groovy script:
switch (ENV) {
case 'DEV':
def map = [WEB_SERVER: '.', DB_SERVER: '', DRIVE_LETTER: 'D$$']
return map
break
case 'TEST':
def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: 'D$$']
return map
break
default:
def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: '']
return map
break
}
which still didn't work when ENV = 'DEV' or 'TEST'.
[EnvInject] - Injecting contributions.
Building in workspace ...
[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
If I downgrade to Jenkins Core 2.11 and run the same code I get the same result. If I remove the trailing $ from DRIVE_LETTER it works. So that confirms to me that it doesn't like the trailing $ character. Can anyone assist with how to escape this $ in this context?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
[JIRA] (JENKINS-34140) Allow to specify node for load from SCM (Jenkinsfile)
Title: Message Title Eli White commented on JENKINS-34140 Re: Allow to specify node for load from SCM (Jenkinsfile) This seems similar to https://issues.jenkins-ci.org/browse/JENKINS-35710 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title David Baumgold assigned an issue to Unassigned Jenkins / JENKINS-13157 EnvInject cannot inject variables whose contents contain a dollar sign ($) Change By: David Baumgold Assignee: David Baumgold 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray updated an issue
Jenkins / JENKINS-13157
EnvInject cannot inject variables whose contents contain a dollar sign ($)
Change By:
apgray
Comment:
I tried the following evaluated groovy script with v1.92.1 of the plugin:{code:java}switch (ENV) {case 'DEV': def map = [WEB_SERVER: '.', DB_SERVER: '', DRIVE_LETTER: 'D$$'] return map break case 'TEST': def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: 'D$$'] return map breakdefault: def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: ''] return map break}{code}which still didn't work when ENV = 'DEV' or 'TEST'.{code:java}[EnvInject] - Injecting contributions.Building in workspace ...[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.{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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray commented on JENKINS-13157
Re: EnvInject cannot inject variables whose contents contain a dollar sign ($)
I tried the following evaluated groovy script with v1.92.1 of the plugin:
switch (ENV) {
case 'DEV':
def map = [WEB_SERVER: '.', DB_SERVER: '', DRIVE_LETTER: 'D$$']
return map
break
case 'TEST':
def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: 'D$$']
return map
break
default:
def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: '']
return map
break
}
which still didn't work when ENV = 'DEV' or 'TEST'.
[EnvInject] - Injecting contributions.
Building in workspace ...
[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Alastair D'Silva commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Note that the Multibranch project plugin is also affected by this (and I can't see any way to customise the workspace path). I do think that Jesse's idea of fixing it in the core is worthwhile though, as there are other avenues that troublesome characters can get into the paths (eg. Matrix axes). 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Alastair D'Silva edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Note that the [Multibranch project plugin|https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin] is also affected by this (and I can't see any way to customise the workspace path).I do think that Jesse's idea of fixing it in the core is worthwhile though the best way forward , as there are other avenues that troublesome characters can get into the paths (eg. Matrix axes). 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title apgray edited a comment on JENKINS-13157 Re: EnvInject cannot inject variables whose contents contain a dollar sign ($) I am using EnvInject version 1.92.1 and also have the same issue. I am trying to set a variable called DRIVE_LETTER="D$" How can we properly escape the a trailing $ character? 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray updated an issue
Jenkins / JENKINS-13157
EnvInject cannot inject variables whose contents contain a dollar sign ($)
Change By:
apgray
Comment:
I tried the following evaluated groovy script with v1.92.1 of the plugin:{code:java}switch (ENV) {case 'DEV': def map = [WEB_SERVER: '.', DB_SERVER: '', DRIVE_LETTER: 'D$$'] return map break case 'TEST': def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: 'D$$'] return map breakdefault: def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: ''] return map break}{code}which still didn't work.[EnvInject] - Injecting contributions.Building in workspace ...[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Alastair D'Silva commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Proposed fix here: https://github.com/jenkinsci/branch-api-plugin/pull/46 It adds a couple of different user-selectable encoding options in addition to the the default one. 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-36439) Evolve more composable redux store code patterns
Title: Message Title Michael Neale commented on JENKINS-36439 Re: Evolve more composable redux store code patterns I think this is only a blocker in the sense that it is "very important" for immediate things that are desperately needed like paging, it isn't blocking most other features that are currently being worked on. 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray updated an issue
Jenkins / JENKINS-13157
EnvInject cannot inject variables whose contents contain a dollar sign ($)
Change By:
apgray
Comment:
I tried the following evaluated groovy script with v1.92.1 of the plugin:{code:java}switch (ENV) {case 'DEV': def map = [WEB_SERVER: '.', DB_SERVER: '', DRIVE_LETTER: 'D$$'] return map break case 'TEST': def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: 'D$$'] return map breakdefault: def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: ''] return map break}{code}which still didn't work.[EnvInject] - Injecting contributions.Building in workspace ...[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray commented on JENKINS-13157
Re: EnvInject cannot inject variables whose contents contain a dollar sign ($)
I tried the following evaluated groovy script with v1.92.1 of the plugin:
switch (ENV) {
case 'DEV':
def map = [WEB_SERVER: '.', DB_SERVER: '', DRIVE_LETTER: 'D$$']
return map
break
case 'TEST':
def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: 'D$$']
return map
break
default:
def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: '']
return map
break
}
which still didn't work. [EnvInject] - Injecting contributions. Building in workspace ... [EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray edited a comment on JENKINS-13157
Re: EnvInject cannot inject variables whose contents contain a dollar sign ($)
I tried the following evaluated groovy script with v1.92.1 of the plugin:{code:java}switch (ENV) {case 'DEV': def map = [WEB_SERVER: ' wsdb4121 . srv.test.dir.telstra.com ', DB_SERVER: ' wsdb4121.srv.test.dir.telstra.com ', DRIVE_LETTER: 'D$$'] return map break case 'TEST': def map = [WEB_SERVER: ' wsdb4120.srv.test.dir.telstra.com ', DB_SERVER: ' wsdb4120.srv.test.dir.telstra.com ', DRIVE_LETTER: 'D$$'] return map breakdefault: def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: ''] return map break}{code}which still didn't work.[EnvInject] - Injecting contributions.Building in workspace ...[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray edited a comment on JENKINS-13157
Re: EnvInject cannot inject variables whose contents contain a dollar sign ($)
I tried the following evaluated groovy script with v1.92.1 of the plugin: ` {code:java} switch (ENV) {case 'DEV': def map = [WEB_SERVER: 'wsdb4121.srv.test.dir.telstra.com', DB_SERVER: 'wsdb4121.srv.test.dir.telstra.com', DRIVE_LETTER: 'D$$'] return map break case 'TEST': def map = [WEB_SERVER: 'wsdb4120.srv.test.dir.telstra.com', DB_SERVER: 'wsdb4120.srv.test.dir.telstra.com', DRIVE_LETTER: 'D$$'] return map break ` default: def map = [WEB_SERVER: '', DB_SERVER: '', DRIVE_LETTER: ''] return map break}{code}which still didn't work.[EnvInject] - Injecting contributions.Building in workspace ...[EnvInject] - Unset unresolved 'DRIVE_LETTER' variable.
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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title
apgray commented on JENKINS-13157
Re: EnvInject cannot inject variables whose contents contain a dollar sign ($)
I tried the following evaluated groovy script with v1.92.1 of the plugin: `switch (ENV) { case 'DEV': def map = [WEB_SERVER: 'wsdb4121.srv.test.dir.telstra.com', DB_SERVER: 'wsdb4121.srv.test.dir.telstra.com', DRIVE_LETTER: 'D$$'] return map break case 'TEST': def map = [WEB_SERVER: 'wsdb4120.srv.test.dir.telstra.com', DB_SERVER: 'wsdb4120.srv.test.dir.telstra.com', DRIVE_LETTER: 'D$$'] return map break`
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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Title: Message Title apgray commented on JENKINS-13157 Re: EnvInject cannot inject variables whose contents contain a dollar sign ($) I am using EnvInject version 1.92.1 and also have the same issue. I am trying to set a variable called DRIVE_LETTER="D$" How can we properly escape the $ character? 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-30744) multibranch issues if branch contains /
Title: Message Title Jesse Glick resolved as Fixed Please refer to JENKINS-34564 for the request for alternate workspace naming. Jenkins / JENKINS-30744 multibranch issues if branch contains / Change By: Jesse Glick 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
[JIRA] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Harry Soehalim commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin um, do we have any update on this issue? thx 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-35284) Migrate external-monitor-job-plugin to 2.x parent pom
Title: Message Title Manuel Recena Soto closed an issue as Done Jenkins / JENKINS-35284 Migrate external-monitor-job-plugin to 2.x parent pom Change By: Manuel Recena Soto Status: In Progress 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill New PR (https://github.com/jenkinsci/lockable-resources-plugin/pull/35) probably supersedes #34 - updating LockRunListener to listen on Run rather than AbstractBuild seems to, well, fix everything! 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-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title J F commented on JENKINS-34722 Re: Unbounded searches with BuildUtil.getDownstreamBuild There are ~280 builds, and 50 pipelines, with varying numbers of build jobs each. (Answering on behalf of Dilip) 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-34725) Multibranch Plugin: Shouldn't run every branch on re-index
Title: Message Title Jesse Glick commented on JENKINS-34725 Re: Multibranch Plugin: Shouldn't run every branch on re-index You can already disable the trigger. JENKINS-34005 proposes adding a Jenkinsfile-based control which would let you conditionally reinstate it for noninitial builds. 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-36485) Create/Update of job via API does not keep entity encoding
Title: Message Title Frank Yehat commented on JENKINS-36485 Re: Create/Update of job via API does not keep entity encoding It works as expected (i.e., always encoded) in an older Jenkins installation (1.6xx) 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-36485) Create/Update of job via API does not keep entity encoding
Title: Message Title Frank Yehat created an issue Jenkins / JENKINS-36485 Create/Update of job via API does not keep entity encoding Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/06 9:53 PM Labels: REST API encoding upload Priority: Minor Reporter: Frank Yehat In Jenkins 2.11, after uploading a Job, the entities at least in textareas are no longer encoded Steps to verify: 1) Create a job with e.g. shell code in a build step and some encoded characters (e.g. quotation marks: ") 2) Download the job config via the REST-API -> quotes are encoded as """ 3) re-upload/Replace the same job/data again 4) Download the configuration again & compare with result of step 2) -> quotes are not encoded Optional step: 5) Save the job again via the GUI by clicking SAVE 6) Download the cofiguration via the API again and compare with result of step 2) -> Both download are identical, i.e. the quotes are encoded again With an account on the server and wireshark we could verify that the configuration is sent/uploaded correctly (=encoded) to the server in step 3), but stored unencoded on the serversin the local XML. This is corrected after savig again in step 5)
[JIRA] (JENKINS-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill I can't see a way to clear the lock without either waiting for a new lock request to come in (as my PR does) or having an async recurring task running periodically checking every locked resource for defunct locks. LockRunListener doesn't seem to fire on hard kill or while-running build deletion, so far as I can tell from my experiments... 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-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Luis Silva edited a comment on JENKINS-36468 Re: Tasks fail to run on ECS after upgrade to 1.4 Hi Jan,I'm using +only+ m3.medium instances with 3.7GB of memory available on a ASG. I tested this with one instance only min=max=desired=1 and it was failing.Before digging into the logs I added another instance thinking it was related to resource starvation. It still didn't work, then I grabbed the above logs.There were no other jenkins jobs running when I was testing this (master, regular slave or ECS slaves), and there were no other tasks or services (running or pending) in the ECS console when I tested this.I downgraded to 1.3 it hasn't failed once. Whenever I try to upgrade to 1.4, they immediately stop working. The attached image shows my ECS console in Standby waiting for the tests to run (that either pass or fail depending on the plugin version) 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-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Luis Silva updated an issue Jenkins / JENKINS-36468 Tasks fail to run on ECS after upgrade to 1.4 Change By: Luis Silva Attachment: ECS.jpg 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-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Luis Silva commented on JENKINS-36468 Re: Tasks fail to run on ECS after upgrade to 1.4 Hi Jan, I'm using only m3.medium instances with 3.7GB of memory available on a ASG. I tested this with one instance only min=max=desired=1 and it was failing. Before digging into the logs I added another instance thinking it was related to resource starvation. It still didn't work, then I grabbed the above logs. There were no other jenkins jobs running when I was testing this (master, regular slave or ECS slaves), and there were no other tasks or services (running or pending) in the ECS console when I tested this. I downgraded to 1.3 it hasn't failed once. Whenever I try to upgrade to 1.4, they immediately stop working. 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-28183) Hard killed job's stage blocks stage in following jobs
Title: Message Title Andrew Bayer commented on JENKINS-28183 Re: Hard killed job's stage blocks stage in following jobs Once JENKINS-26107 is released, stage concurrency will be deprecated. So this won't actually get fixed - instead, the recommendation will be to use lockable-resources, which is getting a fix for at least some of this scenario over at JENKINS-36479. 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-36075) Gitlab oauth does not display in Security Realm
Title: Message Title Jairo Ricarte commented on JENKINS-36075 Re: Gitlab oauth does not display in Security Realm Fixed on PR: https://github.com/jenkinsci/gitlab-oauth-plugin/pull/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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill PR up - https://github.com/jenkinsci/lockable-resources-plugin/pull/34 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-36484) Remove the deprecated code inherited from CopyArtifact plugin
Title: Message Title Alexandru Somai updated an issue Jenkins / JENKINS-36484 Remove the deprecated code inherited from CopyArtifact plugin Change By: Alexandru Somai Sprint: [GSoC] Sprint 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-36484) Remove the deprecated code inherited from CopyArtifact plugin
Title: Message Title Alexandru Somai started work on JENKINS-36484 Change By: Alexandru Somai 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-36484) Remove the deprecated code inherited from CopyArtifact plugin
Title: Message Title Alexandru Somai created an issue Jenkins / JENKINS-36484 Remove the deprecated code inherited from CopyArtifact plugin Issue Type: Task Assignee: Alexandru Somai Components: run-selector-plugin Created: 2016/Jul/06 8:38 PM Priority: Major Reporter: Alexandru Somai A new repository has been created for the run-selector-plugin. As it is now, it has inherited the entire code from CopyArtifact plugin 2.0 version. In this task, the deprecated code should be removed. Add Comment
[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Jan Roehrich assigned an issue to Luis Silva Jenkins / JENKINS-36468 Tasks fail to run on ECS after upgrade to 1.4 Change By: Jan Roehrich Assignee: Jan Roehrich Luis Silva 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-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Jan Roehrich commented on JENKINS-36468 Re: Tasks fail to run on ECS after upgrade to 1.4 Hi Luis Silva, it seems to me like you have more than one EC2 instance in your ECS cluster. And I assume they have a very different memory sizing. Have a look at the first couple of rows of the log you attached: You're requesting 3GB of memory for your slave. See your ECS slave template definition. And I assume that AWS tries to run the task on a machine with less than this amount of memory. 1.4 has autoscaling improvements. It checks the cluster for instances with the required amount of reserved memory and cpu units available. In you case the plugins finds an instance with sufficient resources but AWS tries to run the task on a different instance win unsufficient resources. I think this causes the failure. Can you please check if I'm right? And if so, is it possible to run your cluster with homogeneous cluster instances?` Regards, Jan 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-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Jan Roehrich edited a comment on JENKINS-36468 Re: Tasks fail to run on ECS after upgrade to 1.4 Hi [~luissilva],it seems to me like you have more than one EC2 instance in your ECS cluster. And I assume they have a very different memory sizing. Have a look at the first couple of rows of the log you attached: You're requesting 3GB of memory for your slave. See your ECS slave template definition. And I assume that AWS tries to run the task on a machine with less than this amount of memory.1.4 has autoscaling improvements. It checks the cluster for instances with the required amount of reserved memory and cpu units available. In you your case the plugins finds an instance with sufficient resources but AWS tries to run the task on a different instance win unsufficient resources. I think this causes the failure. Can you please check if I'm right? And if so, is it possible to run your cluster with homogeneous cluster instances?`Regards, Jan 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-34021) NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Title: Message Title Jesse Glick resolved as Fixed Symptom fixed. Root cause unknown. Jenkins / JENKINS-34021 NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140) Change By: Jesse Glick Status: In Progress 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,
[JIRA] (JENKINS-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36479 Locked resources not freed up by Pipeline job hard kill Change By: Jesse Glick Labels: robustness workflow 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-28183) Hard killed job's stage blocks stage in following jobs
Title: Message Title Jesse Glick commented on JENKINS-28183 Re: Hard killed job's stage blocks stage in following jobs The NullPointerException has since been fixed IIRC. Unlikely to be fixed since concurrency of stage is slated for deprecation. Use lock instead, and we will work on JENKINS-36479. 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-36217) Must update IAM roles in the documetnation
Title: Message Title Jan Roehrich closed an issue as Fixed Jenkins / JENKINS-36217 Must update IAM roles in the documetnation Change By: Jan Roehrich Status: Resolved Closed 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-36217) Must update IAM roles in the documetnation
Title: Message Title Jan Roehrich resolved as Fixed Adapted documentation to match current policy requirements Jenkins / JENKINS-36217 Must update IAM roles in the documetnation Change By: Jan Roehrich 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
[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error
Title: Message Title Christopher Eck created an issue Jenkins / JENKINS-36483 Unable to login with google-login plugin with 401 error Issue Type: Bug Assignee: recampbell Components: google-login-plugin Created: 2016/Jul/06 7:59 PM Environment: Jenkins 2.11 running in docker, google-login-plugin 1.2.1 Labels: login Priority: Blocker Reporter: Christopher Eck Attempting to use the plugin with no domain or specifying a domain, I see the following stack trace. com.google.api.client.auth.oauth2.TokenResponseException: 401 Unauthorized at com.google.api.client.auth.oauth2.TokenResponseException.from(TokenResponseException.java:105) at com.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:287) at com.google.api.client.auth.openidconnect.IdTokenResponse.execute(IdTokenResponse.java:120) at org.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm$2.onSuccess(GoogleOAuth2SecurityRealm.java:173) at org.jenkinsci.plugins.googlelogin.OAuthSession.doFinishLogin(OAuthSession.java:99) at org.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm.doFinishLogin(GoogleOAuth2SecurityRealm.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at
[JIRA] (JENKINS-36371) NullPointerException in WebappClassLoader.findResources
Title: Message Title Andres Garcia assigned an issue to Paul Weber Jenkins / JENKINS-36371 NullPointerException in WebappClassLoader.findResources Change By: Andres Garcia Assignee: Paul Weber 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-36371) NullPointerException in WebappClassLoader.findResources
Title: Message Title Andres Garcia assigned an issue to Unassigned Jenkins / JENKINS-36371 NullPointerException in WebappClassLoader.findResources Change By: Andres Garcia Assignee: diana cubillos 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-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Sebastien Vas commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails I am experiencing the same behavior. It is kind of frustrating to have to manually delete slaves. Restarting Jenkins does not resolve the issue. I am worried that the suspended slaves are still accounted for, or at least creating a slow memory leak. 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill Ok, that's just noise - not ideal noise, but just noise. I've pushed a commit with a test that passes now and hangs forever without my changes to LockableResourceManager - that needs to be fixed to actually fail in that scenario. More tests still needed for the doDelete scenario and for the builds-already-in-queue scenario, but I just wanted to make sure this actually worked in the base case. =) 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill Interesting - turns out LockStepExecution.stop still gets called in the case of a hard kill, and it's not pleased about it - INFO: p #1 completed: ABORTED [p #1] Hard kill! Jul 06, 2016 11:27:29 AM org.jenkins.plugins.lockableresources.LockStepExecution stop WARNING: Cannot remove context from lockable resource witing list. The context is not in the waiting list. Jul 06, 2016 11:27:29 AM org.jenkinsci.plugins.workflow.cps.CpsStepContext onFailure WARNING: already completed CpsStepContext[3]:Owner[p/1:p #1] java.lang.IllegalStateException: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:320) at org.jenkins.plugins.lockableresources.LockStepExecution.stop(LockStepExecution.java:90) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:760) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:755) at org.jenkinsci.plugins.workflow.support.concurrent.Futures$1.run(Futures.java:150) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134) at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170) at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:644) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:631) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:568) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744)
[JIRA] (JENKINS-36482) PagerDuty incidentkey doesn't work with variables.
Title: Message Title Bharat Bhatia updated an issue Jenkins / JENKINS-36482 PagerDuty incidentkey doesn't work with variables. Change By: Bharat Bhatia PagerDuty incidentkey doesn't work with variables. It can create trigger event but doesn't resolve the issue. For e.g. If $Var = abc Incident_$Var will create plugin trigger event will create incident with key "Incident_abc" but plugin resolve event doesn't resolve it. 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-36482) PagerDuty incidentkey doesn't work with variables.
Title: Message Title Bharat Bhatia updated an issue Jenkins / JENKINS-36482 PagerDuty incidentkey doesn't work with variables. Change By: Bharat Bhatia Summary: PagerDuty incidentkey doesn't work with variables. It can create trigger event but doesn't resolve 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-36482) PagerDuty incidentkey doesn't work with variables. It can create trigger event but doesn't resolve the issue.
Title: Message Title Bharat Bhatia created an issue Jenkins / JENKINS-36482 PagerDuty incidentkey doesn't work with variables. It can create trigger event but doesn't resolve the issue. Issue Type: Bug Assignee: Alexander Leibzon Components: pagerduty-plugin Created: 2016/Jul/06 6:27 PM Environment: Jenkins 2.12 PagerDuty Plugin 0.2.4 Priority: Minor Reporter: Bharat Bhatia Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36076) Write acceptance tests for external workspace manager
Title: Message Title Alexandru Somai updated an issue Jenkins / JENKINS-36076 Write acceptance tests for external workspace manager Change By: Alexandru Somai Write Acceptance Test Harness for the External Workspace Manager plugin. Mostly the tests are UI based: # Test the Jenkins global config sections, External Workspace Definitions and External Workspace Templates. - e.g. fill in the text boxes, save, and verify if the information was saved correctly# Test the Node configuration, External Workspace property - select the checkbox and fill in the text boxes, after saving, the information should be persisted# Set-up a minimal config, with one node instance and create a basic pipeline job that runs the _exwsAllocate_ and _exws_ steps. Verify the console output for the logged messages. Verify if the _External Workspaces_ run action outputs the appropriate information, e.g. selected disk pool, selected disk, complete path on disk.# Set-up a bit more complex environment, with two node instances. Maybe if I'll point the _localRootPath_ parameter to the same path on both of the nodes, I may be able to test a bit more complex scenario, in which I will build the project on one node, and test the project on a different node. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36076) Write acceptance tests for external workspace manager
Title: Message Title Alexandru Somai updated an issue Jenkins / JENKINS-36076 Write acceptance tests for external workspace manager Change By: Alexandru Somai Write Acceptance Test Harness for the External Workspace Manager plugin. Mostly the tests are UI based:# Test the Jenkins global config sections, External Workspace Definitions and External Workspace Templates. - e.g. fill in the text boxes, save, and verify if the information was saved correctly# Test the Node configuration, External Workspace property - select the checkbox and fill in the text boxes, after saving, the information should be persisted# Set-up a minimal config, with one node instance and create a basic pipeline job that runs the _exwsAllocate_ and _exws_ steps. Verify the console output for the logged messages. Verify if the _External Workspaces_ run action outputs the appropriate information, e.g. selected disk pool, selected disk, complete path on disk.# Set-up a bit more complex environment, with two node instances. Maybe if I'll point the localRootPath _localRootPath_ parameter to the same path on both of the nodes, I may be able to test a bit more complex scenario, in which I will build the project on one node, and test the project on a different node. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36076) Write acceptance tests for external workspace manager
Title: Message Title Alexandru Somai updated an issue Jenkins / JENKINS-36076 Write acceptance tests for external workspace manager Change By: Alexandru Somai Write Acceptance Test Harness for the External Workspace Manager plugin. Mostly the tests are UI based:# Test the Jenkins global config sections, External Workspace Definitions and External Workspace Templates. - e.g. fill in the text boxes, save, and verify if the information was saved correctly# Test the Node configuration, External Workspace property - select the checkbox and fill in the text boxes, after saving, the information should be persisted# Set-up a minimal config, with one node instance and create a basic pipeline job that runs the _exwsAllocate_ and _exws_ steps. Verify the console output for the logged messages. Verify if the _External Workspaces_ run action outputs the appropriate information, e.g. selected disk pool, selected disk, complete path on disk. # Set-up a bit more complex environment, with two node instances. Maybe if I'll point the localRootPath parameter to the same path on both of the nodes, I may be able to test a bit more complex scenario, in which I will build the project on one node, and test the project on a different node. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36076) Write acceptance tests for external workspace manager
Title: Message Title Alexandru Somai commented on JENKINS-36076 Re: Write acceptance tests for external workspace manager I've written some basic test scenarios that I could think of. They are mainly UI based. It may be a bit more difficult to test some real-world case scenarios, because the plugin needs a basic set-up, with multiple nodes and mounting points to disks. Unless I don't have a pre-made environment set-up with docker, I don't think I can write more complex test cases. 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-36076) Write acceptance tests for external workspace manager
Title: Message Title Alexandru Somai updated an issue Jenkins / JENKINS-36076 Write acceptance tests for external workspace manager Change By: Alexandru Somai Write Acceptance Test Harness for the External Workspace Manager plugin. Mostly the tests are UI based:# Test the Jenkins global config sections, External Workspace Definitions and External Workspace Templates. - e.g. fill in the text boxes, save, and verify if the information was saved correctly# Test the Node configuration, External Workspace property - select the checkbox and fill in the text boxes, after saving, the information should be persisted# Set-up a minimal config, with one node instance and create a basic pipeline job that runs the _exwsAllocate_ and _exws_ steps. Verify the console output for the logged messages. Verify if the _External Workspaces_ run action outputs the appropriate information, e.g. selected disk pool, selected disk, complete path on disk. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill Note that this approach doesn't do anything for a scenario where there are already builds queued up for a resource and the build holding that lock gets deleted/hard killed - it only clears that defunct lock when something requests a lock on the resource, though in the X-builds-queued-up scenario, when the X+1th build tries to get a lock, the result will be that the first build in the queue ends up getting a new lock. Still thinking about how to deal with the existing queue without a new lock request... 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-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Title: Message Title Boguslaw Klimas resolved as Fixed Fixed in releas 0.6.0 Jenkins / JENKINS-16290 git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves Change By: Boguslaw Klimas Status: In Progress 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
[JIRA] (JENKINS-36481) Remove clutter from BlueOceanUI
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36481 Remove clutter from BlueOceanUI Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jul/06 5:17 PM Priority: Major Reporter: Vivek Pandey BlueOceanUI is bootstrap class, its not best place to add API methods. There are two of them getPluginVersion() and includeRollbar() that should be reviewed and moved to appropriate place. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Yury Zaytsev thanks for detecting that, and thanks for reporting it. Git plugin 3.0.0-beta1 was released a month ago (changelog). Git plugin 2.5.1 (followed by 2.5.2) was released a few days ago (changelog) with the advanced git behaviors in multibranch pipeline projects (and in literate projects). A new release of git plugin 3.0.0-beta will be needed before the advanced git behaviors will be visible in multibranch pipeline projects with a plugin version that supports submodule authentication. I hope to release that new version of git plugin 3.0.0-beta within the next 12 hours. 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill Continued further with https://github.com/jenkinsci/lockable-resources-plugin/compare/master...abayer:jenkins-36479 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer started work on JENKINS-36479 Change By: Andrew Bayer 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill Very first thoughts on this up at https://github.com/abayer/lockable-resources-plugin/commit/9a0ef2cae5176cef4d5f8439c53b2aad4b6facc0 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-36301) Migrate suppress-stack-trace-plugin to 2.x parent pom
Title: Message Title Manuel Recena Soto closed an issue as Done Jenkins / JENKINS-36301 Migrate suppress-stack-trace-plugin to 2.x parent pom Change By: Manuel Recena Soto Status: In Progress 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-36422) Unable to remove workspace
Title: Message Title Tristan Lewis commented on JENKINS-36422 Re: Unable to remove workspace I'm also getting this, with the same stack trace. It happen even if I disable the "Delete Perforce client" and "Delete workspace files" options under the global P4 settings on Jenkins. I have a system of seed jobs set up which consume perforce-tracked groovy files that define my job via the Job DSL Plugin, and due to this issue my seed jobs are no longer able to succeed if I make a change that results in any job names changing (since this triggers a deletion of the old job name). 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-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title S Raigner edited a comment on JENKINS-36361 Re: javax.servlet.ServletException in pluginmanager Similar problem here. Jenkins wer. 1594. ubuntu 12.04, we had not updated the svn plugin nor did we update Jenkins . Little different method here. I uninstalled the subversion plugin and the problem went away.Initially, I thought that this was the end of my problems, but, discovered that my xvfb plugin was rendered useless. I had to uninstall it and reinstall. I have not reinstalled the svn 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-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title S Raigner edited a comment on JENKINS-36361 Re: javax.servlet.ServletException in pluginmanager Similar problem here. Jenkins wer. 1594. ubuntu 12.04 , we had not updated the svn plugin. Little different method here. I uninstalled the subversion plugin and the problem went away. Initially, I thought that this was the end of my problems, but, discovered that my xvfb plugin was rendered useless. I had to uninstall it and reinstall. I have not reinstalled the svn 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-36480) Recreating projects using jenkins-cli generates "cannot create a build with number" error
Title: Message Title Lee Winder created an issue Jenkins / JENKINS-36480 Recreating projects using jenkins-cli generates "cannot create a build with number" error Issue Type: Bug Assignee: Unassigned Components: cli Created: 2016/Jul/06 4:17 PM Environment: Jenkins v2.0 Priority: Major Reporter: Lee Winder I am using the Jenkins CLI jar to recreate projects based on a tempate project. The process is as follows Calls 'get-job' to check if the job exists If job exists calls 'delete-job' to remove the project Calls 'create-job' to create the project (using the same job name as the one deleted) 'create-job' simply uses the XML job description from the template job with various properties altered (job name, env variables etc.). The issue seems to occur if the job already exists and has been run multiple times before being deleted and recreated. So, if the job is initially created and runs 32 times before being deleted and recreated, the next time this (new) job is run, it generates this error java.lang.IllegalStateException: cannot create a build with number 1 since that (or higher) is already in use among [32] at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:373) at hudson.model.RunMap.put(RunMap.java:191) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1018) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1209) at
[JIRA] (JENKINS-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer commented on JENKINS-36479 Re: Locked resources not freed up by Pipeline job hard kill Also this can happen if the build is deleted while running - a non-ideal usage pattern, sure, but since you can do it, people will end up doing it. So we probably also want to check if the build locking a resource actually even exists in the first place and unlock if the build doesn't exist. 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-36479) Locked resources not freed up by Pipeline job hard kill
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-36479 Locked resources not freed up by Pipeline job hard kill Issue Type: Bug Assignee: Andrew Bayer Components: lockable-resources-plugin Created: 2016/Jul/06 4:06 PM Priority: Major Reporter: Andrew Bayer Since LockStepExecution.Callback.finished(context) never gets called in the case of a hard kill, resources can be locked forever when a build is hard killed. It's possible to manually unlock those resources from the UI, but it'd be preferable to have some behavior that detects this scenario and is able to unlock resources locked by defunct builds. Add Comment
[JIRA] (JENKINS-36478) Artifactory plugin gradle integration problem with groovy versions
Title: Message Title Manuel Franco created an issue Jenkins / JENKINS-36478 Artifactory plugin gradle integration problem with groovy versions Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2016/Jul/06 3:51 PM Environment: JENKINS 1.651.2 Artifactory plugin 2.5.1 Labels: jenkins plugin regression Priority: Minor Reporter: Manuel Franco As result of fixing a test in the ATH (see https://github.com/jenkinsci/acceptance-test-harness/pull/150) we noticed that the problem we were trying to solve is probably caused because the artifactory plugin has been built with a groovy version 2.3+, and that makes it not possible to use the integration with gradle 1.X due to groovy runtime incompatibility (see http://www.groovy-lang.org/mailing-lists.html#nabble-td5720557). Please see the mentioned PR for more info.
[JIRA] (JENKINS-35510) Migrate git-server-plugin to parent pom
Title: Message Title Manuel Recena Soto closed an issue as Done Jenkins / JENKINS-35510 Migrate git-server-plugin to parent pom Change By: Manuel Recena Soto Status: In Progress 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-36378) Jenkins Server caught Blue Dump Screen and crashed
Title: Message Title Amit Kumar commented on JENKINS-36378 Re: Jenkins Server caught Blue Dump Screen and crashed Thanks for the update. Will wait for the reply. 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-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title Kimball Robinson updated an issue Jenkins / JENKINS-36361 javax.servlet.ServletException in pluginmanager Change By: Kimball Robinson Priority: Minor Major 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-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title Kimball Robinson commented on JENKINS-36361 Re: javax.servlet.ServletException in pluginmanager Initially I updated svn but had a conflict with too new of a version, which somehow resulted in the plugin being removed and losing the svn part of some of my job configurations. It was resolved without too much fuss, but now I am living with the errors on the plugins page again. Sadly, I don't have a workaround right now that works for me. I'm glad it's helped others though. Jenkins should not allow these errors to mess up the entire plugins page. Also, it's unclear why this started being an issue now, when I haven't updated svn at all lately. 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-35922) Jenkins cannot start because of java.lang.ClassNotFoundException: hudson.plugins.disk_usage.DiskUsagePlugin
Title: Message Title Loïc Decloedt commented on JENKINS-35922 Re: Jenkins cannot start because of java.lang.ClassNotFoundException: hudson.plugins.disk_usage.DiskUsagePlugin Hi Daniel, Ok, I did not try to reproduce the problem on my side, for obvious reasons . Thanks for your investigation, anyway. Loïc. 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-36378) Jenkins Server caught Blue Dump Screen and crashed
Title: Message Title Daniel Beck commented on JENKINS-36378 Re: Jenkins Server caught Blue Dump Screen and crashed Please stop assigning this 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-36378) Jenkins Server caught Blue Dump Screen and crashed
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-36378 Jenkins Server caught Blue Dump Screen and crashed Change By: Daniel Beck Assignee: Daniel Beck 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-36378) Jenkins Server caught Blue Dump Screen and crashed
Title: Message Title Amit Kumar commented on JENKINS-36378 Re: Jenkins Server caught Blue Dump Screen and crashed Can anyone please update on the issue. If somebody can help in fixing the same. @db...@cloudbees.com 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-36378) Jenkins Server caught Blue Dump Screen and crashed
Title: Message Title Amit Kumar assigned an issue to Daniel Beck Jenkins / JENKINS-36378 Jenkins Server caught Blue Dump Screen and crashed Change By: Amit Kumar Assignee: Daniel Beck 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-36444) Checker never finds issues, because database not updated with vulnerabilities?
Title: Message Title Frank Niessink commented on JENKINS-36444 Re: Checker never finds issues, because database not updated with vulnerabilities? This the jenkins2.log, logged from the Jenkins management console. Seems pretty much the same. Hope it helps though. 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-36444) Checker never finds issues, because database not updated with vulnerabilities?
Title: Message Title Frank Niessink updated an issue Jenkins / JENKINS-36444 Checker never finds issues, because database not updated with vulnerabilities? Change By: Frank Niessink Attachment: jenkins2.log 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-20941) Stored git credentials not used when submodule is updated
Title: Message Title
Yury Zaytsev edited a comment on JENKINS-20941
Re: Stored git credentials not used when submodule is updated
FYI, very sadly, the ability to select advanced git behaviors in multibranch pipeline projects is gone again after upgrade from 2.5.2 to 3.0.0-beta1 of the git plugin. I was assuming 3.0.0-beta1 is necessary to go with 2.0.0-beta1 of the git client plugin. After I downgraded to git plugin 2.5.2 again, but left git client 2.0.0-beta1 in, submodule (public key) authentication on the agents still doesn't seem to work even though the main repository is checked out just fine :({noformat}> git submodule update --init --recursive XXXhudson.plugins.git.GitException: Command "git submodule update --init --recursive XXX" returned status code 128:stdout: stderr: Cloning into 'XXX'...Permission denied, please try again.Permission denied, please try again.Permission denied (publickey,password).fatal: Could not read from remote repository.{noformat} P.S. I was not able to find "Use credentials from default remote of parent repository" under "Additional Behaviours", maybe for that git plugin 3.0.0-beta1 is needed, but see above: if I install it, then "Additional Behaviours" vanish from the multibranch pipeline job scm settings.
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.
