[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Jon Brohauge commented on JENKINS-60831 Re: Localisation to non-english is causing a lot of issues, bug and crashes Pascal Laporte Alessandro Dionisi The language issue I fixed is released in 2.217, I see that you are running 2.214 that had the issue, please upgrade to see if the issue still exists. 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.204182.1579617297000.7794.1581500760330%40Atlassian.JIRA.
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title Jon Brohauge edited a comment on JENKINS-60822 Re: can't parse argument number: changelog.url Working on a PR for this issue, using the exact solution provided above. I'm updating all the message_XX.properties files in stead of only _fr_ and _de._Will update this issue when I've got it done. [PR|[https://github.com/jenkinsci/jenkins/pull/4440]] 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.204165.1579519195000.2779.1579529341149%40Atlassian.JIRA.
[JIRA] (JENKINS-60822) can't parse argument number: changelog.url
Title: Message Title Jon Brohauge commented on JENKINS-60822 Re: can't parse argument number: changelog.url Working on a PR for this issue, using the exact solution provided above. I'm updating all the message_XX.properties files in stead of only fr and de. Will update this issue when I've got it done. 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.204165.1579519195000.2776.1579528560651%40Atlassian.JIRA.
[JIRA] (JENKINS-60140) Cannot run program "powershell" when powershell 6.0 core installed
Title: Message Title
Jon Brohauge updated an issue
Jenkins / JENKINS-60140
Cannot run program "powershell" when powershell 6.0 core installed
Change By:
Jon Brohauge
Having installed Powershell 6.0 Core on our linux agents, there is no longer a program called "powershell". It is called "pwsh", and as such anything calling "powershell" will fail.Example:Fails:{code:java}sh('powershell -version'){code}Works:{code:java}sh('pwsh -version'){code}A possible (I haven't tried) workaround is to make a symbolic link between pwsh -> powershell. {code:java}ln -s /usr/bin/pwsh /usr/bin/powershell{code}
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
[JIRA] (JENKINS-60140) Cannot run program "powershell" when powershell 6.0 core installed
Title: Message Title
Jon Brohauge created an issue
Jenkins / JENKINS-60140
Cannot run program "powershell" when powershell 6.0 core installed
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin, powershell-plugin
Created:
2019-11-12 08:23
Environment:
Jenkins: 2.201 Durable Task Plugin: 1.31 Powershell Plugin: 1.3
Priority:
Minor
Reporter:
Jon Brohauge
Having installed Powershell 6.0 Core on our linux agents, there is no longer a program called "powershell". It is called "pwsh", and as such anything calling "powershell" will fail. Example: Fails:
sh('powershell -version')
Works:
sh('pwsh -version')
A possible (I haven't tried) workaround is to make a symbolic link between pwsh -> powershell.
[JIRA] (JENKINS-58121) Use -- for long flags
Title: Message Title Jon Brohauge edited a comment on JENKINS-58121 Re: Use -- for long flags It is considered best practice for shell-based commands to use a single dash followed by a single character, and two dashes followed by a word. One of the reasons being is that using multiple characters after a single dash can be confused for a value after the single character. I.e. `-f file` and `-ffile` can mean the same, som so `-file` can be interpreted as `-f ile`. 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.200166.1561046126000.4745.1561053780168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58121) Use -- for long flags
Title: Message Title Jon Brohauge commented on JENKINS-58121 Re: Use -- for long flags It is considered best practice for shell-based commands to use a single dash followed by a single character, and two dashes followed by a word. One of the reasons being is that using multiple characters after a single dash can be confused for a value after the single character. I.e. `-f file` and `-ffile` can mean the same, som `-file` can be interpreted as `-f ile`. 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.200166.1561046126000.4742.1561053660186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57937) Write a criteria list for steps in release flow
Title: Message Title Jon Brohauge started work on JENKINS-57937 Change By: Jon Brohauge Status: Open In Progress 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.199913.1560169778000.254.1560424620278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57637) Detach the required classes and their descriptors from "hudson.plugins.promoted_builds" package and refactor them for Pipeline Compatibility.
Title: Message Title Jon Brohauge commented on JENKINS-57637 Re: Detach the required classes and their descriptors from "hudson.plugins.promoted_builds" package and refactor them for Pipeline Compatibility. Changed status, due to no acitve work is being done in this particular task. The work is destributed to related issues, since this task i a superset of tasks 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.199567.1558606596000.227.156040235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Jon Brohauge edited a comment on JENKINS-57903 Re: New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Reopening issue due to missing link to PR Status set to _In Progress_ 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.199868.1559891975000.24446.1560170280582%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Jon Brohauge started work on JENKINS-57903 Change By: Jon Brohauge Status: Reopened In Progress 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.199868.1559891975000.2.1560170280551%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Jon Brohauge reopened an issue Reopening issue due to missing link to PR Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Change By: Jon Brohauge Resolution: Fixed Status: Resolved Reopened 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.199868.1559891975000.24441.1560170280517%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57937) Write a criteria list for steps in release flow
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-57937 Write a criteria list for steps in release flow Issue Type: Task Assignee: Jon Brohauge Components: promoted-builds-plugin Created: 2019-06-10 12:29 Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline Priority: Minor Reporter: Jon Brohauge Write up a list of criteria that is needed for a ticket to have a given status. Add Comment
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge edited a comment on JENKINS-57877 Re: PromotionBadge compatibility with pipelines Status should not be resolved prior to merge on the relevant PRStatus set to be _in progress,_ since __ there is no PR, or other solution presented to resolve this ticket. 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.199840.1559812947000.24436.1560169320238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge edited a comment on JENKINS-57877 Re: PromotionBadge compatibility with pipelines Status should not be resolved prior to merge on the relevant PR Status set to be _in progress,_ since __ there is no PR, or other solution presented to resolve this ticket. 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.199840.1559812947000.24434.1560169320196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge started work on JENKINS-57877 Change By: Jon Brohauge Status: Reopened In Progress 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.199840.1559812947000.24430.1560169260212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Jon Brohauge reopened an issue Status should not be resolved prior to merge on the relevant PR Jenkins / JENKINS-57877 PromotionBadge compatibility with pipelines Change By: Jon Brohauge Resolution: Fixed Status: Resolved Reopened 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.199840.1559812947000.24427.1560169200344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53575) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge closed an issue as Fixed Jenkins / JENKINS-53575 Configuration-as-Code compatibility Change By: Jon Brohauge 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.194055.1536917624000.18764.1559560740807%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53576) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge closed an issue as Fixed Jenkins / JENKINS-53576 Configuration-as-Code compatibility Change By: Jon Brohauge 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.194056.1536917945000.18762.1559560740784%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Jon Brohauge commented on JENKINS-57672 Re: Determine Dependencies between PluginManager.java on Jenkins Core In the essence of loosely coupled components playing nicely together, I personally would like it to be a separate component, but I fear that might be too big at task within the given timeframe. 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.199605.1558721108000.17199.1559288700149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57688) Make promotion job triggerable using parameterized-trigger concept.
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57688 Make promotion job triggerable using parameterized-trigger concept. Change By: Jon Brohauge Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline 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.199623.1558882486000.13416.1559035021595%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57689) Use run-selector/CopyArtifacts plugin to pass parameters/build description to the promotion job
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57689 Use run-selector/CopyArtifacts plugin to pass parameters/build description to the promotion job Change By: Jon Brohauge Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline 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.199624.155888260.13418.1559035022073%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57687) Create new custom steps to be included in the declarative pipeline for promotion description.
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57687 Create new custom steps to be included in the declarative pipeline for promotion description. Change By: Jon Brohauge Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline 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.199622.1558882281000.13414.1559034960122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Jon Brohauge Labels: gsoc-2019 gsoc-2019-artifact-promotion-pipeline-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.199564.1558605601000.13412.1559034720230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57637) Detach the existing extensions,implementations,conditions,etc and refactor them for pipeline compatibility.
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57637 Detach the existing extensions,implementations,conditions,etc and refactor them for pipeline compatibility. Change By: Jon Brohauge Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline 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.199567.1558606596000.13410.1559034660109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Jon Brohauge Labels: gsoc-2019 gsoc-2019-artifact-promotion-pipeline-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.199564.1558605601000.13408.1559034480180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57643) Support for projectName + projectVersion instead of projectId upon synchronous:true
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57643 Support for projectName + projectVersion instead of projectId upon synchronous:true Change By: Jon Brohauge Summary: Support for projectName + projectVersion instead of projectId upon sunchronized= synchronous: true 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.199574.1558617849000.10105.1558618140121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57643) Support for projectName + projectVersion instead of projectId upon sunchronized=true
Title: Message Title
Jon Brohauge created an issue
Jenkins / JENKINS-57643
Support for projectName + projectVersion instead of projectId upon sunchronized=true
Issue Type:
Improvement
Assignee:
Steve Springett
Components:
dependency-track-plugin
Created:
2019-05-23 13:24
Priority:
Minor
Reporter:
Jon Brohauge
Having the projectId obligatory when using this plugin while having synchronous: true, is an issue for automatically created pipelines. Most of the developers that are going to use this tool, know nothing of the projectId, but obviously knows their projectName and projectVersion. Since the plugin can communicate fine with a Dependency-Track server only using projectName and projectVersion for non-synchronous configuration, it should also be doable with a synchronous configuration. Executing the following pipeline step:
dependencyTrackPublisher projectId: "[projectId]", projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: true
works. Executing the following pipeline step:
dependencyTrackPublisher projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: true
does not work. Executing the following pipeline step:
[JIRA] (JENKINS-57640) Support for Configuration as Code
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-57640 Support for Configuration as Code Change By: Jon Brohauge Component/s: dependency-track-plugin Component/s: dependency-check-jenkins-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.199570.1558613883000.9988.155861490%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57640) Support for Configuration as Code
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-57640 Support for Configuration as Code Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-05-23 12:18 Labels: jcasc-compatibility Priority: Minor Reporter: Jon Brohauge Being able to set the global properties using the CasC plugin would be fantastic. This allows for setting the properties programatically and having the values under source control. Add Comment
[JIRA] (JENKINS-56774) Support Configuration as Code
Title: Message Title Jon Brohauge commented on JENKINS-56774 Re: Support Configuration as Code It works, yes. Still would be nice if it was 100% compatible, i.e. the plugin works during the export. 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-56774) Support Configuration as Code
Title: Message Title Jon Brohauge commented on JENKINS-56774 Re: Support Configuration as Code Jenkins works when using this configuration: --- security: queueItemAuthenticator: authenticators: - global: strategy: systemAuthorizationStrategy Using the exporting the jenkins.yaml, I get an exception: security: queueItemAuthenticator: authenticators: - global: strategy: "FAILED TO EXPORT org.jenkinsci.plugins.authorizeproject.GlobalQueueItemAuthenticator#strategy:\ \ \njava.lang.NullPointerException\n\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$describe$4(HeteroDescribableConfigurator.java:99)\n\ \tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$describe$6(HeteroDescribableConfigurator.java:103)\n\ \tat io.vavr.control.Option.map(Option.java:373)\n\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:102)\n\ \tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:50)\n\ \tat io.jenkins.plugins.casc.Attribute.describe(Attribute.java:195)\n\t\ at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:255)\n\ \tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$convertToNode$de0cd4f8$1(HeteroDescribableConfigurator.java:230)\n\ \tat io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201)\n\ \tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.convertToNode(HeteroDescribableConfigurator.java:230)\n\ \tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$describe$5(HeteroDescribableConfigurator.java:101)\n\ \tat io.vavr.control.Option.map(Option.java:373)\n\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:101)\n\ \tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:50)\n\ \tat io.jenkins.plugins.casc.Attribute.describe(Attribute.java:191)\n\t\ at io.jenkins.plugins.casc.Configurator.describe(Configurator.java:162)\n\ \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:107)\n\ \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.lambda$describe$5(GlobalConfigurationCategoryConfigurator.java:100)\n\ \tat java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)\n\ \tat java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)\n\ \tat java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)\n\ \tat java.util.Iterator.forEachRemaining(Iterator.java:116)\n\tat java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)\n\
[JIRA] (JENKINS-53931) Role Strategy: Configuration-as-Code compatibility
Title: Message Title Jon Brohauge commented on JENKINS-53931 Re: Role Strategy: Configuration-as-Code compatibility An Nguyen You could fork the project and introduce the fix in a PR. Afterwards ask the maintainer to review the PR. 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-56774) Support Configuration as Code
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-56774 Support Configuration as Code Change By: Jon Brohauge Labels: configuration jcasc - as-code compatibility 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-56774) Support Configuration as Code
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-56774 Support Configuration as Code Issue Type: Improvement Assignee: Unassigned Components: authorize-project-plugin Created: 2019-03-27 09:55 Labels: configuration-as-code Priority: Minor Reporter: Jon Brohauge This plugin should support setting properties via JCasC, i.e. Configuration-as-Code plugin. Add Comment
[JIRA] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Jon Brohauge commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 We usually don't do upgrades. By leveraging Docker, and JCasC, we rebuild from scratch, every time we need a new version Jenkins or a plugin. Having no state inside Jenkins, we can treat the containers as cattle. If it gets sick, here comes the bolt-pistol. As mentioned in my previous comment comment-343088, we fixed our issue by entering the SSH key "directly" and setting the proper scope. 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-53864) CasC compatibility with Log Parser Plugin
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-53864 CasC compatibility with Log Parser Plugin Change By: Jon Brohauge Comment: PR to get plugin to be JCASC compatible 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-53864) CasC compatibility with Log Parser Plugin
Title: Message Title Jon Brohauge commented on JENKINS-53864 Re: CasC compatibility with Log Parser Plugin PR to get plugin to be JCASC compatible 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-53864) CasC compatibility with Log Parser Plugin
Title: Message Title Jon Brohauge edited a comment on JENKINS-53864 Re: CasC compatibility with Log Parser Plugin [Pull Request|https://github.com/jenkinsci/log-parser-plugin/pull/24] to make the plugin JCASC compatible 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-53864) CasC compatibility with Log Parser Plugin
Title: Message Title Jon Brohauge commented on JENKINS-53864 Re: CasC compatibility with Log Parser Plugin Pull Request 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-53576) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge commented on JENKINS-53576 Re: Configuration-as-Code compatibility I can see that the PR in GitHub has been merged. Is there a set release date for the updated 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53931) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-53931 Configuration-as-Code compatibility Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2018-10-07 15:27 Labels: jcasc-compatibility Priority: Minor Reporter: Jon Brohauge Configuration-as-Code is the (proposed) mechanism to configure jenkins master automatically from plain text recipes. It relies on component internal model auto-discovery, and as such assume plugins do follow best practices for UI data-binding and internal design. Updating this component to allow for direct interaction is requested. There is a current work-around in the Configuration-as-Code-Support plugin, which would be appreciated if it got incorporated into this plugin. The bits pertaining this specific plugin, can be found here Add Comment
[JIRA] (JENKINS-53576) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge commented on JENKINS-53576 Re: Configuration-as-Code compatibility Proposed fix: https://github.com/jenkinsci/active-directory-plugin/pull/86 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-53576) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-53576 Configuration-as-Code compatibility Change By: Jon Brohauge Summary: Compatability issues with JCASC Configuration-as-Code compatibility 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-53575) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge updated an issue Jenkins / JENKINS-53575 Configuration-as-Code compatibility Change By: Jon Brohauge Summary: Compatability issues with JCASC Configuration-as-Code compatibility 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-53576) Compatability issues with JCASC
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-53576 Compatability issues with JCASC Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2018-09-14 09:39 Labels: jcasc-compatibility Priority: Minor Reporter: Jon Brohauge Configuration-as-Code is the (proposed) mechanism to configure jenkins master automatically from plain text recipes. It relies on component internal model auto-discovery, and as such assume plugins do follow best practices for UI data-binding and internal design. Using the export feature to generate a configuration yaml-file it's partially supported, but significant configuration attributes don't follow expected design. as a resume manual JSON parsing vs data-binding no setters for databound configuration elements optional block vs optional property Part of the experienced Exception: "FAILED TO EXPORT hudson.model.Hudson#securityRealm: \nio.jenkins.plugins.casc.ConfiguratorException:\ \ Can't read attribute 'customDomain' from hudson.plugins.active_directory.ActiveDirectorySecurityRealm@1009dfeb\n\ \tat io.jenkins.plugins.casc.Attribute._getValue(Attribute.java:246)\n\tat io.jenkins.plugins.casc.Attribute.getValue(Attribute.java:166)\n\ \tat
[JIRA] (JENKINS-53575) Compatability issues with JCASC
Title: Message Title Jon Brohauge created an issue Jenkins / JENKINS-53575 Compatability issues with JCASC Issue Type: Improvement Assignee: Stefan Wolf Components: gradle-plugin Created: 2018-09-14 09:33 Environment: Labels: jcasc-compatibility Priority: Minor Reporter: Jon Brohauge Configuration-as-Code is the (proposed) mechanism to configure jenkins master automatically from plain text recipes. It relies on component internal model auto-discovery, and as such assume plugins do follow best practices for UI data-binding and internal design. Using the export feature to generate a configuration yaml-file it's partially supported, but significant configuration attributes don't follow expected design. as a resume manual JSON parsing vs data-binding no setters for databound configuration elements optional block vs optional property Part of the experienced Exception: "FAILED TO EXPORT hudson.plugins.gradle.GradleInstallation$DescriptorImpl\ \ : \nio.jenkins.plugins.casc.ConfiguratorException: Can't read attribute 'installations'\ \ from
