[JIRA] (JENKINS-39754) Config Provider Files created by DSL cannot be used via Pipeline
Title: Message Title Jason Kulatunga commented on JENKINS-39754 Re: Config Provider Files created by DSL cannot be used via Pipeline Hey Daniel Yeah, that looks like exactly what we need. The syntax looks a bit easier to understand (customConfigFile vs configFiles) and the id is used as a primary identifier. I haven't verified that it works, but from what I can see it looks like it should solve our problems Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39754) Config Provider Files created by DSL cannot be used via Pipeline
Title: Message Title
Jason Kulatunga updated an issue
Jenkins / JENKINS-39754
Config Provider Files created by DSL cannot be used via Pipeline
Change By:
Jason Kulatunga
Config provider files cannot be created with a constant ID via the Job DSL. This is a problem as the Config provider Pipeline step only accepts ID's as a reference, which is are dynamically generated by the Job DSL . {code:java}configFileProvider([configFile(fileId: 'maven-settings', variable: 'MAVEN_SETTINGS')]) {sh 'mvn -s $MAVEN_SETTINGS clean package'}{code}The Job DSL should allow specifying the ID when creating a new Config provider file (just as we can when creating Config provider files through the UI)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-39754) Config Provider Files created by DSL cannot be used via Pipeline
Title: Message Title
Jason Kulatunga updated an issue
Jenkins / JENKINS-39754
Config Provider Files created by DSL cannot be used via Pipeline
Change By:
Jason Kulatunga
Config provider files cannot be created with a constant ID via the Job DSL. This is a problem as the Config provider Pipeline step only accepts ID's as a reference, which are dynamically generated by the Job DSL. {code:java}configFileProvider([configFile(fileId: 'maven-settings', variable: 'MAVEN_SETTINGS')]) {sh 'mvn -s $MAVEN_SETTINGS clean package'}{code}The Job DSL should allow specifying the a custom/static ID when creating a new Config provider file (just as we can when creating Config provider files through the UI)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-39754) Config Provider Files created by DSL cannot be used via Pipeline
Title: Message Title
Jason Kulatunga created an issue
Jenkins / JENKINS-39754
Config Provider Files created by DSL cannot be used via Pipeline
Issue Type:
Bug
Assignee:
Daniel Spilker
Attachments:
Screen Shot 2016-11-15 at 10.53.04 AM.png
Components:
job-dsl-plugin
Created:
2016/Nov/15 6:55 PM
Environment:
job-dsl: v1.53 config-file-provider: v2.13
Priority:
Major
Reporter:
Jason Kulatunga
Config provider files cannot be created with a constant ID via the Job DSL. This is a problem as the Config provider Pipeline step only accepts ID's as a reference, which is unknown.
configFileProvider(
[configFile(fileId: 'maven-settings', variable: 'MAVEN_SETTINGS')]) {
sh 'mvn -s $MAVEN_SETTINGS clean package'
}
The Job DSL should allow specifying the ID when creating a new Config provider file (just as we can when creating Config provider files through the UI)
[JIRA] (JENKINS-39754) Config Provider Files created by DSL cannot be used via Pipeline
Title: Message Title
Jason Kulatunga updated an issue
Jenkins / JENKINS-39754
Config Provider Files created by DSL cannot be used via Pipeline
Change By:
Jason Kulatunga
Config provider files cannot be created with a constant ID via the Job DSL. This is a problem as the Config provider Pipeline step only accepts ID's as a reference, which is unknown dynamically generated . {code:java}configFileProvider([configFile(fileId: 'maven-settings', variable: 'MAVEN_SETTINGS')]) {sh 'mvn -s $MAVEN_SETTINGS clean package'}{code}The Job DSL should allow specifying the ID when creating a new Config provider file (just as we can when creating Config provider files through the UI)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more
[JIRA] [ldap-plugin] (JENKINS-25826) Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box
Title: Message Title
Jason Kulatunga edited a comment on JENKINS-25826
Re: Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box
This was also a huge issue for us. We traced the issue to the Mailer/ext-email plugins, by verifying that a vanilla jenkins install doesn't have this issue, and then individually deleting config files until we found the culprit. We think it has something to do with [https://issues.jenkins-ci.org/browse/JENKINS-20595]If the _hudson.tasks.Mailer.xml_ file exists with a _hudsonUrl_ entry inside, and the _jenkins.model.JenkinsLocationConfiguration.xml_ file doesn't exist, it seems that something goes horribly wrong during the login. *Broken*{{$ cat hudson.tasks.Mailer.xml @***.com https://***.com/ build@***.com localhost false UTF-8$ cat jenkins.model.JenkinsLocationConfiguration.xmlcat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory}}*Fix 1*{{$ cat hudson.tasks.Mailer.xml @***.com build@***.com localhost false UTF-8$ cat jenkins.model.JenkinsLocationConfiguration.xmlcat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory}}*Fix 2*{{$ cat hudson.tasks.Mailer.xml @***.com < hudsonUrl>https://***.com/ < adminAddress>build@***.com localhost false UTF-8$ cat jenkins.model.JenkinsLocationConfiguration.xml Build Jenkins http://***.com/}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [ldap-plugin] (JENKINS-25826) Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box
Title: Message Title
Jason Kulatunga commented on JENKINS-25826
Re: Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box
This was also a huge issue for us. We traced the issue to the Mailer/ext-email plugins, by verifying that a vanilla jenkins install doesn't have this issue, and then individually deleting config files until we found the culprit. We think it has something to do with https://issues.jenkins-ci.org/browse/JENKINS-20595 If the hudson.tasks.Mailer.xml file exists with a hudsonUrl entry inside, and the jenkins.model.JenkinsLocationConfiguration.xml file doesn't exist, it seems that something goes horribly wrong during the login.
Broken {{ $ cat hudson.tasks.Mailer.xml @***.com https://***.com/ build@***.com localhost false UTF-8
$ cat jenkins.model.JenkinsLocationConfiguration.xml cat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory }}
Fix 1
{{ $ cat hudson.tasks.Mailer.xml @***.com build@***.com localhost false UTF-8
$ cat jenkins.model.JenkinsLocationConfiguration.xml cat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory }}
Fix 2
{{ $ cat hudson.tasks.Mailer.xml @***.com build@***.com localhost false UTF-8
$ cat jenkins.model.JenkinsLocationConfiguration.xml Build Jenkins http://***.com/ }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [ldap-plugin] (JENKINS-25826) Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box
Title: Message Title
Jason Kulatunga edited a comment on JENKINS-25826
Re: Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box
This was also a huge issue for us. We traced the issue to the Mailer/ext-email plugins, by verifying that a vanilla jenkins install doesn't have this issue, and then individually deleting config files until we found the culprit. We think it has something to do with [https://issues.jenkins-ci.org/browse/JENKINS-20595]If the _hudson.tasks.Mailer.xml_ file exists with a _hudsonUrl_ entry inside, and the _jenkins.model.JenkinsLocationConfiguration.xml_ file doesn't exist, it seems that something goes horribly wrong during the login. *Broken*{{ $ cat hudson.tasks.Mailer.xml @***.com https://***.com/ build@***.com localhost false UTF-8$ cat jenkins.model.JenkinsLocationConfiguration.xmlcat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory }}*Fix 1* Remove the hudsonUrl entry from xml file {{ $ cat hudson.tasks.Mailer.xml @***.com build@***.com localhost false UTF-8$ cat jenkins.model.JenkinsLocationConfiguration.xmlcat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory }}*Fix 2* Using the Jenkins manage ui, save a new Jenkins Url under Jenkins Location section. It will generate a JenkinsLocationConfiguration.xml file. {{ $ cat hudson.tasks.Mailer.xml @***.com https://***.com/ build@***.com localhost false UTF-8$ cat jenkins.model.JenkinsLocationConfiguration.xml Build Jenkins http://***.com/ }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [active-choices-plugin] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Jason Kulatunga updated an issue Jenkins / JENKINS-29407 Active Choices plugin doesn't work with Workflow Plugin Change By: Jason Kulatunga Attachment: configurepage.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-choices-plugin] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Jason Kulatunga updated an issue Jenkins / JENKINS-29407 Active Choices plugin doesn't work with Workflow Plugin Configure page. Change By: Jason Kulatunga Attachment: ScreenShot2015-07-14at9.24.35AM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-choices-plugin] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Jason Kulatunga edited a comment on JENKINS-29407 Re: Active Choices plugin doesn't work with Workflow Plugin Configure I'veaddedanattachmentwiththeissuei'mreferencing.Itsdifferentthanthelinkyouprovided.TheerrorishappeningintheJobconfigure page. !ScreenShot2015-07-14at9.24.35AM.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-choices-plugin] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Jason Kulatunga created an issue Jenkins / JENKINS-29407 Active Choices plugin doesn't work with Workflow Plugin Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 13/Jul/15 10:23 PM Priority: Minor Reporter: Jason Kulatunga When configuring a workflow job and adding a active-choices parameter to the job, the script section is blank/empty. This also seems to happen when the active-choices plugin is used with another plugin that has a groovy script textarea. Add Comment
