[JIRA] (JENKINS-56796) JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins
Title: Message Title Ralf Loesche updated JENKINS-56796 Jenkins / JENKINS-56796 JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins Change By: Ralf Loesche Status: Fixed but Unreleased 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-56796) JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins
Title: Message Title Ralf Loesche updated JENKINS-56796 Defining credentials for remote jenkins is deprecated - so it does not make sense to configure this Jenkins / JENKINS-56796 JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins Change By: Ralf Loesche Status: Open Fixed but Unreleased Resolution: Not A Defect 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-56796) JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins
Title: Message Title Ralf Loesche created an issue Jenkins / JENKINS-56796 JCASC and ParameterizedRemoteTrigger: Not able to set auth for remote Jenkins Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, parameterized-remote-trigger-plugin Created: 2019-03-28 14:55 Environment: Windows 2012 Jenkins 2.167 JCASC 1.7 Parameterized Remote Trigger 3.0.7 Labels: plugin configuration Priority: Minor Reporter: Ralf Loesche I configured a remote Jenkins with global Jenkins credentials ( username/password ). Works fine. Now I want to put that configuration in a jenkins.yaml in order to automatically get this configuration. The export from JCASC looks like this ( just Credentials and the remote Jenkins - leading blancs replaced by .): credentials: ..system: domainCredentials: - credentials: ..- usernamePassword: ..description: "Jenkinsuser" ..id: "jenkinsuser" ..password: xxx ..scope: GLOBAL ..username: "User" unclassified: ..remoteBuildConfiguration: remoteSites: - address: "http://xxx.xxx.xxx.xxx:/" ..auth2: CredentialsAuth: ..credentials: "jenkinsuser" ..displayName: "JenkinsUser" If I read that back in I get a Nullpointer - see below. Jenkins does not find the credential and the username. I tried to name the credentials parameter differently ( credentialsId ). But I do not get it to work. Googling and looking into the source of the plugins did not help ( I'm not that deep into the Jenkins plugins ). I might need a pointer to get me startet with
