[JIRA] (JENKINS-49900) Add optional "enableTopButton" option to repeatable forms
Title: Message Title Guillaume Monzerol assigned an issue to Guillaume Monzerol Jenkins / JENKINS-49900 Add optional "enableTopButton" option to repeatable forms Change By: Guillaume Monzerol Assignee: Guillaume Monzerol Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.15.1520126991000.6642.1561167060150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58042) Set verb "Build" string in button "Build with parameters" to anything else
Title: Message Title Guillaume Monzerol assigned an issue to Guillaume Monzerol Jenkins / JENKINS-58042 Set verb "Build" string in button "Build with parameters" to anything else Change By: Guillaume Monzerol Assignee: Guillaume Monzerol Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200062.1560764167000.6640.1561166940194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52646) KV v2 changes the API path to secrets & the response format
Title: Message Title Abubadabu commented on JENKINS-52646 Re: KV v2 changes the API path to secrets & the response format Ok...looks like it's already fixed...but not released. Any Peter Tierno any plan for a push to release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192501.1531974458000.6630.1561158660278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title Tilman Blumenbach updated JENKINS-55203 Jenkins / JENKINS-55203 Jenkins EC2 plugin prints private key contents in Jenkins log Change By: Tilman Blumenbach Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196273.1544798485000.6627.1561156320257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52646) KV v2 changes the API path to secrets & the response format
Title: Message Title
Abubadabu edited a comment on JENKINS-52646
Re: KV v2 changes the API path to secrets & the response format
Any hint on how to retrive the data['data']['data']['username'] for a v2 reply? KV 1.0 [https://www.vaultproject.io/api/secret/kv/kv-v1.html#read-secret] {code:java}curl --header "X-Vault-Token: xxx" https://127.0.0.1/v1/kv1/foobar{ "request_id":"...", "lease_id":"", "renewable":false, "lease_duration":2764800, "data": {"password":"xxx","username":"xxx" }, "wrap_info":null, "warnings":null, "auth":null}{code}{code:java}wrap([$class: 'VaultBuildWrapper', vaultSecrets: [[path: 'kv1/foobar', secretValues: [ [envVar: 'username', vaultKey: 'username'], [envVar: 'password', vaultKey: 'password']){ sh('echo $username') sh('echo $password')}// --> echos username / passwor{code}KV 2.0 [https://www.vaultproject.io/api/secret/kv/kv-v2.html#read-secret-version] {code:java}curl --header "X-Vault-Token: xxx" https://127.0.0.1/v1/kv2/data/foobar{ "request_id":"...", "lease_id":"", "renewable":false, "lease_duration":0, "data": {"data": { "password":"xxx", "username":"xxx"},"metadata": { "created_time":"...", "deletion_time":"", "destroyed":false, "version":1} }, "wrap_info": null, "warnings": null, "auth": null}{code}{code:java}wrap([$class: 'VaultBuildWrapper', vaultSecrets: [[path: 'kv2/data/foobar', secretValues: [ [envVar: 'username', vaultKey: 'username'], [envVar: 'password', vaultKey: 'password']){ sh('echo $username') sh('echo $password')}// --> empty echo{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-52646) KV v2 changes the API path to secrets & the response format
Title: Message Title
Abubadabu commented on JENKINS-52646
Re: KV v2 changes the API path to secrets & the response format
Any hint on how to retrive the data['data']['data']['username'] for a v2 reply? KV 1.0
curl --header "X-Vault-Token: xxx" https://127.0.0.1/v1/kv1/foobar
{
"request_id":"...",
"lease_id":"",
"renewable":false,
"lease_duration":2764800,
"data": {
"password":"xxx",
"username":"xxx"
},
"wrap_info":null,
"warnings":null,
"auth":null
}
wrap([$class: 'VaultBuildWrapper', vaultSecrets: [[path: 'kv1/foobar', secretValues: [
[envVar: 'username', vaultKey: 'username'],
[envVar: 'password', vaultKey: 'password']
)
{
sh('echo $username')
sh('echo $password')
}
// --> echos username / passwor
KV 2.0
curl --header "X-Vault-Token: xxx" https://127.0.0.1/v1/kv2/data/foobar
{
"request_id":"...",
"lease_id":"",
"renewable":false,
"lease_duration":0,
"data": {
"data": {
"password":"xxx",
"username":"xxx"
},
"metadata": {
"created_time":"...",
"deletion_time":"",
"destroyed":false,
"version":1
}
},
"wrap_info": null,
"warnings": null,
"auth": null
}
wrap([$class: 'VaultBuildWrapper', vaultSecrets: [[path: 'kv2/data/foobar', secretValues: [
[envVar: 'username', vaultKey: 'username'],
[envVar: 'password', vaultKey: 'password']
)
{
sh('echo $username')
sh('echo $password')
}
// --> empty echo
Add Comment
[JIRA] (JENKINS-58151) Invalid condition "unsuccessful" in post block
Title: Message Title
Eric Anderson created an issue
Jenkins / JENKINS-58151
Invalid condition "unsuccessful" in post block
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-06-21 21:49
Priority:
Major
Reporter:
Eric Anderson
In Jenkins version 2.169 the condition blocks supported in "post" do not match those in the documentation. Some of the supported ones are not documented. According to the documentation] "post can support any of of the following post-condition blocks: always, changed, fixed, regression, aborted, failure, success, unstable, unsuccessful, and cleanup. " However {{post { success { script { // stuff } } unsuccessful { script { // stuff } } cleanup { script { // stuff } } } }} results in this error: WorkflowScript: 128: Invalid condition "unsuccessful" - valid conditions are [always, changed, fixed, regression, aborted, success, unstable, failure, notBuilt, cleanup] @ line 128, column 5. unsuccessful {
Add Comment
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Doug Whitfield updated an issue Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Doug Whitfield Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6588.1561152600116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Doug Whitfield updated an issue Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Doug Whitfield Labels: P4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6586.1561152420250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Doug Whitfield updated an issue Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Doug Whitfield Labels: P4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6584.1561152420218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Doug Whitfield commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly the suggested "Similar Issues" do not seem to relevant Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6582.1561152360100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Doug Whitfield commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly label worked for me on 1.9.7, but I see this in the 1.10.0 console: (p4):stop:10 P4: Warning label is static and cannot be used with polling! (p4):cmd:... p4 counter DCIlabel p4 counter DCIlabel looks like there are some related issues. Will investigate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6580.1561151940134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration ui
Title: Message Title Sagar Khushalani commented on JENKINS-58089 Re: Can't configure report pattern in job configuration ui Can confirm on Jenkins v2.176.1 with version 2.3.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200130.1560932882000.6577.1561151040151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-57567 View's description has no setter which is needed for JCasC Change By: Tim Jacomb Released As: 2.180 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199481.1558374598000.6573.1561150020198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Tim Jacomb closed an issue as Fixed Jenkins / JENKINS-57567 View's description has no setter which is needed for JCasC Change By: Tim Jacomb Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199481.1558374598000.6571.1561149960324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58150) Regex doesn't remove underlying requests for response time graph description
Title: Message Title Alexander Podelko created an issue Jenkins / JENKINS-58150 Regex doesn't remove underlying requests for response time graph description Issue Type: Bug Assignee: Andrey Pokhilko Attachments: graph_description.jpg Components: performance-plugin Created: 2019-06-21 20:04 Environment: performance plugin 3.16 Priority: Minor Reporter: Alexander Podelko When I specify a regex to eliminate underlying HTTP requests and show only transactions and then click on performance report - response time graph, in the description I see all requests including those which where eliminated everywhere else (including the response graph itself). Add Comment
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Nick Carpenter edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Workaround that worked for me:Groovy config - for a container {code:java} //See BUG - https://issues.jenkins-ci. org /browse/JENKINS-54126 org .jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0{code}And{code:java}GitHubServerConfig server = new GitHubServerConfig("my_github_credential_API"); server.setApiUrl(githubAPIurl)server.setClientCacheSize(0) //<--See https://issues.jenkins-ci.org/browse/JENKINS-54126. Had to disable this one too to get this to stop happening{code}Once both of those are configured, delete the directory:$jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache Now that directory is not getting re-populated. Not sure why 2nd code block was required, but for what its worth, to the next person.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.6492.1561146841742%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Nick Carpenter commented on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Workaround that worked for me: Groovy config - for a container
//See BUG - https://issues.jenkins-ci.org/browse/JENKINS-54126 org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0
And
GitHubServerConfig server = new GitHubServerConfig("my_github_credential_API");
server.setApiUrl(githubAPIurl)
server.setClientCacheSize(0) //<--See https://issues.jenkins-ci.org/browse/JENKINS-54126. Had to disable this one too to get this to stop happening
Once both of those are configured, delete the directory: $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache Now that directory is not getting re-populated. Not sure why 2nd code block was required, but for what its worth, to the next person.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.6415.1561146121596%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Eric Boehm updated an issue Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Eric Boehm Summary: P4 Pluging p4-plugin 1.10.0 does not sync to label correctly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6410.1561146000203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Eric Boehm updated an issue Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Eric Boehm If you try to sync to a label, the p4plugin p4-plugin syncs to latest changelist instead.This does not happen in p4plugin 1.9.7Output from same client, different version of pluginp4-plugin 1.10.0P4 Task: syncing files at change: 230943p4 sync -q /auto/wksp/test_client/...@230943duration: 0m 26sp4-plugin 1.9.7p4 label -o REL_XXX +P4 Task: syncing files at client/label: REL_XXXp4 sync -q /auto/wksp/test_client/...@REL_XXX +00:00:39 duration: (280ms)Note that there is no p4 label -o REL_XXX output for p4-plugin 1.10.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200194.1561145922000.6412.1561146000263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58149) P4 Pluging 1.10.0 does not sync to label correctly
Title: Message Title Eric Boehm created an issue Jenkins / JENKINS-58149 P4 Pluging 1.10.0 does not sync to label correctly Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-06-21 19:38 Environment: Jenkins 2.179 p4 plugin 1.10.0 Priority: Blocker Reporter: Eric Boehm If you try to sync to a label, the p4plugin syncs to latest changelist instead. This does not happen in p4plugin 1.9.7 Output from same client, different version of plugin p4-plugin 1.10.0 P4 Task: syncing files at change: 230943 p4 sync -q /auto/wksp/test_client/...@230943 duration: 0m 26s p4-plugin 1.9.7 p4 label -o REL_XXX + P4 Task: syncing files at client/label: REL_XXX p4 sync -q /auto/wksp/test_client/...@REL_XXX + 00:00:39 duration: (280ms) Note that there is no p4 label -o REL_XXX output for p4-plugin 1.10.0 Add Comment
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title Jesse Glick commented on JENKINS-27413 Re: Handle file parameters Another plugin idea, useful for uploads too large to be reasonably handled as Base64 and environment variables: a parameter type which lets you upload a file to an S3 (or MinIO) bucket. Could either upload from the master upon form/CLI submission; or, more efficiently, provide a special UI & API endpoint to allocate a blob and then hand you a presigned URL good for upload only, valid for an hour. The parameter value would be a presigned URL good for download only, again valid only for a day or so. Similarly for Azure etc. (No need to delete the blob in a RunListener after the build completes. That would break Replay / Rebuild and, as with artifact-manager-s3, would force the master to have a more dangerous IAM permission. Anyway S3 can be configured to automatically expunge or archive old blobs.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161212.1426248363000.6406.1561144751330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58148) Jenkins pod reuse defeats cloud restrictions
Title: Message Title Chris K updated an issue Jenkins / JENKINS-58148 Jenkins pod reuse defeats cloud restrictions Change By: Chris K *Summary*Per the Kubernetes plugin documentation, one can [restrict which can execute on clouds at the folder level| [https://github.com/jenkinsci/kubernetes-plugin #restricting-what-jobs-can-use-your-configured-cloud].]Jenkins however, seems to use label selectors to find a build agent for a job (as reported by JENKINS-56546). These label selectors do not take into account whether the build agent selected is running in a restricted cloud or not.If you have a job in a folder that does not have access to a restricted cloud but specifies a label selector that matches an agent running in a restricted cloud, that job will run on the restricted cloud's agent regardless of the fact that cloud is restricted.*Use Case*Our organization has two tiers of developers: privileged and unprivileged. Unprivileged developers are not allowed to deploy to production environments.We use Jenkinsfiles to define pipelines. Our pipelines deploy to dev, test, and production environments. We want to build contributions from unprivileged developers, but ensure unmerged contributions don't go beyond dev environments. Since Jenkinsfiles can be modified on a branch, and Jenkins will build whatever is in the modified Jenkinsfile, there's nothing inherently preventing a unprivileged developer from modifying a Jenkinsfile to deploy say to production.To mitigate we have : * two different jobs , ** a privileged job which triggers off master and tags , and ** an unprivileged job which triggers off pull requests. Those * those jobs are in two different folders , ** a privileged folder and ** an unprivileged folder. We have * two clouds , ** privileged and : restricted for use only by the privileged folder ** unprivileged : open to any job . Unprivileged Cloud is restricted to only have permissions and network access to our dev environments.Both the privileged and unprivileged jobs reference the same Jenkinsfile, but the cloud restrictions prevent modifications on branches to the Jenkinsfile from reaching beyond dev.The problem is, since these jobs reference the same Jenkinsfile, they used the same label, and we realized that we had unprivileged jobs running on privileged agents. Not good.Now we We can parameterize the label so this doesn't happen by default, but since the labels are configured in the Jenkinsfile, you can't ensure the Jenkinsfile isn't modified on a branch to use a privileged agent. Not good. Is there a way to prevent jobs from running on agents in clouds they shouldn't have access to in a manner that is controlled outside of the Jenkinsfile?Currently the only solution we can think of is to have two separate Jenkins masters, one for privileged jobs and one for unprivileged, but this makes the folder restrictions for clouds seem less useful.
[JIRA] (JENKINS-58148) Jenkins pod reuse defeats cloud restrictions
Title: Message Title Chris K created an issue Jenkins / JENKINS-58148 Jenkins pod reuse defeats cloud restrictions Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-06-21 18:59 Environment: Jenkins 2.176.1 LTS running on Kubernetes managed by Amazon EKS kubernetes-plugin 1.16.1 Priority: Major Reporter: Chris K Summary Per the Kubernetes plugin documentation, one can restrict which can execute on clouds at the folder level Jenkins however, seems to use label selectors to find a build agent for a job (as reported by JENKINS-56546). These label selectors do not take into account whether the build agent selected is running in a restricted cloud or not. If you have a job in a folder that does not have access to a restricted cloud but specifies a label selector that matches an agent running in a restricted cloud, that job will run on the restricted cloud's agent regardless of the fact that cloud is restricted. Use Case Our organization has two tiers of developers: privileged and unprivileged. Unprivileged developers are not allowed to deploy to production environments. We use Jenkinsfiles to define pipelines. Our pipelines deploy to dev, test, and production environments. We want to build contributions from unprivileged developers, but ensure unmerged contributions don't go beyond dev environments. Since Jenkinsfiles can be modified on a branch, and Jenkins will build whatever is in the modified Jenkinsfile, there's nothing inherently preventing a unprivileged developer from modifying a Jenkinsfile to deploy say to production. To mitigate we have two different jobs, a privileged job which triggers off master and tags, and an unprivileged job which triggers off pull requests. Those jobs are in two different folders, a privileged folder and
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page A strange update, the problems have mysteriously disappeared in my chrome console (was getting 403 forbidden for field element lookups etc) and I can edit the settings I couldn't before! My version still is `0.32` as if it failed to downgrade but the problem has mysteriously self-resolved on my end. ¯ \ _(ツ)_/¯ If restarting Jenkins helped it should have been immediately apparent. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6281.1561143000726%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page A strange update, the problems have mysteriously disappeared in my chrome console (was getting 403 forbidden for field element lookups etc) and I can edit the settings I couldn't before! My version still is `0.32` as if it failed to downgrade but the problem has mysteriously self-resolved on my end. ¯_(ツ)_/¯ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6251.1561142940564%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue. (Previous: 0.29 worked)We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. " * No valid crumb was included in the request * " errors all around is our life now. [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround for this bug. We may be able to force CSRF disabled in Jenkins v2.176.1 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue.Thanks guys, CSRF implementations are never fun. :) Hope a fix is found soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6221.1561142400680%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue. (Previous: 0.29 worked)We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all around Is there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround for this bug. We may be able to force CSRF disabled in Jenkins v2.176.1 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue.Thanks guys, CSRF implementations are never fun. :) Hope a fix is found soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6192.1561141680983%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue. (Previous: 0.29 worked)We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround for this bug. We may be able to force CSRF disabled in Jenkins v2 .176.1 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue.Thanks guys, CSRF implementations are never fun. :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6134.1561141501138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue. (Previous: 0.29 worked)We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround for this bug. We may be able to force CSRF disabled in Jenkins v2.176.1 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue.Thanks guys, CSRF implementations are never fun. :) Hope a fix is found soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6163.1561141501580%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue. (Previous: 0.29 worked)We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround for this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue. Thanks guys, CSRF implementations are never fun. :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6105.1561141440727%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue. I clicked downgrade to ` (Previous: 0.29 ` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required. worked) We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround for this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6076.1561141380697%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth ` 0.32 ` , we have no workarounds workaround to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6018.1561141321119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth 0.32, we have no workaround to resolve for this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6047.1561141321445%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and in general always .Deleting element in config.xml might be an option also for disabling CSRF. We can't do it via global security settings because of this bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5931.1561141262279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. Deleting element in config.xml might be an option also for disabling CSRF. We can't do it via global security settings because of this bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5960.1561141262694%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and always. That is why prioritization is critical on this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.6015.1561141264355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to major CRITICAL if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `hudson.security.csrf.GlobalCrumbIssuerConfiguration=false` but that is a really bad idea with the oauth integration and in general.Deleting element in config.xml might be an option also for disabling CSRF. We can't do it via global security settings because of this bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5902.1561141261760%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title
Jon Kelley edited a comment on JENKINS-57154
Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to major if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option ` \{{d-Dhudson hudson .security.csrf.GlobalCrumbIssuerConfiguration=false` }} but that is a really bad idea with the oauth integration and in general.Deleting element in config.xml might be an option also for disabling CSRF. We can't do it via global security settings because of this bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5873.1561140240647%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title
Jon Kelley edited a comment on JENKINS-57154
Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Restarted Jenkins after "downgrading" to 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option ` \ {{d-Dhudson.security.csrf.GlobalCrumbIssuerConfiguration=false` }}but that is a really bad idea with the oauth integration and in general.Deleting element in config.xml might be an option too also for disabling CSRF. We can't do it via global security settings because of this bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5815.1561140181306%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title
Jon Kelley edited a comment on JENKINS-57154
Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Upgrading this bug to major if you don't mind. Restarted Jenkins after "downgrading" to github-oauth 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `\{{d-Dhudson.security.csrf.GlobalCrumbIssuerConfiguration=false` }}but that is a really bad idea with the oauth integration and in general.Deleting element in config.xml might be an option also for disabling CSRF. We can't do it via global security settings because of this bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5844.1561140181826%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title
Jon Kelley edited a comment on JENKINS-57154
Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Restarted Jenkins after "downgrading" to 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. We may be able to force CSRF disabled in Jenkins v2 by setting java startup option `{{d-Dhudson.security.csrf.GlobalCrumbIssuerConfiguration=false` }}but that is a really bad idea with the oauth integration and in general.Deleting element in config.xml might be an option too for disabling CSRF. We can't do it via global security settings because of this bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5786.1561140120587%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley updated an issue Jenkins / JENKINS-57154 Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Change By: Jon Kelley Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5757.1561139941855%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1We upgraded to `0.32` github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? [EDIT] Restarted Jenkins after "downgrading" to 0.29 and we are still on github-oauth `0.32`, we have no workarounds to resolve this bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5728.1561139880758%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58147) Support Different Formats for Listing Plugins to be Downloaded
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58147 Support Different Formats for Listing Plugins to be Downloaded Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-21 17:48 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa The plugin manager should be able to take in inputs other than a .txt file. It should also be able to accept and parse formats such as yaml or json. Add Comment
[JIRA] (JENKINS-58146) Expose parameters creation to Jenkinsfile Pipeline
Title: Message Title João Pedro Abreu de Souza created an issue Jenkins / JENKINS-58146 Expose parameters creation to Jenkinsfile Pipeline Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2019-06-21 17:36 Labels: pipeline-compatibility Priority: Minor Reporter: João Pedro Abreu de Souza The use case is : my company is moving from Jenkins hosting and I want to put the parameters creation all on the declarative jenkinsfile of project, to make easy move without need to reconfigure all parameters on UI again. With this and configuration-as-code plugin, we can put almost all jenkins config on text files on git. Add Comment
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Jenkins ver 2.176.1 We upgraded to `0.32` on jenkins ver 2.176.1 github oauth and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all aroundIs there a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5696.1561138080727%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page We upgraded to `0.32` on jenkins ver 2.176.1 and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required. We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. What is the Is there a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5638.1561137721055%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page We upgraded to `0.32` on jenkins ver 2.176.1 and experience this issue.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required.We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. "No valid crumb was included in the request" errors all around Is there a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5667.1561137721436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page We upgraded to `0.32` on jenkins ver 2.176.1 and experience this issue. We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. The plugin said a restart wasn't required. We can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. What is the workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5609.1561137660592%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley edited a comment on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page We upgraded to `0.32` on jenkins ver 2.176.1 and experience this issue. Can We can 't edit global settings, security settings, security permissions on jobs or even edit workspace permissions.I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. What is the workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5580.1561136702691%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Kelley commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page We upgraded to `0.32` on jenkins ver 2.176.1 and experience this issue. Can't edit global settings, security settings, security permissions on jobs or even edit workspace permissions. I clicked downgrade to `0.29` and it said success, yet it still says `0.32` is installed and we lost the option to downgrade. What is the workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.5551.1561136701286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58145) Blue Ocean pipeline shows no progress
Title: Message Title Jonathan B created an issue Jenkins / JENKINS-58145 Blue Ocean pipeline shows no progress Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-06-21 16:48 Priority: Minor Reporter: Jonathan B After upgrading pipeline-model-definition 1.38 to 1.39, I started seeing strange behavior in one declarative pipeline. Unfortunately it's a complicated pipeline and I haven't had time to come up with a minimal case to reproduce the issue. In some situations, the Blue Ocean UI doesn't show progress. It appears as if the build hasn't started yet, even though it has (i.e. go to the console output in the classic UI, and the build is running). When the build gets to an input prompt, the header bar of Blue Ocean turns the "input prompt blue", but no prompt is visible, and no progress is still shown. It's necessary to navigate to the "classic" UI to respond to the prompt. The pipeline has a call to `input()` in the steps of its first stage. I don't know if this is relevant. I haven't seen the problem in our other pipelines, or even in an obviously reproducible way with the pipeline that does exhibit the issue. Downgrading to pipeline-model-definition:1.38 fixes the issue. Sorry for the vague report. I had to do the downgrade quickly to unblock my teammates, and didn't have time to investigate thoroughly.
[JIRA] (JENKINS-58138) Confusing saml plugin keystore breakage
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58138 Re: Confusing saml plugin keystore breakage The key store is needed by the pac4j library even do you do not use encryption, because of that the plugin manages a dummy keystore, it is created and the key is maintained in case it expired. It should be transparent for the user, but seems like for some reason cannot write the JENKINS_HOME/saml-jenkins-keystore.jks and also fails to read the keystore inside the jar, I will add the exception and the workaround to the Troubleshooting guide, also I will review if there is a better solution, probably I will remove the use of the demo keystore and show an error in the logs in that way you are aware that it is not possible to create the dummy keystore. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200183.1561110857000.5542.1561135560103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56379) Absorb pipeline-model-definition symbol-hetero-list.jelly into hetero-list.jelly
Title: Message Title Jonathan B assigned an issue to Josh Soref Jenkins / JENKINS-56379 Absorb pipeline-model-definition symbol-hetero-list.jelly into hetero-list.jelly Change By: Jonathan B Assignee: Jonathan B Josh Soref Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197965.1551674873000.5538.1561133640103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56379) Absorb pipeline-model-definition symbol-hetero-list.jelly into hetero-list.jelly
Title: Message Title Jonathan B assigned an issue to Jonathan B Jenkins / JENKINS-56379 Absorb pipeline-model-definition symbol-hetero-list.jelly into hetero-list.jelly Change By: Jonathan B Assignee: Josh Soref Jonathan B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197965.1551674873000.5536.1561133580106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Chris Carr commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files I'm hitting the same problem - I've been experimenting with using the P4 object to sync to a small subset of the stream we are building on. Using p4sync with the same credentials works correctly, but creating a p4 object and then syncing fails with "ERROR: P4: Task Exception: Invalid credentials". Unfortunately it's not practical to fully sync to our streams on the master, as they are quite large. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.5511.1561133100532%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Carlos Sanchez commented on JENKINS-58143 Re: Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized have you tried running with a lower number of seconds in -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=86400 https://github.com/jenkinsci/kubernetes-plugin/pull/429 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.5508.1561130760137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov updated an issue Jenkins / JENKINS-58143 Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Change By: Andrei Stepanov Attachment: jenkins-log-58143.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.5506.1561130520208%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58030) TFS plugin failing in Jenkins
Title: Message Title prav teja updated an issue Jenkins / JENKINS-58030 TFS plugin failing in Jenkins Change By: prav teja Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199979.1560368858000.5504.1561130220866%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov updated an issue Jenkins / JENKINS-58143 Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Change By: Andrei Stepanov Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.5502.1561129440379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov created an issue Jenkins / JENKINS-58143 Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-06-21 15:03 Priority: Minor Reporter: Andrei Stepanov Hello, Jun 21, 2019 2:10:17 PM FINE io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager scheduleReconnectSubmitting reconnect task to the executor Jun 21, 2019 2:10:17 PM WARNING io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2 onFailureExec Failure: HTTP 401, Status: 401 - Unauthorized java.net.ProtocolException: Expected HTTP 101 response but was '401 Unauthorized' at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:219) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:186) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Jun 21, 2019 2:10:17 PM FINE io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$3 executeScheduling reconnect task It happens on from time to time. We have other Jenkins master in the same project. The other master works good. Kubernetes plugins in: 1.16.1 Jenkins master is: Jenkins ver. 2.164.2
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Roman Komarov edited a comment on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable [~larry_west], I've found an ugly workaround to this - avoid using env and params in echo output as much as possible and then make a second echo showing the actual output. This still leaves lots of "Print message" in BlueOcean output, but at least people can see the actual phase action within the step .But you are right, this is very annoying and users become reluctant to use BO because of this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194144.1537309242000.5483.1561127400344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Roman Komarov commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable Larry West, I've found an ugly workaround to this - avoid using env and params in echo output as much as possible and then make a second echo showing the actual output. This still leaves lots of "Print message" in BlueOcean output, but at least people can see the actual phase. But you are right, this is very annoying and users become reluctant to use BO because of this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194144.1537309242000.5468.1561127340385%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57603) Git Plugin: No JCasC configurator for Submodule configurations
Title: Message Title Evaristo Gutierrez commented on JENKINS-57603 Re: Git Plugin: No JCasC configurator for Submodule configurations https://github.com/jenkinsci/git-plugin/pull/725 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199528.1558527868000.5466.1561127221416%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57603) Git Plugin: No JCasC configurator for Submodule configurations
Title: Message Title Evaristo Gutierrez updated JENKINS-57603 Jenkins / JENKINS-57603 Git Plugin: No JCasC configurator for Submodule configurations Change By: Evaristo Gutierrez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199528.1558527868000.5464.1561127221267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Thomas Gimpel commented on JENKINS-57967 Re: vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher In our Jenkins installation even all statically configured SSH slaves are broken after the update to 1.3.0 of the SSH Slaves plugin. The plugin changelog has note about breaking changes, but gives no hint, how to get the SSH slaves working again. We had to restore version 1.29.4 from the backup (the plugin manager failed to that). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199950.1560271877000.5460.1561126500144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title
Nick Jones edited a comment on JENKINS-57967
Re: vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Looking at [https://github.com/jenkinsci/vsphere-cloud-plugin/blob/6aee348fbe3a6c046383a2749de7b22c59152252/src/main/java/org/jenkinsci/plugins/vSphereCloudSlaveTemplate.java#L477-L481] and [https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L249-L251], and when the signature of this SSHLauncher constructor was last changed, I'm not sure how this ever worked, as it looks to be missing an argument for the {{sshHostKeyVerificationStrategy}} parameter {{ . Not sure what to do to fix? }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199950.1560271877000.5458.1561125240227%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title
Nick Jones commented on JENKINS-57967
Re: vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Looking at https://github.com/jenkinsci/vsphere-cloud-plugin/blob/6aee348fbe3a6c046383a2749de7b22c59152252/src/main/java/org/jenkinsci/plugins/vSphereCloudSlaveTemplate.java#L477-L481 and https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L249-L251, and when the signature of this SSHLauncher constructor was last changed, I'm not sure how this ever worked, as it looks to be missing an argument for the sshHostKeyVerificationStrategy parameter{{. Not sure what to do to fix?}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199950.1560271877000.5451.1561125180356%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()
Title: Message Title Karl Wirth commented on JENKINS-58048 Re: P4 error - No open file stream in ClientSystemFileCommands.writeFile() Investigation still progressing. Reports of this so far involve Virus checkers. CANNOT reproduce it artificially by locking the file using Powershell: (1) Run new job on a Windows slave. (2) Open a Powershell Window and exclusively lock the file: $myFile="C:\filestore\Jenkins\JOBS\workspace\MYJOB\MYFILE.txt" Set-ItemProperty $myFile -name IsReadOnly -value $false $file = [System.IO.File]::Open($myFile, "Open", "Read", "None") (3) Run the job again and see a different the error: ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): file 9.c operating system write error: C:\filestore\Jenkins\JOBS\workspace\MYJOB\MYFILE.txt (The process cannot access the file because it is being used by another process). (4) Unlock the file $file.Close() Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are
[JIRA] (JENKINS-58044) PDF Report output for Load Runner controller execution from Jenkins using Micro focus file system plugin
Title: Message Title Govind Sureka commented on JENKINS-58044 Re: PDF Report output for Load Runner controller execution from Jenkins using Micro focus file system plugin Hello Daniel, Could you please let us know when this feature would be available in the plugin. Thanks, Govind Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200064.1560766556000.5446.1561124401237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Govind Sureka commented on JENKINS-57334 Re: "Run on planned host" from Build section not working Hello Anda, Thanks for sharing this ne build of plugin. I created a Node and ran a job but it didn’t ran the Test Case though the status is Success. Could you please share a new version of plugin. See logs. Started by user admin Building remotely on Test1 in workspace d:\jenkins\workspace\UFT_Test No emails were triggered. [UFT_Test] $ d:\jenkins\workspace\UFT_Test\HpToolsLauncher.exe -paramfile props11062019080414105.txt "Started..." runtype is alm Timeout is set to: -1 Run mode is set to: RUN_PLANNED_HOST Trying to connect to project CreateTDConnection Login to ALM Logged in Connecting to domain and project Connected to domain and project connected to alm : True Node not found. Starting test set execution Test set name: 1_DashBoard, Test set id: 3001 Scheduler starts execution Run mode is: RUN_PLANNED_HOST Run host is: Number of tests in set: 1 Test 1: [1]02_ACCDashboard will run on host: log4net:ERROR [RollingFileAppender] Unable to acquire lock on file d:\jenkins\workspace\UFT_Test\. Could not find a part of the path 'd:\jenkins\workspace\UFT_Test\'. Problem while running TestSet: Exception from HRESULT: 0x80040459 "Scheduler started at:11/06/2019 08:04:32 --- Test set: 1_DashBoard, finished at 11/06/2019 08:04:32 Run status: Job succeeded, total tests: 1, succeeded: 0, failures: 0, errors: 0, warnings: 0 Unknown: Dispose ALM connection Email was triggered for: Success Sending email for trigger: Success Sending email to: a...@xyz.com Finished: SUCCESS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-58142) Use @ConfiguredWithCode for JMH benchmarks
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58142 Use @ConfiguredWithCode for JMH benchmarks Change By: Abhyudaya Sharma Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200187.1561118916000.5440.1561119000177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58142) Use @ConfiguredWithCode for JMH benchmarks
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-58142 Use @ConfiguredWithCode for JMH benchmarks Issue Type: Improvement Assignee: Abhyudaya Sharma Components: jenkins-test-harness Created: 2019-06-21 12:08 Priority: Minor Reporter: Abhyudaya Sharma The CascJmhBenchmarkState does the same job as @ConfiguredWithCode however, the annotations are not visible in the `state` class (created by JMH) visible to us in the benchmark. Make this annotation work with JMH benchmarks. Add Comment
[JIRA] (JENKINS-58142) Use @ConfiguredWithCode for JMH benchmarks
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-58142 Use @ConfiguredWithCode for JMH benchmarks Change By: Abhyudaya Sharma The CascJmhBenchmarkState does the same job as @ConfiguredWithCode however . However , the annotations are not visible in the `state` class (created by JMH) visible to us in the benchmark. Make this annotation work with JMH benchmarks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200187.1561118916000.5438.1561118940348%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57429) SYSTEM; is prohibited as a username for security reasons.
Title: Message Title Bogdan Grosu edited a comment on JENKINS-57429 Re: SYSTEM; is prohibited as a username for security reasons. Hi guys, Is it possible to get an update on this bug? Is this a bug or not? What would be the way to remediate the issue? Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199241.1557750187000.5434.1561118820049%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57429) SYSTEM; is prohibited as a username for security reasons.
Title: Message Title Bogdan Grosu commented on JENKINS-57429 Re: SYSTEM; is prohibited as a username for security reasons. Hi guys, Is it possible to get an update on this bug? Is this a bug or not? Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199241.1557750187000.5433.1561118760043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Stefan Verhoeff commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Sure that might solve MY issue right now. The point is that this issue exists for everyone who upgrades mq-notifier-plugin, so this is a bug that needs to fixed in the plugin itself and not with a workaround. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5431.1561117440129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Thien Vu commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Hi you can go to the link above. Change it to your plugin: mq-notifier-plugin try to get the older version and upload to Jenkins to match with workflow-step-api Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5429.1561117080372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56861) Send PMD, FB, Checkstyle metrics to influxDB
Title: Message Title Philipp Deuchert commented on JENKINS-56861 Re: Send PMD, FB, Checkstyle metrics to influxDB We have the same Problem. We tried to push the results of the static code analytic(PMD, Checkstyle, Findbugs) to the InfluxDB. Is there a implementation to be expected? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198523.1554266985000.5426.1561117080303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title
Bogdan Grosu updated an issue
Jenkins / JENKINS-58141
Jenkins Startup issues with jobConfigHistory
Change By:
Bogdan Grosu
I have update Jenkins to the latest version - 2.176.1.Now when I startup Jenkins I see this warning/error in the startup script. {code:java}Jun 21, 2019 11:13:54 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorJun 21, 2019 11:13:54 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorWARNING: Failed to instantiate Key[type=jenkins.telemetry.Correlator, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) Tried proxying jenkins.telemetry.Correlator to support a circular dependency, but it is not an interface.1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:335) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:193) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at hudson.model.User.allocateDefaultPropertyInstancesAsNeeded(User.java:205) at hudson.model.User.load(User.java:194) at hudson.model.User.(User.java:187) at hudson.model.User.getOrCreateById(User.java:519) at hudson.model.User.getById(User.java:615) at hudson.model.User.get(User.java:599) at hudson.plugins.jobConfigHistory.PluginUtils.getSystemHistoryDao(PluginUtils.java:132) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.getHistoryDao(JobConfigHistorySaveableListener.java:92) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:56) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.Descriptor.save(Descriptor.java:877) at jenkins.telemetry.Correlator.(Correlator.java:52) at jenkins.telemetry.Correlator$$FastClassByGuice$$5678e8d6.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title Bogdan Grosu created an issue Jenkins / JENKINS-58141 Jenkins Startup issues with jobConfigHistory Issue Type: Bug Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2019-06-21 11:28 Priority: Minor Reporter: Bogdan Grosu I have update Jenkins to the latest version - 2.176.1. Now when I startup Jenkins I see this warning/error in the startup script. Jun 21, 2019 11:13:54 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorJun 21, 2019 11:13:54 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorWARNING: Failed to instantiate Key[type=jenkins.telemetry.Correlator, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying jenkins.telemetry.Correlator to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:335) at hudson.ExtensionList.load(ExtensionList.java:381) at
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Stefan Verhoeff commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Thanks Thien Vu. I already have 2.14 installed, but because the new version of mq-notifier-plugin requires a newer version , it was installed an not compatible with the Jenkins version. My point of reporting this issue is to highlight that the update path is broken for older Jenkins versions. I guess the minimal required Jenkins version for mq-notifier-plugin can be updated to v2.121.1 to avoid this? At least a user can then not break Jenkins accidentally. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5418.1561116240175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58140) Support @LocalData for JMH benchmarks
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-58140 Support @LocalData for JMH benchmarks Issue Type: Improvement Assignee: Abhyudaya Sharma Components: jenkins-test-harness Created: 2019-06-21 11:20 Priority: Minor Reporter: Abhyudaya Sharma Allow configuring JMH benchmarks with config.xml files like it is done in JTH's @LocalData Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-49215) java.lang.ClassCastException: hudson.plugins.git.browser.GitLab.version expects class java.lang.String but received class java.lang.Double
Title: Message Title Mark Waite commented on JENKINS-49215 Re: java.lang.ClassCastException: hudson.plugins.git.browser.GitLab.version expects class java.lang.String but received class java.lang.Double I don't have a final date for git client plugin 3.0.0 release and git plugin 4.0.0 release, but I plan to release a new beta of both by end of day June 22, 2019. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188055.1517072065000.5411.1561115100239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57928) Add JCasc support to JMH benchmarks
Title: Message Title Abhyudaya Sharma updated JENKINS-57928 Jenkins / JENKINS-57928 Add JCasc support to JMH benchmarks Change By: Abhyudaya Sharma Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/configuration-as-code-plugin/releases/tag/configuration-as-code-1.21 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199902.1560142004000.5409.1561114920636%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58139) User cannot access his job inside the folder when global "authenticated user" does not have read permission
Title: Message Title parsa vali created an issue Jenkins / JENKINS-58139 User cannot access his job inside the folder when global "authenticated user" does not have read permission Issue Type: Bug Assignee: Daniel Beck Components: matrix-auth-plugin Created: 2019-06-21 10:17 Environment: Jenkins version: 2.176.1 Matrix-auth plugin version: 2.4.2 Folders plugin version: 6.9 Priority: Minor Reporter: parsa vali Issue I created two users (user1 and user2) in Jenkins. user1 is Administrator globally. Authenticated user has "job:read" globally. I created a folder and a new "Freestyle project" Inside the folder. In the job configuration I enabled "project-based security" with "Do not inherit permission grants from other ACLs" and I also gave "job:read" permission to "user2". user2 is able to see the job without any problems. By removing "job:read" for authenticated user globally user2 cannot see his job indeed he is configured to read the job and "Do not inherit permission grants from other ACLs" is set on the job-level. Note: testing same scenario by creating a job on the root level works completely. Issue occurs only inside Folders.
[JIRA] (JENKINS-54537) Scripted Pipeline does not work due to tags
Title: Message Title Donald Leckie commented on JENKINS-54537 Re: Scripted Pipeline does not work due to tags Attached patch which works for me inspired by Cédric SARRE's comment above.[JENKINS-54537]_Scripted_Pipeline_does_not_work_due_to_tags.patch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195309.1541669457000.5405.156920166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54537) Scripted Pipeline does not work due to tags
Title: Message Title Donald Leckie updated an issue Jenkins / JENKINS-54537 Scripted Pipeline does not work due to tags Change By: Donald Leckie Attachment: [JENKINS-54537]_Scripted_Pipeline_does_not_work_due_to_tags.patch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195309.1541669457000.5402.156740312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55264) Threshold Number of tests not working
Title: Message Title Klynton Fowler commented on JENKINS-55264 Re: Threshold Number of tests not working I'm also experiencing this error. However manually changing the value in the XML to 1 does resolve the issue, as long as you restart Jenkins after making the change (Reload Config from Disk doesn't seem to work). But if you ever Configure the job and save changes it will revert back to 2. As a workaround I've got a quick batch file that auto updates the entry in the XML which runs as part of my Jenkins startup. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196348.1545234045000.5398.156320196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58138) Confusing saml plugin keystore breakage
Title: Message Title
Tomasz Śniatowski updated an issue
Jenkins / JENKINS-58138
Confusing saml plugin keystore breakage
Change By:
Tomasz Śniatowski
* Have authentication set up using SAML with no custom encryption options* Wait (?) (I suspect waiting a year for validity expiration is what triggers this)* Log in attempts break with a verbose backtrace on the login page{code}Stack traceorg.pac4j.core.exception.TechnicalException: Unsupported resource format: jar:file:/srv/jenkins/home/plugins/saml/WEB-INF/lib/saml.jar!/samlKeystore.jks. Use a relative or absolute path at org.pac4j.core.util.CommonHelper$1.getFilename(CommonHelper.java:373) at org.pac4j.saml.client.SAML2ClientConfiguration.getKeystorePath(SAML2ClientConfiguration.java:313) at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:92) at org.pac4j.saml.client.SAML2Client.initCredentialProvider(SAML2Client.java:174) at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:111) at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:145) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:64) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doCommenceLogin(SamlSecurityRealm.java:258) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739){code}The call stack above is misleading. It appears to be caused by the "demo keystore" path (PAC4J_DEMO_KEYSTORE) being invalid in principle. The real issue is however that the plugin tries to use the demo key store in the first place, which is hinted at in a brief log line with no backtrace:{code}WARNING: Using bundled keystore : /srv/jenkins/home/saml-jenkins-keystore.jks (Permission denied)Jun 19, 2019 8:19:44 AM org.jenkinsci.plugins.saml.OpenSAMLWrapper createSAML2ClientWARNING: Using bundled keystore : resource:samlKeystore.jks{code}The configuration used no custom encryption settings, so whatever default key store the plugin wanted was used. Trying to disable and enable the saml authentication did not help, trying to use a custom key store in encryption settings an dreverting back to the default did not work.Looking at the code I realized it has code to create the key store from scratch if it doesn't exist and sure
[JIRA] (JENKINS-58138) Confusing saml plugin keystore breakage
Title: Message Title Tomasz Śniatowski created an issue Jenkins / JENKINS-58138 Confusing saml plugin keystore breakage Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2019-06-21 09:54 Priority: Minor Reporter: Tomasz Śniatowski Have authentication set up using SAML with no custom encryption options Wait (I suspect waiting a year for validity expiration is what triggers this) Log in attempts break with a verbose backtrace on the login page Stack trace org.pac4j.core.exception.TechnicalException: Unsupported resource format: jar:file:/srv/jenkins/home/plugins/saml/WEB-INF/lib/saml.jar!/samlKeystore.jks. Use a relative or absolute path at org.pac4j.core.util.CommonHelper$1.getFilename(CommonHelper.java:373) at org.pac4j.saml.client.SAML2ClientConfiguration.getKeystorePath(SAML2ClientConfiguration.java:313) at org.pac4j.saml.crypto.KeyStoreCredentialProvider.(KeyStoreCredentialProvider.java:92) at org.pac4j.saml.client.SAML2Client.initCredentialProvider(SAML2Client.java:174) at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:111) at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:145) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:64) at
[JIRA] (JENKINS-41476) Jenkinsfile fails with BOM
Title: Message Title
Harald Albers edited a comment on JENKINS-41476
Re: Jenkinsfile fails with BOM
I increased priority for this issue because it now has a wider scope: any pipeline job can be affected, and the cause can be hard to find.As an example, the I have a production job might also fail that fails with {code:java}groovy.lang.MissingPropertyException: No such property: for class: groovy.lang.Binding{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178273.1485433226000.5385.1561108920193%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54657) dropWhile doesn't behave correctly
Title: Message Title
S. Panchenko commented on JENKINS-54657
Re: dropWhile doesn't behave correctly
Workaround: create NonCPS-function in a shared library:
@NonCPS
static dropWhileIfNotFound(final c, final search_item) {
return c.dropWhile{ it != search_item }
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195448.1542306982000.5382.1561108860281%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58137) readCSV fails when passing CSVFormat
Title: Message Title
Florian Geckeler updated an issue
Jenkins / JENKINS-58137
readCSV fails when passing CSVFormat
Change By:
Florian Geckeler
Hi, I would like to read a csv String or file as documented here: [https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/]When I pass any CSVFormat (tried it with 'DEFAULT', 'EXCEL', and using the newFormat method as well) as format to the step the pipeline fails with error [1].Steps to reproduce: execute following script in a pipeline: { { code:java} node(''){ }} {{ String csv = "\"http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764')\", \"hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1\"" }} {{ def rec = readCSV text: csv, format: CSVFormat.DEFAULT }} } { { code } }} [1]: {code: java }java .lang.ClassCastException: class org.jenkinsci.plugins.pipeline.utility.steps.csv.ReadCSVStep.setFormat() expects class org.apache.commons.csv.CSVFormat but received class org.apache.commons.csv.CSVFormat at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:446) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:386) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:290) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:205) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:25) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:13) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:262) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) 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:20)Caused: java.lang.IllegalArgumentException: Could not instantiate {text="[http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764|http://opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner=] ')", "hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1", format=Delimiter=<,> QuoteChar=<"> RecordSeparator=< > EmptyLines:ignored SkipHeaderRecord:false} for ReadCSVStep(file?: String, format?: org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on
[JIRA] (JENKINS-58137) readCSV fails when passing CSVFormat
Title: Message Title
Florian Geckeler updated an issue
Jenkins / JENKINS-58137
readCSV fails when passing CSVFormat
Change By:
Florian Geckeler
Hi, I would like to read a csv String or file as documented here: [https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/]When I pass any CSVFormat (tried it with 'DEFAULT', 'EXCEL', and using the newFormat method as well) as format to the step the pipeline fails with error [1].Steps to reproduce: execute following script in a pipeline: {{node(''){}} {{ String csv = "\"http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764')\", \"hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1\""}} {{ def rec = readCSV text: csv, format: CSVFormat.DEFAULT}} {{}}} [1]: {{ }}{{ java.lang.ClassCastException: class org.jenkinsci.plugins.pipeline.utility.steps.csv.ReadCSVStep.setFormat() expects class org.apache.commons.csv.CSVFormat but received class org.apache.commons.csv.CSVFormat }} {{ at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:446) }} {{ at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:386) }} {{ at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:290) }} {{ at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:205) }} {{ at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:25) }} {{ at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:13) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:262) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) }} {{ at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) }} {{ at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) }} {{ 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:20) }} {{ Caused: java.lang.IllegalArgumentException: Could not instantiate }} { {{ text="[http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764|http://opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner=] ')", "hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1", format=Delimiter=<,> QuoteChar=<"> RecordSeparator=< > EmptyLines:ignored SkipHeaderRecord:false} }}{{ for ReadCSVStep(file?:
[JIRA] (JENKINS-58137) readCSV fails when passing CSVFormat
Title: Message Title
Florian Geckeler updated an issue
Jenkins / JENKINS-58137
readCSV fails when passing CSVFormat
Change By:
Florian Geckeler
Hi, I would like to read a csv String or file as documented here: [https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/]When I pass any CSVFormat (tried it with 'DEFAULT', 'EXCEL', and using the newFormat method as well) as format to the step the pipeline fails with error [1].Steps to reproduce: execute following script in a pipeline: {{node(''){}} {{ String csv = "\"http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764')\", \"hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1\""}} {{ def rec = readCSV text: csv, format: CSVFormat.DEFAULT}} {{}}} [1]: {{ }} ava {{java .lang.ClassCastException: class org.jenkinsci.plugins.pipeline.utility.steps.csv.ReadCSVStep.setFormat() expects class org.apache.commons.csv.CSVFormat but received class org.apache.commons.csv.CSVFormat }} {{ at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:446) }} {{ at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:386) }} {{ at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:290) }} {{ at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:205) }} {{ at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:25) }} {{ at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:13) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:262) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) }} {{ at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) }} {{ at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) }} {{ 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:20) }} {{ Caused: java.lang.IllegalArgumentException: Could not instantiate }} { {{ text="[http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764|http://opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner=] ')", "hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1", format=Delimiter=<,> QuoteChar=<"> RecordSeparator=< > EmptyLines:ignored SkipHeaderRecord:false} }}{{ for
[JIRA] (JENKINS-58137) readCSV fails when passing CSVFormat
Title: Message Title
Florian Geckeler updated an issue
Jenkins / JENKINS-58137
readCSV fails when passing CSVFormat
Change By:
Florian Geckeler
Hi, I would like to read a csv String or file as documented here: [https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/] When I pass any CSVFormat (tried it with 'DEFAULT', 'EXCEL', and using the newFormat method as well) as format to the step the pipeline fails with error [1].Steps to reproduce: execute following script in a pipeline: {{node(''){}} {{ String csv = "\"http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764')\", \"hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1\""}} {{ def rec = readCSV text: csv, format: CSVFormat.DEFAULT}} {{}}} When I pass any CSVFormat (tried it with 'DEFAULT', 'EXCEL', and using the newFormat method as well) as format to the step the pipeline fails with following error [1] : {quote}java ava .lang.ClassCastException: class org.jenkinsci.plugins.pipeline.utility.steps.csv.ReadCSVStep.setFormat() expects class org.apache.commons.csv.CSVFormat but received class org.apache.commons.csv.CSVFormat at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:446) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:386) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:290) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:205) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:25) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:13) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:262) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) 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:20) Caused: java.lang.IllegalArgumentException: Could not instantiate Unknown macro: \ {text="[http } :///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764|http://opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner=] ')", "hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1", format=Delimiter=<,> QuoteChar=<"> RecordSeparator=<> EmptyLines:ignored
[JIRA] (JENKINS-58137) readCSV fails when passing CSVFormat
Title: Message Title
Florian Geckeler updated an issue
Jenkins / JENKINS-58137
readCSV fails when passing CSVFormat
Change By:
Florian Geckeler
Hi, I would like to read a csv String or file as documented here: [https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/] {{node(''){}} {{ String csv = "\"http:///opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner(BusinessPartner='1003764')\", \"hystrix-.addressmgr.commands.GetSingleBusinessPartnerByIdCommand#t=#u=-1\""}} {{ def rec = readCSV text: csv, format: CSVFormat.DEFAULT}} {{}}} When I pass any CSVFormat (tried it with 'DEFAULT', 'EXCEL', and using the newFormat method as well) as format to the step the pipeline fails with following error:{quote}java.lang.ClassCastException: class org.jenkinsci.plugins.pipeline.utility.steps.csv.ReadCSVStep.setFormat() expects class org.apache.commons.csv.CSVFormat but received class org.apache.commons.csv.CSVFormat at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:446) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:386) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:290) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:205) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:25) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:13) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:262) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) 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:20) Caused: java.lang.IllegalArgumentException: Could not instantiate Unknown macro: \{text="[http} for ReadCSVStep(file?: String, format?: org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class org.apache.commons.csv.CSVFormat, text?: String) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:293) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:205) at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepDescriptorImpl.newInstance(AbstractFileOrTextStepDescriptorImpl.java:25) at
[JIRA] (JENKINS-41476) Jenkinsfile fails with BOM
Title: Message Title
Harald Albers edited a comment on JENKINS-41476
Re: Jenkinsfile fails with BOM
I could reproduce this with a simple Jenkinsfile that just contains "echo 'Hello-World!'".See attached file [^Jenkinsfile].*Steps to reproduce*# Add the attached Jenkinsfile to a GIT repo.# Create a Pipeline Job.# Set Definition to "Pipeline script from SCM".# Set "SCM "to "Git", configure the repository and point "Script Path" to the Jenkinsfile.If the file has a UTF-8-BOM, the Job fails with {code:java}java.lang.NoSuchMethodError: No such DSL method 'echo' found among steps [archive, bat, ... zip] or globals [currentBuild, docker, env, params, pipeline, scm]{code}Remove the BOM, check in, push and the job will run as expected. Tested with Jenkins ver. 2.176.1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178273.1485433226000.5366.1561107540187%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
