[JIRA] (JENKINS-61319) Missing "secret text" (string) credential?
Title: Message Title Brendan Holmes closed an issue as Duplicate Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-59971 Jenkins / JENKINS-61319 Missing "secret text" (string) credential? Change By: Brendan Holmes Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61319) Missing "secret text" (string) credential?
Title: Message Title Brendan Holmes commented on JENKINS-61319 Re: Missing "secret text" (string) credential? This is becuase job-dsl does not support the plain-credentials plugin. Issue #59971 is already open for this: so closing this duplicate. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204907.1583311278000.4703.1583318280107%40Atlassian.JIRA.
[JIRA] (JENKINS-61319) Missing "secret text" (string) credential?
Title: Message Title
Brendan Holmes created an issue
Jenkins / JENKINS-61319
Missing "secret text" (string) credential?
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2020-03-04 08:41
Priority:
Minor
Reporter:
Brendan Holmes
Trying to create a "secret text" (string) credential in a folder using job-dsl. But according to the job-dsl api-viewer, our Jenkins only has the following credential types: _basicSSHUserPrivateKey {} certificateCredentialsImpl {} fileSystemServiceAccountCredential {} openShiftBearerTokenCredentialImpl {} usernamePasswordCredentialsImpl {}_ We can create a string credential manually in the webui. Has "secret text" not been implmemented in job-dsl? I'm expecting a type should exist with properties: scope, id, description, and secret. Our folder definition starts:
folder("test_folder") {
displayName("Test Folder")
description("Our test folder")
properties {
folderCredentialsProperty {
domainCredentials {
domainCredentials {
domain {
name("main")
description("")
}
credentials {
[JIRA] (JENKINS-61319) Missing "secret text" (string) credential?
Title: Message Title
Brendan Holmes updated an issue
Jenkins / JENKINS-61319
Missing "secret text" (string) credential?
Change By:
Brendan Holmes
Trying to create a "secret text" (string) credential in a folder using job-dsl. But according to the job-dsl api-viewer, our Jenkins only has the following credential types: _basicSSHUserPrivateKey basicSSHUserPrivateKey {}certificateCredentialsImpl {}fileSystemServiceAccountCredential {}openShiftBearerTokenCredentialImpl {}usernamePasswordCredentialsImpl {} _ We can create a string credential manually in the webui. Has "secret text" not been implmemented in job-dsl? I'm expecting a type should exist with properties: scope, id, description, and secret.Our folder definition starts:{code:java} folder("test_folder") {displayName("Test Folder")description("Our test folder")properties { folderCredentialsProperty {domainCredentials { domainCredentials {domain { name("main") description("")}credentials { {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title Brendan Holmes commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Yes changing the port to something other than 5 seems to have fixed for us too. Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.164374.1438763471000.1230.1581968940190%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title Brendan Holmes edited a comment on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Did you find a solution [~iamveritas]? We're experiencing this port 5 conflict too running in docker. I expect it's a race condition. Our test jenkins with the same configuration, but fewer jobs & no persistent storage doesn't experience it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.164374.1438763471000.771.1581952140387%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title Brendan Holmes commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Did you find a solution ovi craciun? We're experiencing this too running in docker. I expect it's a race condition. Our test jenkins with the same configuration, but fewer jobs & no persistent storage doesn't experience it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.164374.1438763471000.769.1581952140360%40Atlassian.JIRA.
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Jenkins client in Keycloak using the ["Keycloak config" here . |https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " _ is missing the Overall/Read permission_ permission ".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. http:///whoAmI/ doesn't show any group memberships, but not sure if it should. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Jenkins client in Keycloak using the ["Keycloak config" here . |https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Jenkins client in Keycloak using the ["Keycloak config" here.|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " _ is missing the Overall/Read permission permission_ ".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203298.1574859362000.7808.1574867940232%40Atlassian.JIRA.
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've synced our groups in Keycloak and then added a mapper to the Keycloak Jenkins client in Keycloak using the ["Keycloak config" here |https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284]Authorization fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission".This plugin gives nowhere to add a ["Token Claim Name"|https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've added a mapper to the Keycloak client using the ["Keycloak config" here | https://github.com/jenkinsci/oic-auth-plugin/issues/8 #issuecomment-403000284] .] Authorization fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission".This plugin gives nowhere to add a ["Token Claim Name"| https://github.com/jenkinsci/oic-auth-plugin/issues/8 #issuecomment-403000284] defined in our Keycloak mapper. Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes created an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Issue Type: Bug Assignee: D. Lauer Components: keycloak-plugin Created: 2019-11-27 12:56 Environment: Jenkins version: 2.190.3 Keycloak plugin version: 2.3.0 Priority: Minor Reporter: Brendan Holmes We would like to login using AD group membership. We've added a mapper to the Keycloak client using the "Keycloak config" here Authentication fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission". This plugin gives nowhere to add a "Token Claim Name".] Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've added a mapper to the Keycloak client using the ["Keycloak config" here| [https://github.com/jenkinsci/oic-auth-plugin/issues/8 #issuecomment-403000284].] Authentication Authorization fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission".This plugin gives nowhere to add a ["Token Claim Name"| [https://github.com/jenkinsci/oic-auth-plugin/issues/8 #issuecomment-403000284] defined in our Keycloak mapper. |https://github.com/jenkinsci/oic-auth-plugin/issues/8#issuecomment-403000284 ].] Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are
[JIRA] (JENKINS-60303) Authorize access by group membership using keycloak-plugin
Title: Message Title Brendan Holmes updated an issue Jenkins / JENKINS-60303 Authorize access by group membership using keycloak-plugin Change By: Brendan Holmes We would like to login using AD group membership. We've added a mapper to the Keycloak client using the ["Keycloak config" here|#issuecomment-403000284].]Authorization fails unless user is added to Project Matrix permissions rather than group. " is missing the Overall/Read permission".This plugin gives nowhere to add a ["Token Claim Name"|#issuecomment-403000284] defined in our Keycloak mapper. ].] Am I right that this plugin lacks ability to login by virtue of group membership? If so this is a feature request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title Brendan Holmes updated JENKINS-56739 Jenkins / JENKINS-56739 job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..." Change By: Brendan Holmes Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title Brendan Holmes closed an issue as Not A Defect Jenkins / JENKINS-56739 job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..." Change By: Brendan Holmes 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title
Brendan Holmes updated an issue
Jenkins / JENKINS-56739
job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Change By:
Brendan Holmes
Hi,The below script works fine on job-dsl-plugin 1.71:{code:java}pipelineJob("restart_jenkins") { steps {systemGroovyScriptFile('import hudson.model.*; Hudson.instance.doSafeRestart(null);') {} }}{code}But fails to create a job on 1.72 with error: { noformat code:java }ERROR: (script, line 4) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types: (script$_run_closure1$_closure3) values: [script$_run_closure1$_closure3@6b5277ea]{ noformat code } Any ideas?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title
Brendan Holmes created an issue
Jenkins / JENKINS-56739
job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-03-25 11:32
Priority:
Minor
Reporter:
Brendan Holmes
Hi, The below script works fine on job-dsl-plugin 1.71:
pipelineJob("restart_jenkins") {
steps {
systemGroovyScriptFile('import hudson.model.*; Hudson.instance.doSafeRestart(null);') {}
}
}
But fails to create a job on 1.72 with error:
ERROR: (script, line 4) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types: (script$_run_closure1$_closure3) values: [script$_run_closure1$_closure3@6b5277ea]
Any ideas?
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Brendan Holmes commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free JDK10 is still available, but the plugin now has the wrong URL for it. Per the issue I've just opened, first part of the URL should be: http://download.oracle.com/otn instead of: http://download.oracle.com/otn-pub Can we get this corrected? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54522) Host JDK Tool Plugin download failing
Title: Message Title Brendan Holmes created an issue Jenkins / JENKINS-54522 Host JDK Tool Plugin download failing Issue Type: Bug Assignee: Devin Nusbaum Attachments: Untitled.png Components: jdk-tool-plugin Created: 2018-11-07 18:16 Priority: Major Reporter: Brendan Holmes I'm on jdk-tool:1.1 and Jenkins 2.138.2. I've configured JDK10 in Global Tools per the attached screenshot. When running a job that uses it, I get: Installing JDK jdk-10.0.2-oth-JPR Downloading JDK from http://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.io.IOException: Failed to request https://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz?AuthParam=1541612216_106847a9a60b4e512bb6e81d31a78d22 exit code=404 I believe these URLs should be: http://download.oracle.com/otn instead of: http://download.oracle.com/otn-pub I've tried using other installer methods such as Extract *.zip/*.tar.gz and also the Custom Tool plugin instead, but these lack the authentication-handling needed to download JDK from Oracle. If the "Install from java.sun.com" method is currently broken, how are people using the official JDK with Jenkins? Doesn't seem to be a public docker image for it. Is everyone using openjdk instead? Or maintaining their own jdk docker images?
[JIRA] [core] (JENKINS-22710) Broken Debian upgrades because postinst doesn't check for present group/user
Brendan Holmes commented on JENKINS-22710 Broken Debian upgrades because postinst doesnt check for present group/user Getting this with 1.564 in Lubuntu 14.04 LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
