[JIRA] (JENKINS-52497) Jenkins cannot build with error - groovy
Title: Message Title Bruno P. Kinoshita closed an issue as Cannot Reproduce Jenkins / JENKINS-52497 Jenkins cannot build with error - groovy Change By: Bruno P. Kinoshita Status: Open Closed Resolution: Cannot Reproduce 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.192328.1531333815000.24559.1589185440515%40Atlassian.JIRA.
[JIRA] (JENKINS-61243) Artifactory plugin to fail active-choice plugin
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61243 Artifactory plugin to fail active-choice plugin Change By: Bruno P. Kinoshita Summary: Artifactory plugin to fall fail active-choice plugin 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.204800.1582736596000.24561.1589185440572%40Atlassian.JIRA.
[JIRA] (JENKINS-52497) Jenkins cannot build with error - groovy
Title: Message Title Bruno P. Kinoshita commented on JENKINS-52497 Re: Jenkins cannot build with error - groovy Hi Tomas Pavelka I'm closing as I cannot reproduce this. Feel free to re-open if you can either provide us with a way to reproduce, or if you have an environment that can be used for troubleshooting. Bruno 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.192328.1531333815000.24553.1589185380158%40Atlassian.JIRA.
[JIRA] (JENKINS-62215) antisamy-markup-formatter-plugin v2.0 filters input fields from uno-choice plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-62215 Re: antisamy-markup-formatter-plugin v2.0 filters input fields from uno-choice plugin Thanks for the report and for the taking your time to provide detailed description and screenshots. We were preparing a release for the next days (waiting till pending pull request gets reviewed/tested by other maintainers). I will try to include some time to take a look and try to reproduce/fix this one. Bruno 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.206149.159205000.23530.1588917840195%40Atlassian.JIRA.
[JIRA] (JENKINS-62145) Getting error when clicking on testlink results 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult
Title: Message Title Bruno P. Kinoshita commented on JENKINS-62145 Re: Getting error when clicking on testlink results 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult Hi Empower Solutions No updates from me, sorry. The project is maintained by volunteers. I haven't had time to look into the issue yet. If it's urgent for you, you can reach out to CloudBees. They provide paid support. If you have a pull request, I can review and prepare a release quite quickly. Otherwise I will prioritize it in the next development cycle (busy with $work, GSoC, Apache, and family for the next weeks) Bruno 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.206064.1588413622000.23528.1588917720218%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61751 let :disabled and :deleted at the same time Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi 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.205582.1585633679000.21413.1588636920758%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61751 let :disabled and :deleted at the same time Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi 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.205582.1585633679000.21414.1588636920845%40Atlassian.JIRA.
[JIRA] (JENKINS-53540) Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
Title: Message Title Bruno P. Kinoshita commented on JENKINS-53540 Re: Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter Not sure if that will work well with pipelines Meghana V, the plug-in is not developed with pipelines in mind (though it may work). It's designed for the HTML DOM of Jenkins UI, which can act different when using pipelines. 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.194016.1536789673000.8788.1586472660239%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61751 let :disabled and :deleted at the same time Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi 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.205582.1585633679000.3786.1585686600123%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita started work on JENKINS-61751 Change By: Bruno P. Kinoshita Status: Open In Progress 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.205582.1585633679000.3434.1585636740084%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-61751 let :disabled and :deleted at the same time Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-03-31 05:47 Priority: Minor Reporter: Bruno P. Kinoshita Placeholder for https://github.com/jenkinsci/active-choices-plugin/pull/33/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Merged and added to the changelog for the next release. Thanks a lot Adam Gabryś! 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.204555.1581528008000.6785.1582689480092%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi 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.204555.1581528008000.6781.1582689420254%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Ioannis Moutsatsos, attached the plugin hpi file for testing: uno-choice.hpi 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.204555.1581528008000.6783.1582689420279%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita updated JENKINS-61068 Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed 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.204555.1581528008000.6779.158260275%40Atlassian.JIRA.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library I agree, and really would like to implement it. But first would need to find either some good guidelines to avoid security issues later, or have a good amount of time to investigate possible solutions. The risk with this feature is that the plugin would be blacklisted (again) due to security issues in the implementation. 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.184658.1503497167000.9084.1581626042397%40Atlassian.JIRA.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library If anyone knows of a plugin doing something similar, that'd be helpful. Pull requests welcome as well 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.184658.1503497167000.9086.1581626042429%40Atlassian.JIRA.
[JIRA] (JENKINS-61021) Performance issue in active-choices plugin at commit 372d91b
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-61021 Performance issue in active-choices plugin at commit 372d91b Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-02-08 07:51 Priority: Major Reporter: Bruno P. Kinoshita Reported via the mailing list in Google (though I think it was a direct e-mail to list owners) The change to the active choices plugin at commit 372d91b is causing problems and we cannot use the latest versions of the plugin without reverting this commit and building on our own. The problem is strange. But, is appears to be mostly a performance issue. With this change, we are seeing '504 gateway error' failures because of connection timeouts. It is somehow related to the artifactory plugin, because the jenkins log file contains multiple occurrences per second of the following log message. (omitting message as it's not related to the performance issue) Add Comment
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Bruno P. Kinoshita commented on JENKINS-60319 Re: Reactive Parameter ignores toString Just a quick update. I debugged this issue over the weekend, but couldn't understand why it was happening. Reproducing was quite simple, thanks to the example provided in the issue description. Will have another go next time I have some spare time. 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.203316.1574954163000.9887.1575253080131%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Bruno P. Kinoshita commented on JENKINS-60319 Re: Reactive Parameter ignores toString Oh, interesting problem. Thanks for reporting. I'll need to debug to understand what's going on. Might have time this coming Sunday (NZ time). 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.203316.1574954163000.9205.1574989500397%40Atlassian.JIRA.
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46592 Re: Issue with Graph Plugin Available in the experimental update center, as 2.0-alpha-1. In order to release the plug-in, had to update the version of Jenkins it it built against. That resulted in new Findbugs issues. Fixing some of these errors, I realized I am not too sure about backward compatibility now. So bumped up the version to 2.0, and did a bit more of cleaning, like removing deprecated methods and fields. I will release the 2.0 version of the plugin by the next weekend if there are no issues reported for this alpha release. Thanks! Bruno 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.184922.1504289511000.6898.1574757000487%40Atlassian.JIRA.
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46592 Re: Issue with Graph Plugin Connection timedout uploading the pom (looks like the hpi went through). Will have more time tonight to try the release of 1.5 again. 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.184922.1504289511000.6665.1574729760201%40Atlassian.JIRA.
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46592 Re: Issue with Graph Plugin Sure thing Scott Logan. Releasing now, unless something goes wrong with the Maven process, it should be available in the next hours. 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.184922.1504289511000.6628.1574728140175%40Atlassian.JIRA.
[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita updated JENKINS-46592 Jenkins / JENKINS-46592 Issue with Graph Plugin Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed 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.184922.1504289511000.6623.1574728081362%40Atlassian.JIRA.
[JIRA] (JENKINS-59881) org.tap4j.parser.ParserException: Error parsing TAP Stream: Duplicated TAP Plan found.
Title: Message Title Bruno P. Kinoshita commented on JENKINS-59881 Re: org.tap4j.parser.ParserException: Error parsing TAP Stream: Duplicated TAP Plan found. Emmanuel Andre I haven't updated instanttap in a while, so it may be validating for an earlier version of tap4j. Unfortunately I don't have much bandwidth for tap-plugin at the moment. Will update the issue later once I have time to look into it with calm. Thanks for the good description and comment about which version you downgraded and fixed it. That will help troubleshooting it. If you have a pull request, feel free to ping me as it takes normally only a few minutes for me to review PR's, so I can find some spare time for that. Cheers Bruno 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.202626.1571743721000.847.1571984640269%40Atlassian.JIRA.
[JIRA] (JENKINS-52454) Testlink integration
Title: Message Title Bruno P. Kinoshita commented on JENKINS-52454 Re: Testlink integration Hi Clemens Gmeiner, Closed the issue as Not A Defect. Turns out this feature was implemented long time ago. Took me a moment to find it in the code, and a bit longer to test it. 1. Added a node to Jenkins called "localhost" using the slave.jar 2. Added a fake TestLink installation in global configuration 3. Created a job in Jenkins and for platform name, used "$NODE_NAME" We are "expanding" (i.e. converting $NODE_NAME to whatever value is bound in Jenkins environment) the following environment variables in the plugin: project name test plan name platform name build name build notes See here for code: https://github.com/jenkinsci/testlink-plugin/blob/1235c466a7b460c39f4fba46051082c1d9c214ff/src/main/java/hudson/plugins/testlink/TestLinkBuilder.java#L189-L197 Which means, when you configure these variables in a Jenkins job for the plugin, you can use any of the variables available in Jenkins. So any of this list: https://wiki.jenkins.io/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-belowJenkinsSetEnvironmentVariables Or any variable defined in plugins that increments this list. Few screenshots of a quick test with a debugger in Eclipse.In case I missed something, or it doesn't really solves the issue described here, feel free to point out what is missing and re-open this issue. Cheers Bruno Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-52454) Testlink integration
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-52454 Testlink integration Change By: Bruno P. Kinoshita Attachment: Screenshot_2019-09-28_20-01-40.png Attachment: Screenshot_2019-09-28_20-02-21.png Attachment: Screenshot_2019-09-28_20-02-58.png 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.192281.1531227423000.7076.1569658320207%40Atlassian.JIRA.
[JIRA] (JENKINS-52454) Testlink integration
Title: Message Title Bruno P. Kinoshita updated JENKINS-52454 Jenkins / JENKINS-52454 Testlink integration Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Not A Defect 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.192281.1531227423000.7074.1569657960288%40Atlassian.JIRA.
[JIRA] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-29407 Re: Active Choices plugin doesn't work with Workflow Plugin Hi , once released the issue will be marked as closed or fixed here. I have no bandwidth to work on this right now, but happy to review/merge pull requests. Bruno 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.163874.1436826209000.4060.1569320220444%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Bruno P. Kinoshita commented on JENKINS-59381 Re: OWASP Plugin 1.6 crashed Jenkins I haven't tested with the scenario described here. The exception looks the same users got in active choices when upgrading to 2.2. Released 2.2.1 last night (New Zealand time) with a tentative fix. One user reported it worked so far. 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.201937.1568575654000.4601.1568662020211%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Bruno P. Kinoshita commented on JENKINS-59389 Re: Active choices plugin causes Jenkins to crash on startup Syncing should happen in some minutes. Then force Jenkins to refresh info from update center. 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.201945.1568634852000.4245.1568636700255%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Bruno P. Kinoshita commented on JENKINS-59389 Re: Active choices plugin causes Jenkins to crash on startup Thanks for reporting it. Can you try 2.2.1 please? Cheers Bruno 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.201945.1568634852000.4233.1568636460115%40Atlassian.JIRA.
[JIRA] (JENKINS-59381) OWASP Plugin 1.6 crashed Jenkins
Title: Message Title Bruno P. Kinoshita commented on JENKINS-59381 Re: OWASP Plugin 1.6 crashed Jenkins Hi, sorry for the update that broke it. It appears we made scriptler a non-optional dependency. Will try to get a fix in this week and cut a new release. 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.201937.1568575654000.4087.1568628420188%40Atlassian.JIRA.
[JIRA] (JENKINS-28734) Maintain Active Choices selections between filter applications
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28734 Re: Maintain Active Choices selections between filter applications We must also consider the two closed duplicated tickets. In one of them (51054) it appears that a simpler approach would be enough to fix the use case of the user. One where we do not clear the selections. However, not sure what happens if we have items A, B[selected], C[seleted] in the first state. Then the user changes another parameter and then the items displayed are now only A, C[selected]... not sure if the user would still want B[selected] if B is displayed again, or if it would be in a reset/clear state. If the latter, that's much easier. Also, we could suggest the simplest solution (not clearing selections), instead of maintaining the full state of selections between states (much harder, with more risk of bugs). For later, as this will probably need at least a minor version release. Next release will be probably patch/bugs. 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.163185.1433385727000.15.1560386160129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51054) Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter
Title: Message Title Bruno P. Kinoshita updated JENKINS-51054 Jenkins / JENKINS-51054 Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Duplicate 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.190295.1525169847000.12.1560385980351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Title: Message Title Bruno P. Kinoshita updated JENKINS-50837 Jenkins / JENKINS-50837 [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3 Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Duplicate 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.189951.1523953451000.8.1560385920974%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Title: Message Title Bruno P. Kinoshita commented on JENKINS-50837 Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3 No updates from me. I'm currently overseas for a conference, back in July, will have some time with family before returning to $work. Then once I have time to work on Open Source will triage issues here to see what can be fixed and included in the next release. Closing this and the other duplicate issues, as there is an older issue for this already. Multiple issues make it harder to triage things and can be confusing to users too. This is not too complicated to fix, but requires a lot of patience and time, as it would require creating a state layer in _javascript_, with some sort of Stack/State, and link it with the choices selected... this can lead to multiple issues with different browsers, or different parameter types. Pull requests welcome! Always happy to review contributions by others and include in a future release. If there is urgency in this issue, please consider also hiring professional services, as there is a number of companies that offer Jenkins development (e.g. CloudBees, Praqma, most IT shops, and several Jenkins plugin maintainers), as most of the work here is maintained as Open Source volunteer work. 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.189951.1523953451000.6.1560385920929%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52454) Testlink integration
Title: Message Title Bruno P. Kinoshita commented on JENKINS-52454 Re: Testlink integration Otherwise, if you are in no hurry, it is really not a very complex issue. It would just need to wait until I have time to work on this one (probably near December, unless I have some other project that needs work). I think I also need to update the testlink-java-api for 1.9.19, and was planning on doing that after November, which normally includes going through pending issues. 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.192281.1531227423000.9593.1558564740328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52454) Testlink integration
Title: Message Title Bruno P. Kinoshita commented on JENKINS-52454 Re: Testlink integration Hi Clemens Gmeiner feel free to contact me off-list if you would like to sponsor this issue. Cheers Bruno 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.192281.1531227423000.9591.1558564620246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Bruno P. Kinoshita assigned an issue to Unassigned Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Bruno P. Kinoshita Assignee: Bruno P. Kinoshita 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.197855.155115906.2705.1557973020233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Bruno P. Kinoshita edited a comment on JENKINS-38893 Re: Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Ok, I think I finally understood the issue and what's going on. What we have when we use Jenkins' File parameter is a [FileParameterValue|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/FileParameterValue.java].The Jelly [file used to render|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/FileParameterDefinition/config.jelly] is very simple and it seems like the part we are missing here is that the input field's name must be "file", not "value".If you want to cascade to other parameters, I think you will have to find some _javascript_ that reacts to the event when the user chooses the file, then copies the file name in another input name="value".So in summary, the only thing I changed from your example to get it working was: To match Jenkins' jelly file.Could you check if that works for you [~ioannis], please? Here's a screen shot (also checked in the disk, and both files were uploaded , but no file name in the latter ). !screenshot-1.png|thumbnail! 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-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Bruno P. Kinoshita commented on JENKINS-38893 Re: Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Ok, I think I finally understood the issue and what's going on. What we have when we use Jenkins' File parameter is a FileParameterValue. The Jelly file used to render is very simple and it seems like the part we are missing here is that the input field's name must be "file", not "value". If you want to cascade to other parameters, I think you will have to find some _javascript_ that reacts to the event when the user chooses the file, then copies the file name in another input name="value". So in summary, the only thing I changed from your example to get it working was: To match Jenkins' jelly file. Could you check if that works for you Ioannis Moutsatsos, please? Here's a screen shot (also checked in the disk, and both files were uploaded). 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-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-38893 Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Change By: Bruno P. Kinoshita Attachment: screenshot-1.png 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-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Bruno P. Kinoshita commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Oh, sorry Madhavi Katreddy. So I think we can ignore the screenshot. Could you provide some more info like Jenkins and active-choice-plugins versions (as well as any plugin relevant if used in this job). We would also need some way to replicate the issue. You mentioned a database, but it would probably take me a little while to work on this issue if I needed to set up a DB server/container/etc to replicate it. Does the issue happen if you execute a normal list that is retrieved via a Groovy script, but that is not going to the database? If the answer is no, then we will probably need to consider the possibility of a bug in the Groovy script that is calling the DB... Hope that makes sense. Ioannis and I triaged some issues a couple of weeks ago, and I am currently working through the current backlog. If it is easy to replicate and understand what's going on, I can try to include this issue in the next release. Otherwise we will have a look and try to include in the next one Cheers Bruno 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-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Bruno P. Kinoshita edited a comment on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Oh, sorry [~madhavi_katreddy]. So I think we can ignore the screenshot.Could you provide some more info like Jenkins and active-choice-plugins versions (as well as any plugin relevant if used in this job). We would also need some way to replicate the issue.You mentioned a database, but it would probably take me a little while to work on this issue if I needed to set up a DB server/container/etc to replicate it. Does the issue happen if you execute a normal list that is retrieved via a Groovy script, but that is not going to the database? If the answer is no, then we will probably need to consider the possibility of a bug in the Groovy script that is calling the DB...Hope that makes sense. Ioannis [~ioannis] and I triaged some issues a couple of weeks ago, and I am currently working through the current backlog. If it is easy to replicate and understand what's going on, I can try to include this issue in the next release.Otherwise we will have a look and try to include in the next one (y)CheersBruno 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-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Bruno P. Kinoshita commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Oh, and you won't see that variable persisted in any XML. The plug-in creates that variable in the Groovy runtime context. So it should work as long as you use it for a Groovy script in an Active Choices parameter. 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-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Bruno P. Kinoshita commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Hi Madhavi Katreddy, thanks for bumping this issue. I hadn't seen it before (or just cannot remember seeing it, sorry anyway). The projectName variable is volatile, and may disappear after the project is renamed, or even if there is some other plugin fiddling with the XML. The plug-in, however, tries to workaround this by providing the jenkinsProject variable, which contains the jenkinsProject.name attribute. That jenkinsProject variable tries to use the projectName, but has a fallback mechanism to load the project info programmatically. Not perfect, but if you could try, this could be a workdaround for the time being. Cheers Bruno 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-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Ioannis Moutsatsos now I noticed, you were using the `projectName` property of the parameter. That is a helper variable, used when the project is created via its constructor. But if it is loaded via serializer/Stapler/etc, then I am not sure if the constructor will always be called. There is a logic that tries to use that variable, but when it is not found, we fallback to locating a project with a parameter UUID (every active choices has a random UUID). However, we do not save the project to `projectName`. For the current implementation - which is a bit complex, and may need to improvements - the best way to access the Jenkins project is via the variable `jenkinsProject`, that the plugin populates automatically. Tried with a groovy script that returned `return [jenkinsProject.name]`, and it worked before & after renaming the project. Hope that makes sense? 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-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Bruno P. Kinoshita updated JENKINS-53356 Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Change By: Bruno P. Kinoshita Status: Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Bruno P. Kinoshita commented on JENKINS-53356 Re: Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Fixed! Think so at least 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-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Change By: Bruno P. Kinoshita Attachment: Screenshot from 2019-03-02 20-03-03.png Attachment: Screenshot from 2019-03-02 20-36-24.png 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-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Bruno P. Kinoshita commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Hi Saheta B, thanks for reporting the issue. I am working on other issues at the moment. Even though your issue has a good title, and you set the priority to Critical, this bug may very well be ignored during the next triage. The reason for that is that you are not providing enough information. You need to imagine yourself as a developer trying to fix it. Then ask yourself could it be a problem with the previous version the user had installed? Maybe he didn't upgrade from the latest to 2.150.3. Could it be another plug-in? What are the exact steps that I need to perform to reproduce? Would a screenshot help? Would a config.xml help? etc etc. So if you logged a Minor priority bug, but with good information for troubleshooting, that could have more chances of being quickly fixed then the other way. 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-41709) Blue Ocean doesnt render Active Choices parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-41709 Re: Blue Ocean doesnt render Active Choices parameters Hi Omit Rathore. Increasing the priority won't have any effect for me. We (mainly Ioannis and myself) triage the issues, looking for bugs and things that we need for our environments or that are missing from the plug-in. We have already triaged a few bugs for the next development cycle. But given that Ioannis and myself are not using Blue Ocean, we wouldn't know how to start working to add support to it. A pull request or some work that work ease the work for somebody else to create a pull request would better IMO. 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-55787) Switch labels from entry to checkbox
Title: Message Title Bruno P. Kinoshita updated JENKINS-55787 Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Bruno P. Kinoshita Resolution: Fixed Status: Resolved In 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Bruno P. Kinoshita commented on JENKINS-55787 Re: Switch labels from entry to checkbox Sorry Josh Soref! I am so used to add the link to the release notes in the Wiki, move to released, and close... then after a few minutes I realized it was not a tap-plugin issue, nor assigned to me. I apologize. Re-opened. 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-55787) Switch labels from entry to checkbox
Title: Message Title Bruno P. Kinoshita updated JENKINS-55787 Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Bruno P. Kinoshita 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-55787) Switch labels from entry to checkbox
Title: Message Title Bruno P. Kinoshita updated JENKINS-55787 Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Bruno P. Kinoshita Status: Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Bruno P. Kinoshita updated JENKINS-55787 Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Bruno P. Kinoshita Status: Reopened Open 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-48488) Request to make Testcase version available in Jenkins Build environment
Title: Message Title Bruno P. Kinoshita updated JENKINS-48488 Just released 3.16 with the change. Also updated the plugin Wiki. Thanks! Jenkins / JENKINS-48488 Request to make Testcase version available in Jenkins Build environment Change By: Bruno P. Kinoshita 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-48488) Request to make Testcase version available in Jenkins Build environment
Title: Message Title Bruno P. Kinoshita updated JENKINS-48488 PR merged. Release pending, but will do it in some 7/8 hours. Jenkins / JENKINS-48488 Request to make Testcase version available in Jenkins Build environment Change By: Bruno P. Kinoshita Status: Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48488) Request to make Testcase version available in Jenkins Build environment
Title: Message Title Bruno P. Kinoshita commented on JENKINS-48488 Re: Request to make Testcase version available in Jenkins Build environment Hadn't seen that one Achim Zimmer! Sorry. Merged, will release it tonight. 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-41709) Blue Ocean doesnt render Active Choices parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-41709 Re: Blue Ocean doesnt render Active Choices parameters Thanks Torben Knerr! Alas I'm still not using Blue Ocean, and no plans to use it yet. Unfortunately I have other issues for Open Source projects, plus $work. So no plans to work on it yet. Hopefully a pull request will come from someone else! If that happens, promise I will try to test it and release asap. Cheers Bruno 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita updated JENKINS-42632 Jenkins / JENKINS-42632 CCM Plugin Not Creating Trend Graph Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Won't 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Thanks Alex Gray! I've upgraded the plugin README copying what checkstyle-plugin did. 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Oh, actually, looks like they support CCM too. Would you be willing to give it a try on your Windows computer. If that works, I will update CCM README and Wiki, asking users to use the Warnings NG instead. 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Did a bit of socializing, but I do enjoy a quiet corner and a book, or hotel room with good Internet connection and some project to work on Alex, I had a look at the bug and it is indeed quite easy to reproduce with your XML. From what I remember, we were using the analysis plugin... but looks like... it's no more? Looks like there's a new warnings plugin. And they suggest for others to write a groovy parser... which would be simple to do for CCM. But if that works well, this plugin would probably be deprecated in favour of this new warnings plugin. Does that make sense to you? I'll see when I have time to continue investigating this new plugin (haven't used Jenkins in a while, sorry) 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Never got the time to actually work on CCM Plugin since my last comment. But am currently in a conference, with some hotel time. Would you have - or be able to produce - a CCM file that I could use, please Alex Gray? I am on Linux, without CCM. But having an XML I can at least force the plugin to read it, even on Linux (if I remember well, I did that in the past while developing it). If it is something simple, it might be doable to release a version by the end of this week (once conference is over). Cheers Bruno 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-46394) active choices reactive parameter cant load shared library
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library Looks like this is something useful for users. Next development cycle will start looking into ways other plugins are using to support that. I really want to avoid the plugin being blacklisted again due to security issues/CVE's. So my plain is 1. learn how other plugins are working 2. create a branch with the solution 3. upload here a .hpi file with the proposed solution, and also try to release to the experimental update site (not sure if that still exists) 4. release only, and really only, if there's enough testing from users that also took into consideration possible attack vectors created by this feature (i.e. giving some thought to what issues this feature could cause... do they have a security permission model that could allow users to use dangerous libraries? did we implement in a way that the administrator him/herself could shoot his own foot and accidentally introduce a security problem in their jenkins/etc) And once we pass step 4, and we are confident this won't introduce a security bug, cut a release. Let me know if anyone has any other suggestions, or if interested in helping with the testing/development. Cheers Bruno 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-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title Bruno P. Kinoshita commented on JENKINS-49894 Re: Active Choices Reactive Reference Parameter triggering the groovy script twice Have just spent some minutes debugging it, and I believe I now understand what's causing the issue. Can't fix it right now due to limited bandwidth to develop, but the below is a short explanation of the problem (and also a note to myself in the future, when working on this issue again). I only reproduced it on the first time the page is loaded. Debugging, it is possible to see the first call comes from Jelly tags being evaluated. And the second call comes from _javascript_ code. The issue appears to be that when we put the elements on the UI, we also intentionally call the update method on the server side, to get the right values. Then once everything is loaded, there is a JS call to refresh the elements' values. The ideal approach would be to have Jelly creating the elements, then using JS to start the execution. But that's not easy to implement without breaking other things. 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-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title
Bruno P. Kinoshita updated an issue
Jenkins / JENKINS-49894
Active Choices Reactive Reference Parameter triggering the groovy script twice
Change By:
Bruno P. Kinoshita
I am trying to fetch a list of branches from git in the active choice reactive reference parameter.I am using the run *groovy script* option.But the script is ran twice when I check the tomcat logs.Because of which the drop down is rendered twice.Please find the below script{code: java groovy }def html= ''' Select... ''' def cmd = ["/bin/bash", "-c","sudo sh /home/centos/JenkinScripts/dynamicChoices/getBranchesFromGit.sh https://kgjenk...@bitbucket.org/vtakru/escloudadmin.git"] def sout = new StringBuffer() def serr = new StringBuffer() // Run the command println "running "+cmd def proc = cmd.execute() proc.consumeProcessOutput ( sout, serr ) proc.waitFor() def options="" sout.tokenize().each{ branch-> if(branch.contains("refs/heads/")){ branch=branch.minus("refs/heads/") println "Branch "+branch options+="$branch" } } html+=options return html{code} Please help me with 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
[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title
Bruno P. Kinoshita updated an issue
Jenkins / JENKINS-49894
Active Choices Reactive Reference Parameter triggering the groovy script twice
Change By:
Bruno P. Kinoshita
I am trying to fetch a list of branches from git in the active choice reactive reference parameter.I am using the run *groovy script* option.But the script is ran twice when I check the tomcat logs.Because of which the drop down is rendered twice.Please find the below script html= {code:java} def html= '''Select... {code} ''' {code:java} def cmd = ["/bin/bash", "-c","sudo sh /home/centos/JenkinScripts/dynamicChoices/getBranchesFromGit.sh https://kgjenk...@bitbucket.org/vtakru/escloudadmin.git"] def sout = new StringBuffer() def serr = new StringBuffer() // Run the command println "running "+cmd def proc = cmd.execute() proc.consumeProcessOutput ( sout, serr ) proc.waitFor() def options="" sout.tokenize().each{ branch-> if(branch.contains("refs/heads/")){ branch=branch.minus("refs/heads/") println "Branch "+branch options+="$branch" } } html+=options return html {code} Please help me with 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
[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title
Bruno P. Kinoshita updated an issue
Jenkins / JENKINS-49894
Active Choices Reactive Reference Parameter triggering the groovy script twice
Change By:
Bruno P. Kinoshita
I am trying to fetch a list of branches from git in the active choice reactive reference parameter.I am using the run *groovy script* option.But the script is ran twice when I check the tomcat logs.Because of which the drop down is rendered twice.Please find the below scripthtml= ''' {code:java} Select... {code} ''' {code:java} def cmd = ["/bin/bash", "-c","sudo sh /home/centos/JenkinScripts/dynamicChoices/getBranchesFromGit.sh https://kgjenk...@bitbucket.org/vtakru/escloudadmin.git"]def sout = new StringBuffer()def serr = new StringBuffer()// Run the commandprintln "running "+cmddef proc = cmd.execute()proc.consumeProcessOutput ( sout, serr )proc.waitFor() def options=""sout.tokenize().each \ { branch->if(branch.contains("refs/heads/")) \ {branch=branch.minus("refs/heads/")println "Branch "+branchoptions+="$branch"}}html+=optionsreturn html {code} Please help me with 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
[JIRA] (JENKINS-54018) Exception on UI after Manually uploading Plugins
Title: Message Title Bruno P. Kinoshita commented on JENKINS-54018 Re: Exception on UI after Manually uploading Plugins Gokulendra Panda, among the components you assigned, you added active-choices-plugin, but there is no mention of it in your description, stack trace, or in the issues. Just checking, do you believe this issue is related to active-choices? 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title Bruno P. Kinoshita commented on JENKINS-40501 Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter Haven't had time to look into this after remi P's great comment with steps to reproduce. Let's reopen it. If anyone has time to investigate, pull requests welcome! 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title Bruno P. Kinoshita updated JENKINS-40501 Jenkins / JENKINS-40501 Reactive Reference Parameter not working with "List Subversion Tags" parameter Change By: Bruno P. Kinoshita Status: In Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54926) reactive parameters are no longer reacting
Title: Message Title Bruno P. Kinoshita commented on JENKINS-54926 Re: reactive parameters are no longer reacting Not a problem marlene cote. But thanks a lot for updating the ticket's resolution, and also explaining what happened - which might be helpful to others with similar issues. Bruno 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-54926) reactive parameters are no longer reacting
Title: Message Title Bruno P. Kinoshita commented on JENKINS-54926 Re: reactive parameters are no longer reacting Not a problem marlene cote. But thanks a lot for updating the ticket's resolution, and also explaining what happened - which might be helpful to others with similar issues. Bruno 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-37579) image-gallery-plugin should support pipeline builds
Title: Message Title Bruno P. Kinoshita commented on JENKINS-37579 Re: image-gallery-plugin should support pipeline builds (and if the plugin is awesome, that's only because of users that are also awesome to help with issues, pull requests, documentation, pinging issues to help prioritize them, etc so thanks for helping make this plugin helpful to others) 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-37579) image-gallery-plugin should support pipeline builds
Title: Message Title Bruno P. Kinoshita commented on JENKINS-37579 Re: image-gallery-plugin should support pipeline builds Hi Amit Bakhru, alas I am a bit strapped for time this end of year. I might have some time for BioUno/Jenkins plug-ins around x-mas. When I start to triage issues, I normally favour the ones that are easier to reproduce, debug, and fix. What would be helpful for this one to be done quickly, would be to have as much info as possible. For example, a scenario including Jenkins version, other plugins (pipeline - which I am normally not using), imaging-plugin version, then a simple job that shows why it doesn't work. And, finally, a short explanation of how it should work. Being able to foresee possible issues (e.g. workspace with pipelines, remote jobs, checkpoints with the plugin, etc etc) would be extra helpful Cheers Bruno 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-23265) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Title: Message Title Bruno P. Kinoshita commented on JENKINS-23265 Re: TestLink plugin indicates test case as "not run" and TestLink is not updated with build status Sobhit Sharma not updates from my, sorry. I am not using the plug-in, nor is my current employer, and at spare time I am working on other open source projects right now, so not much time left to volunteer on this plug-in. But if anyone suggests a fix through a pull request, I'd be happy to have a look, review, merge, and release a new version. I put this plug-in up for adoption, so anybody willing to contribute for a longer time and would like to be the maintainer, just get in touch. If anybody's environment is broken, and a fix is desperately needed, CloudBees offers paid services to manage plug-ins. Cheers Bruno 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-39665) Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-39665 Re: Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin Hi Lubomir Stanko, Added comments to the pull request explaining why this approach would cause issues to other existing users of the plugin. Unfortunately I think we have to investigate other alternatives to workaround scroll bars or performance issues (or a completely different approach). But always thinking what will happen to other users Cheers Bruno 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-53122) Add i18n messages files
Title: Message Title Bruno P. Kinoshita commented on JENKINS-53122 Re: Add i18n messages files From: https://wiki.jenkins.io/display/JENKINS/Active+Choices+Plugin?focusedCommentId=143495207#comment-143495207 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53122) Add i18n messages files
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-53122 Add i18n messages files Change By: Bruno P. Kinoshita Summary: Add i18n messages files Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53122) Add messages files
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-53122 Add messages files Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2018-08-19 23:11 Priority: Minor Reporter: Bruno P. Kinoshita We had a message on the Wiki about internationalisation, but never added the messages.properties files. We need these for Jelly and Java. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Ioannis Moutsatsosuno-choice.hpi as promised, here's the hpi Just checked out the project and `mvn clean package`'d. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49260) this.binding.jenkinsProject not returning project of current build
Title: Message Title Bruno P. Kinoshita updated JENKINS-49260 Fixed in pull request. Thanks! Jenkins / JENKINS-49260 this.binding.jenkinsProject not returning project of current build Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Fixed in pull request 20 by sebcworks (thanks!) https://github.com/jenkinsci/active-choices-plugin/pull/20 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita updated JENKINS-51296 Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-39593 Performance slow in 1.5 release Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita commented on JENKINS-39593 Re: Performance slow in 1.5 release Thanks for testing it Piotr Tempes! I suspect we had these issues in 1.5.x releases too, and - hopefully - they were all fixed in 2.x. I've re-applied the changes from the old branch, onto the new code base, and created the branch https://github.com/jenkinsci/active-choices-plugin/tree/JENKINS-39593-2 Testing, I couldn't notice much difference. But maybe someone with a test server and a few more example projects could test it too? If anyone has some spare time to test it, here's a new version attach (uno-choice-20180527.hpi). Thanks! Bruno Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-39593 Performance slow in 1.5 release Change By: Bruno P. Kinoshita Attachment: uno-choice-20180527.hpi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-39593 Performance slow in 1.5 release Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Bruno P. Kinoshita stopped work on JENKINS-29407 Change By: Bruno P. Kinoshita Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-29407 Re: Active Choices plugin doesn't work with Workflow Plugin Previous comment was also a memory note, as I tend to forget things after a while but if you've read it and have another alternative, please let me know. So far the only other ways I can think of fixing it is by modifying the Jenkins core, which would require a longer time to design the change and get its approval (if approved) by core-devs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-29407 Re: Active Choices plugin doesn't work with Workflow Plugin Started working on this issue today after a long time (it's quite a storm outside anyway). Alas I couldn't find a good solution yet. Branch: https://github.com/jenkinsci/active-choices-plugin/tree/pipeline-support Started by fixing the variables jenkinsBuild and jenkinsProject for pipeline builds (which also removes one deprecated method call at least). Then created a few pipeline jobs to test the plug-in. As expected, when you add "This build is parameterized", everything works as expected. But if you call another job, the cascaded parameters do not receive updates from other parameters. The behaviour is the same you would see by scheduling a job with AC cascaded parameters. When a job is scheduled without the UI, we could - in theory - still create the values for parameters, and then notify other parameters about the update, or read the value of the referenced parameters. These are the two options we have I think. Alternative 1) notify other parameters about the update When the UI is available, and we have _javascript_ and the DOM, what we created in Active Choices is a push based parameters update. Where one parameter is changed, and then kindly goes to each of its children parameters and tells them that there is an update available. We are able to do that, because we basically hijack each parameter in the UI that we need, and add event listeners to notify parameters. But in the Java side, there is no option for doing the same. We could modify our parameters in Active Choices to notify other parameters in the "default value" method, or even check what was the "Cause" that triggered the job, and identify when the UI/DOM is not available... but we don't have an option to update other parameters such as String Parameter. Nor we have any extension point in Jenkins for that. Alternative 2) read the value of the referenced parameters In this case, you have something like PARAM1 – is referenced by – > PARAM2. In the UI, you must have PARAM1 configured before PARAM2, so that PARAM1 is executed first. The order is kept in timer scheduled builds. So PARAM1 is executed fine. But when PARAM2 (which is either a HTML referenced parameter, or a cascade choice parameter) is executed, the value of its referenced parameters is not updated. When you have the UI, this update happens via _javascript_. Inside the PARAM2 execution, you can retrieve the project (we already do that, to put the jenkinsProject variable in the context for Groovy). And via the project, you can retrieve the other parameters. Amongst these parameters, you can find the one that is referenced by PARAM2, i.e. PARAM1. However, there is no value associated with PARAM1. The value is never stored in some context or session that can be accessed by other parameters. I believe because Jenkins was not designed for that, which makes sense I think.
[JIRA] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Bruno P. Kinoshita started work on JENKINS-29407 Change By: Bruno P. Kinoshita Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43573) Build form value different than parameter passed to the build
Title: Message Title Bruno P. Kinoshita commented on JENKINS-43573 Re: Build form value different than parameter passed to the build Perfect! Thanks for updating the ticket. >Do you think that there are other such 'features from the Jenkins UI' that we need to note? Definitely, though my memory... and the Jenkins core API has changed a lot since pipelines, blue ocean, etc... so probably more things have changed since the last I checked it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43573) Build form value different than parameter passed to the build
Title: Message Title
Bruno P. Kinoshita commented on JENKINS-43573
Re: Build form value different than parameter passed to the build
Hi Ioannis! Little un-documented feature from Jenkins UI: check boxes values need a JSON value That's why we do it here: https://github.com/jenkinsci/active-choices-plugin/blob/2b542d2fee641efa445ac4aed1c8cda597ef850d/src/main/resources/org/biouno/unochoice/common/checkboxContent.jelly#L23 Just tested your example after updating the checkbox used, and it seemed to have worked.
def choices=['DNA','RNA','Protein']
def color=['#ff','#00ff00','#ff','#ff','#ff','#ff']
def html=''
idx=0
choices.each{
html=html+"""
---:${it as String}
"""
idx++
}
return html
Could you give it a try, and if that works mark this issue as Not an issue or similar, please? Cheers Bruno
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-43126) TestLink connected to Jenkins but tests are marked as 'not run' and fails to log to jenkins
Title: Message Title Bruno P. Kinoshita closed an issue as Won't Fix I believe you commented on another issue saying you have this issue. Opening an extra issue will just increase the number of tickets developers need to fix, and make it harder for them, and likely slow down the release with your fix Let's focus on the existing issue, and in case a release with the fix for that issue does not fix your problem, let's discuss and maybe create a new issue. Thanks Bruno Jenkins / JENKINS-43126 TestLink connected to Jenkins but tests are marked as 'not run' and fails to log to jenkins Change By: Bruno P. Kinoshita Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
