[JIRA] (JENKINS-62035) Tabular report no longer sortable
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-62035 Tabular report no longer sortable Issue Type: Bug Assignee: Unassigned Components: summary_report-plugin Created: 2020-04-23 20:08 Environment: Jenkins 2.222.1, summary_report-plugin v1.15 Labels: reporting summary css Priority: Minor Reporter: Ioannis Moutsatsos After upgrading Jenkins to v2.222.1 reports with sortable columns are no longer sortable. I have noticed that now a different CSS stylesheet is loaded when one inspects the table headers. The CSS for elements with class="sortheader" is now loaded from http://yourJenkinsServer/static/98e8fbe5/jsbundles/base-styles-v2.css while previously was loading from http://yourJenkinsServer/static/166f2f84/css/style.css Add Comment
[JIRA] (JENKINS-59056) Report displays raw HTML if CDATA terms are used
Title: Message Title Ioannis Moutsatsos commented on JENKINS-59056 Re: Report displays raw HTML if CDATA terms are used Adam Olejar you can apply the setting at the command used to startup Jenkins. This is what my command line looks like: java -Xrs -Xmx2048m -XX:MaxPermSize=512m -Dhudson.model.DirectoryBrowserSupport.CSP= -Dorg.kohsuke.stapler.jelly.CustomJellyContext.escapeByDefault="false" -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "path/to/jenkins/jenkins.war" --httpPort=8080 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.201412.1566489784000.13204.1587139920203%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Thank you Adam Gabryś. I've learned something! Bruno P. Kinoshita it should be safe to incorporate these basic improvements into a new release. Thank you! 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.204555.1581528008000.4204.1583864280262%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Adam Gabryś thank you for the clatification. I missed this point (since I never use the parameters this way). In this case YES I can reproduce the issue with previous versions of the plugin, and INDEED it is corrected in this version. I would love to see an example where you can set other Active Choices parameters to a value using GET or POST. Does the cascading of other Active Choices still works? For the plugin documentation we state that this plugin only works and is intended for interactive use by a human and not by API. Has this PR changed that? See: https://plugins.jenkins.io/uno-choice/ 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.204555.1581528008000.3894.1583847240133%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Ioannis Moutsatsos Attachment: image-2020-03-10-09-32-13-452.png 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.204555.1581528008000.3887.1583847180325%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL The 2.2.3 snapshot works. However, using Plugin v 2.1 and 2.2.2 I'm not able to reproduce the Jira issue as reported . In each case I get the correct default value selected. (see screenshot below)Nonetheless, I'm using an older version of [Jenkins ver. 2.121.3 and |https://jenkins.io/] [Jenkins ver. 2.187|https://jenkins.io/] Is it possible that this could be the difference causing the issue?!image-2020-03-09-15-50-25-634.png! 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.204555.1581528008000.3452.1583783940173%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL It is not clear what issue this PR is resolving The 2 . Using 2.3 snapshot works. However, using Plugin v 2.1 and 2.2.2 I'm not able to reproduce the Jira issue as reported . In each case I get the correct default value selected. (see screenshot below) Nonetheless, I'm using an older version of [Jenkins ver. 2.121.3|https://jenkins.io/]Is it possible that this could be the difference causing the issue? !image-2020-03-09-15-50-25-634.png! 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.204555.1581528008000.3447.1583783700228%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Ioannis Moutsatsos Attachment: image-2020-03-09-15-50-25-634.png 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.204555.1581528008000.3441.1583783460363%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL It is not clear what issue this PR is resolving. Using Plugin v 2.1 and 2.2.2 I'm not able to reproduce Jira issue as reported In each case I get the correct default value selected. 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.204555.1581528008000.3444.1583783460441%40Atlassian.JIRA.
[JIRA] (JENKINS-61219) Display a warning message if Active Choice script is not yet approved
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-61219 Display a warning message if Active Choice script is not yet approved Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-02-25 12:24 Priority: Minor Reporter: Ioannis Moutsatsos When a project containing Active Choice parameters is loaded from the disk (via Jenkins reload) it is possible that some of the Active Choice scripts are not approved yet by an administrator. As a result, the project would fail to render correctly. We should display a warning message on the screen similar to the Extended Choice plugin. https://plugins.jenkins.io/extended-choice-parameter/ The message has a link that takes the user to the screen where the scripts can be approved. The user should have admin access to approve scripts. Add Comment
[JIRA] (JENKINS-54887) How can multiple text boxes be created corresponding to each choice done via active choice reactive parameter and how to access them from your jenkins workspace?To be more preci
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-54887 How can multiple text boxes be created corresponding to each choice done via active choice reactive parameter and how to access them from your jenkins workspace?To be more precise refer as per my attachment Change By: Ioannis Moutsatsos Labels: ActiveChoices dynamic question textbox 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.195889.1543326808000.4979.1581255060184%40Atlassian.JIRA.
[JIRA] (JENKINS-55007) How do I have more then one parameter on a single line for parameterized jobs?
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-55007 How do I have more then one parameter on a single line for parameterized jobs? Change By: Ioannis Moutsatsos Labels: question 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.196043.154393021.4976.1581255000209%40Atlassian.JIRA.
[JIRA] (JENKINS-58619) execute commands such as git inside jenkins DSL plugin for dynamic parameters
Title: Message Title Ioannis Moutsatsos commented on JENKINS-58619 Re: execute commands such as git inside jenkins DSL plugin for dynamic parameters The recommended way for troubleshooting Active Choice scripts is from the Jenkins Groovy console. Write your script and variables as they will be used in the job and test the script until it works correctly and returns the required data structure for the Active Choice type you are using. In the context of a freestyle job Active Choice parameters are reported to the Chrome _javascript_ console and that is also helpful for troubleshooting. Hope this helps 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.200785.1563905144000.4971.1581254880243%40Atlassian.JIRA.
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos resolved as Fixed Not an issue. Working as expected Jenkins / JENKINS-59938 Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Change By: Ioannis Moutsatsos Status: Open Resolved 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
[JIRA] (JENKINS-60790) Project
Title: Message Title Ioannis Moutsatsos closed an issue as Fixed Undefined issue or spam Jenkins / JENKINS-60790 Project Change By: Ioannis Moutsatsos Status: Open Closed 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
[JIRA] (JENKINS-43752) Not able to use git, sh, pwd etc in active choice parameter script
Title: Message Title Ioannis Moutsatsos commented on JENKINS-43752 Re: Not able to use git, sh, pwd etc in active choice parameter script My understanding is that these scripts are Groovy DSL and not pure Groovy. I would not expect them to work in Active Choices, unless the appropriate DSL libraries are included. Have you tried that? 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.181168.1492763793000.14706.1576981680191%40Atlassian.JIRA.
[JIRA] (JENKINS-57498) string value in Groovy script in Reactive Choice parameter replaced with null when approved in in-process script approval
Title: Message Title Ioannis Moutsatsos commented on JENKINS-57498 Re: string value in Groovy script in Reactive Choice parameter replaced with null when approved in in-process script approval nimesh saman I'm suspecting that the code peculiar formatting is causing some display issues with the widget used in the Jenkins UI widget for the script approval. I have run into a similar issue with code that looks like html textarea in the Scriptlet plugin Groovy editor 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.199360.1557990365000.14703.1576981260166%40Atlassian.JIRA.
[JIRA] (JENKINS-59389) Active choices plugin causes Jenkins to crash on startup
Title: Message Title Ioannis Moutsatsos resolved as Fixed Jenkins / JENKINS-59389 Active choices plugin causes Jenkins to crash on startup Change By: Ioannis Moutsatsos Status: Open Resolved Resolution: Fixed Released As: v 2.2.1 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.14699.1576980720375%40Atlassian.JIRA.
[JIRA] (JENKINS-60519) Move Plugin documentation to github
Title: Message Title Ioannis Moutsatsos resolved as Fixed Documentation has been transferred to GitHub form the Confluence wiki and is now available as the readme.md file in the root folder of the project Jenkins / JENKINS-60519 Move Plugin documentation to github Change By: Ioannis Moutsatsos Status: Open Resolved Assignee: Bruno P. Kinoshita Ioannis Moutsatsos Resolution: Fixed Released As: v2.2.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60519) Move Plugin documentation to github
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-60519 Move Plugin documentation to github Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2019-12-18 02:23 Priority: Minor Reporter: Ioannis Moutsatsos See: https://jenkins.io/blog/2019/10/21/plugin-docs-on-github/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59191) SPAM-Not an issue
Title: Message Title Ioannis Moutsatsos updated JENKINS-59191 Jenkins / JENKINS-59191 SPAM-Not an issue Change By: Ioannis Moutsatsos Status: Fixed but Unreleased Closed 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.201632.1567441959000.7470.1576286940258%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated JENKINS-60319 Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Status: Fixed but Unreleased Closed Resolution: Fixed 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.203316.1574954163000.7466.1576286580290%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated JENKINS-60319 Cast Objects to String. The returned Groovy array should always be a String array Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Status: Open Fixed but Unreleased Assignee: Bruno P. Kinoshita Ioannis Moutsatsos Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-60319
Re: Reactive Parameter ignores toString
class Choice {
String tag
String branch
@Override
String toString() {
return tag + ' / ' + branch
}
}
def obj1 = new Choice(branch: '1', tag:"3")
def obj2 = new Choice(branch: '2', tag:"4")
println obj1.getClass()
return [obj1 as String, obj2 as String ]
This works as expected. It seems to me that the original array is not 'stingified' .You need to explicity cast the Choice objects to String.
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.7461.1576286400415%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Attachment: image-2019-12-13-20-19-21-140.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.203316.1574954163000.7458.1576286400278%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Attachment: image-2019-12-13-20-15-51-433.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.203316.1574954163000.7455.1576286160207%40Atlassian.JIRA.
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-59938 Re: Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Indeed this is how the cascade parameter update happens. Any parameter used by an active choice reactive has to be defined upstream. There are some advanced strategies for sharing parameters independent of their sequence in the form (using an in-memory h2 database) but this is beyond the scope of most typical freestyle jobs. We have discussed this with [~kinow] as a future improvement. 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.202740.1572022411000.1514.1573784040183%40Atlassian.JIRA.
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59938 Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Change By: Ioannis Moutsatsos Issue Type: Bug Improvement 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.202740.1572022411000.1511.1573783980332%40Atlassian.JIRA.
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos commented on JENKINS-59938 Re: Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Indeed this is how the cascade parameter update happens. Any parameter used by an active choice reactive has to be defined upstream. There are some advanced strategies for sharing parameters independent of their sequence in the form (using an in-memory h2 database) but this is beyond the scope of most typical freestyle jobs. 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.202740.1572022411000.1505.1573783920353%40Atlassian.JIRA.
[JIRA] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-29407 Re: Active Choices plugin doesn't work with Workflow Plugin [~kinow] thanks for the interesting comment/memory dump above! As of now (OCT-25-2019), there are at least 13 different active-choice Jira related tickets referencing the use of this plugin in pipeline jobs/Jenkinsfile. Given that this plugin was designed to be used interactively on freestyle job build forms (clearly stated in the plugin documentation) is there a point to keep looking for solutions in this space especially if there are no convenient Jenkins extension points to support this approach? Should we just close all these issues as will not be done. It seems no-one is reading the plugin documentation any longer. Perhaps these AC shortcomings could be addressed in a different plugin designed specifically for pipeline jobs. 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.1371.1572000720569%40Atlassian.JIRA.
[JIRA] (JENKINS-29407) Active Choices plugin doesn't work with Workflow Plugin
Title: Message Title Ioannis Moutsatsos commented on JENKINS-29407 Re: Active Choices plugin doesn't work with Workflow Plugin Bruno P. Kinoshita thanks for the interesting comment/memory dump above! As of now (OCT-25-2019), there are at least 13 different active-choice Jira related tickets referencing the use of this plugin in pipeline jobs/Jenkinsfile. Given that this plugin was designed to be used interactively on freestyle job build forms (clearly stated in the plugin documentation) is there a point to keep looking for solutions in this space especially if there are no convenient Jenkins extension points to support this approach? Should we just close all these issues as will not be done. It seems no-one is reading the plugin documentation any longer. 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.1351.1572000664531%40Atlassian.JIRA.
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Ioannis Moutsatsos commented on JENKINS-58219 Re: Active Choices Reactive Parameter Groovy script returning String instead of List Brett Hand AC parameters have not been tested in use with Jenkinsfile and we only have experience using them in 'freestyle' type builds. Nonetheless, in these cases returning a list of Strings is required for proper display in the build form UI. The parameters are passed to the build as text with the selected options as a comma separated String. You may need to tokenize this string to return a list. Note that 'splitting' a string with Groovy returns a String[] not a list I hope this helps. And any experience with using AC parameters in jenkinsfile is always useful (for future reference). Thank you! 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.200279.1561574404000.1367.1568217300202%40Atlassian.JIRA.
[JIRA] (JENKINS-59188) How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter
Title: Message Title Ioannis Moutsatsos closed an issue as Fixed Question answered Jenkins / JENKINS-59188 How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter Change By: Ioannis Moutsatsos Status: Open Closed 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
[JIRA] (JENKINS-59188) How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-59188
Re: How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter
If you must have multiple parameters into a single Jenkins parameter 'Frontend_Merge' you can have an AC REF parameter that returns a json structure and then parse it in your build. So the 'Frontend_Merge' would return a value something like:
{
"ffchef_backend":[
"branch1",
"branch2"
],
"ffchef_frontend":[
"branch3",
"branch4"
]
}
Nonetheless, I would still recommend having a separate AC Ref for 'ffchef_backend' and another for ffchef_frontend'
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.201626.156743271.1359.1568216520183%40Atlassian.JIRA.
[JIRA] (JENKINS-59191) SPAM-Not an issue
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59191 SPAM-Not an issue Change By: Ioannis Moutsatsos Summary: Jual Obat Kuat Asli Di Apotik Medan Dan Harganya SPAM-Not an issue Priority: Minor Trivial h1. *JUAL OBAT VIAGRA ASLI DI APOTIK CENTURY*[_*Viagra*_|https://apotektitangel.com/jual-obat-viagra-asli/] adalah salah satu obat kuat penunjang stamina ereksi yang banyak direkomendasikan oleh para dokter ahli di dunia sebagai obat disfungsi ereksi. _*Obat viagra asli*_ berbentuk pil berwarna biru dengan bentuk seperti wajik atau ketupat. Di _*indonesia*_, viagra dikenal sebagai obat yang ampuh untuk melawan disfungsi ereksi, yang artinya obat ini dapat membuat alat vital pria menjadi ereksi dengan keras dan juga tahan lama hingga hubungan seksual dengan pasangan selesai. Dengan kata lain, obat ini dianggap menjadi salah satu solusi yang membuat para pria lega dan tidak khawatir lagi dengan permasalahan seksual yang di alaminya.[!https://apotektitangel.com/wp-content/uploads/2019/04/viagra-asli.jpg|width=300,height=300!|https://apotektitangel.com/jual-obat-viagra-asli/]*Obat kuat viagra* memang salah satu obat yang banyak dicari, sebab dengan adanya obat ini dapat membantu aliran darah ke penis menjadi lancar sehingga orang yang mengkonsumsinya dapat mempertahankan ereksi. Beberapa pria memiliki permasalahan dalam ereksi, hal ini dapat memberikan pengaruh terhadap keharmonisan rumah tangga. Dimana ereksi dapat mempengaruhi ketika berhubungan badan. Tidak heran jika pria yang sulit ereksi menjadi tidak percaya diri ketika berhubungan bersama pasangan, hal inilah yang menjadi pemicu retaknya rumah tangga anda. Maka kehadiran obat ini dianggap menjadi solusi untuk anda yang memiliki permasalahan itu, namun masih banyak orang yang belum mengenal bagaimana cara kerja viagra dan siapa saja yang boleh mengkonsumsinya. Sebab terdapat beberapa aturan jika anda ingin mengkonsumsinya agar dapat bekerja dengan sangat efektif dan optimal.*Viagra asli* original pfizer usa atau yang biasa di sebut dengan _*pil biru*_ ini banyak di jual di Apotik Kimia Farma, Century, K24 di seluruh kota besar indonesia seperti Bogor, Jakarta, Tangerang, Bekasi, Depok, Semarang, Makassar, Palembang, Surabaya dan lain sebagainya.h3. *Ciri - Ciri Viagra Asli :* * Di kemas dalam 1 botol berisi 30 tablet * Rasanya sangat pahit * Tablet berwarna biru dan sangat keras * Pil berbentuk jajargenjang dengan tulisan Pfizer di bagian tengah * Tablet Viagra asli berbentuk jajargenjang dengan tulisan Pfizer di bagian
[JIRA] (JENKINS-59191) Jual Obat Kuat Asli Di Apotik Medan Dan Harganya
Title: Message Title Ioannis Moutsatsos updated JENKINS-59191 SPAM! Jenkins / JENKINS-59191 Jual Obat Kuat Asli Di Apotik Medan Dan Harganya Change By: Ioannis Moutsatsos 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
[JIRA] (JENKINS-59056) Report displays raw HTML if CDATA terms are used
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-59056 Re: Report displays raw HTML if CDATA terms are used After some investigation and head-banging I came across what seems to be the exact cause of this bug: [https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+2018-10-10+Stapler+security+hardening] The Summary Display Plugin is specifically listed and the 'impact/behavior' is listed as 'Raw HTML is shown if CDATA terms are used' They also claim that 'We expect that (affected) plugins will adapt pretty quickly to this change, as the fix is typically straightforward.' Finally a workaround is offered, which I'm using until the plugin is fixed. See [https://jenkins.io/doc/upgrade-guide/2.138/#security-hardening-to-prevent-xss-vulnerabilities] 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.201412.1566489784000.8954.1566591720057%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) Report displays raw HTML if CDATA terms are used
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59056 Report displays raw HTML if CDATA terms are used Change By: Ioannis Moutsatsos Summary: HTML in report Report displays as raw HTML if CDATA terms are used 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.201412.1566489784000.8951.1566590400103%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) HTML in report displays as raw HTML if CDATA terms are used
Title: Message Title Ioannis Moutsatsos commented on JENKINS-59056 Re: HTML in report displays as raw HTML if CDATA terms are used After some investigation and head-banging I came across what seems to be the exact cause of this bug: https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+2018-10-10+Stapler+security+hardening The Summary Display Plugin is specifically listed and the 'impact/behavior' is listed as 'Raw HTML is shown if CDATA terms are used' They also claim that 'We expect that (affected) plugins will adapt pretty quickly to this change, as the fix is typically straightforward.' 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.201412.1566489784000.8950.1566589920049%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) HTML in report displays as raw HTML if CDATA terms are used
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59056 HTML in report displays as raw HTML if CDATA terms are used Change By: Ioannis Moutsatsos Summary: HTML in report no longer renders but displays as raw HTML if CDATA terms are used 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.201412.1566489784000.8948.1566589500165%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) HTML in report no longer renders but displays as raw HTML
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59056 HTML in report no longer renders but displays as raw HTML Change By: Ioannis Moutsatsos After upgrading the plugin JENKINS from v 1 v1 . 13 the 121.3 to v1.187 CDATA generated HTML is no longer rendered, but instead it is displayed as raw HTML.!image-2019-08-22-11-56-28-540.png!With the v1.13 Jenkins version 1.121 teh CDATA renders the HTML corectly to an image href !image-2019-08-22-11-56-59-572.png!Sample xml generating the 'ACTIONS' example tab is attached 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.201412.1566489784000.8947.1566589440073%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) HTML in report no longer renders but displays as raw HTML
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59056 HTML in report no longer renders but displays as raw HTML Change By: Ioannis Moutsatsos After upgrading the plugin from v 1.13 the HTML is no loger longer rendered, but instead it is displayed as raw HTML.!image-2019-08-22-11-56-28-540.png!With the v1.13 version!image-2019-08-22-11-56-59-572.png!Sample xml generating the 'ACTIONS' example tab is attached 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.201412.1566489784000.8067.1566491220071%40Atlassian.JIRA.
[JIRA] (JENKINS-59056) HTML in report no longer renders but displays as raw HTML
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-59056 HTML in report no longer renders but displays as raw HTML Issue Type: Bug Assignee: Unassigned Attachments: actions.xml, image-2019-08-22-11-56-28-540.png, image-2019-08-22-11-56-59-572.png Components: summary_report-plugin Created: 2019-08-22 16:03 Environment: Jenkins v 2.187 Summary Display Plugin v1.15 Labels: reporting HTML Priority: Major Reporter: Ioannis Moutsatsos After upgrading the plugin from v 1.13 the HTML is no loger rendered, but instead it is displayed as raw HTML. With the v1.13 version Sample xml generating the 'ACTIONS' example tab is attached
[JIRA] (JENKINS-54647) Plugin is not working in downstream jobs
Title: Message Title Ioannis Moutsatsos commented on JENKINS-54647 Re: Plugin is not working in downstream jobs Unfortunately, you are not providing enough information to understand your issue. Having the parameter configuration or even some screenshots included, would help. Nonetheless, Active Choice parameters are used interactively and set by the user. Active choice parameters were not designed for automated selection of parameters 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.195437.1542290232000.1118.1557745920136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53540) Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-53540
Re: Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
You understand of course that ${ReactiveRefParam} is either a referenced parameter (from upstream input) or a variable computed in within the code block of the AC Reactive Reference. If you are still having difficulty, please, submit your configuration for me to provide additional feedback. Bets regards
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.194016.1536789673000.1095.1557744727685%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 Ioannis Moutsatsos commented on JENKINS-38893 Re: Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Thanks for looking into this Bruno! So you have clearly confirmed my previous investigation: https://issues.jenkins-ci.org/browse/JENKINS-38893?focusedCommentId=305784=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-305784 Excellent! I will investigate the workaround you suggested, but I think this is the first case where we can't reproduce a functional Jenkins UI control whose value can be cascaded in the typical AC way. I will try to document on wiki after I find a workaround for it. Thank you-have a great Sunday afternoon in NZ! 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 Ioannis Moutsatsos commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Thank you for your feedback Saheta B 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-52497) Jenkins cannot build with error - groovy
Title: Message Title Ioannis Moutsatsos commented on JENKINS-52497 Re: Jenkins cannot build with error - groovy Tomas Pavelka any updates? Is this really due to the Active Choice parameter. Otherwise, please provide a test case we can troubleshoot. Best regards Ioannis 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-53540) Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter
Title: Message Title Ioannis Moutsatsos commented on JENKINS-53540 Re: Dynamically allow user to provide information in "Input text box" field for Active Choices Reactive Reference Parameter This behavior is already present in AC Reactive Reference. Return a 'Formatted HTML' parameter (not an Input Text Box) of type and insure that under advanced options you select 'Omit value filed' You can even provide a default value that can be further edited by the user. Something like this would work: return "" 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-54006) No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter
Title: Message Title Ioannis Moutsatsos commented on JENKINS-54006 Re: No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter Have you tried to go into the advanced options of the AC Reactive Reference and check the Omit value field option? Otherwise the default 'null' value is passed into the build 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-54006) No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-54006 No value is passed in case of Multiple Formatted HTML Active Choice Reactive Reference parameter Change By: Ioannis Moutsatsos Attachment: image-2019-03-09-09-58-36-226.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-55007) How do I have more then one parameter on a single line for parameterized jobs?
Title: Message Title Ioannis Moutsatsos commented on JENKINS-55007 Re: How do I have more then one parameter on a single line for parameterized jobs? Hi ANSHUK ROY You could use an Active Choice reactive reference to return formatted HTML. You could then have multiple input fields and other control inputs (checkboxes, calendar, colors etc) returned by a single parameter. You may need to deconvolute this complex value later though, as it will return the various values simply as a comma separated list Hope this helps Best regards Ioannis 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 Ioannis Moutsatsos edited a comment on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Why is this issue even tagged with Active Choices plugin? I don't see what the issue is with AC? I have removed the AC plugin tag until the relevance is demonstrated 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 Ioannis Moutsatsos updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Ioannis Moutsatsos Component/s: active-choices-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Ioannis Moutsatsos commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Why is this issue even tagged with Active Choices plugin? I don't see what the issue is with AC? 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 Ioannis Moutsatsos commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Hi Madhavi. I must say that most issues with AC reactive parameters boil down to the values of referenced parameters. Depending on the state of your build form referenced parameter values could change (or even be null) and of course that would affect the success or failure of the AC reactive script. Do you have a fallback script? This is always a good way to troubleshoot. You can have a fallback script that reports the values of referenced parameters so at least you know what the script input is. Finally, you can debug your AC reactive script by running it from the script console and hard-coding some of the input values to observe it behavior Hope this is helpful Best regards Ioannis 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-48709) html
Title: Message Title Ioannis Moutsatsos closed an issue as Fixed Fixed in updated version of Active Choices Jenkins / JENKINS-48709 html
[JIRA] (JENKINS-50485) Active Choice Reactive Parameter not returning list as output
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-50485 Active Choice Reactive Parameter not returning list as output Change By: Ioannis Moutsatsos Priority: Critical Minor 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-50485) Active Choice Reactive Parameter not returning list as output
Title: Message Title Ioannis Moutsatsos closed an issue as Not A Defect Closing this as it appears to be a programming issue. The user did not respond to the testing suggestion either Jenkins / JENKINS-50485 Active Choice Reactive Parameter not returning list as output Change By: Ioannis Moutsatsos Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53498) Ant Task locks build log file. Unable to delete build.
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-53498 Ant Task locks build log file. Unable to delete build. Issue Type: Bug Assignee: Unassigned Attachments: Untitled_Clipping_091018_025240_PM.jpg, Untitled_Clipping_091018_025642_PM.jpg Components: antexec-plugin Created: 2018-09-10 18:58 Environment: Jenkins v2.121.3 LTS, AntExec v1.11 Java v1.8.0.161, Windows Server 2008 Labels: lock log delete ant unzip Priority: Major Reporter: Ioannis Moutsatsos Running Jenkins on a Windows 2008 server, I'm experiencing an issue where using the AntExec plugin and executing the ant unzip task on a file in the workspace works, but leaves a file handle open on the log file of the build. As a result, trying to delete these builds fails with a Java IOException see error screnshot. Using Windows Process Explorer, I can see that the file handles are open for all the builds executed and not just the last one. Note, I have also noticed similar issues with trying to run the same Ant task from a System Groovy script.
[JIRA] (JENKINS-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Ioannis Moutsatsos commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 You must note that most editors that work fine with XML 1.0 can't parse XML 1.1. After more than a decade successfully using the free MS utility XML Notepad for all XML tasks I may have to look for another editor. How much of a demand there was for this change? 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-48463 Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Change By: Ioannis Moutsatsos Attachment: image-2018-08-30-17-20-59-194.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-38893) Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
Title: Message Title Ioannis Moutsatsos commented on JENKINS-38893 Re: Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Changed the severity, as this is directly affecting the expected behavior of the AC control 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 Ioannis Moutsatsos updated an issue Jenkins / JENKINS-38893 Active Choice Reactive Reference parameter value rendered as File Selector not cascaded Change By: Ioannis Moutsatsos Priority: Minor Major 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 Ioannis Moutsatsos updated an issue Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Change By: Ioannis Moutsatsos In the UIproject UI project configuration: Adding Scriptler based Active Choice parameters to a project does not display the '_ViewScript_' and Scriptler _Required Parameters_. This *makes it difficult to inspect the scriptlet and set the job parameters.*The ' _ViewScrip_t _ViewScrip ' and _Required Required parameters_ are displayed ONLY IF a Scriptler based build step is added.Here is an comparison of what the configuration screen looks like without and with a Scriptler build step!image-2018-08-30-13-28-49-996.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-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: image-2018-08-30-13-28-49-996.png Components: active-choices-plugin Created: 2018-08-30 17:30 Environment: Jenkins v 2.212.3, Active-Choices v2.1 Priority: Minor Reporter: Ioannis Moutsatsos In the UIproject configuration: Adding Scriptler based Active Choice parameters to a project does not display the 'ViewScript' and Scriptler Required Parameters. This makes it difficult to inspect the scriptlet and set the job parameters. The 'ViewScrip_t' and _Required parameters are displayed ONLY IF a Scriptler based build step is added. Here is an comparison of what the configuration screen looks like without and with a Scriptler build step
[JIRA] (JENKINS-39618) HTML in portlet 'Display Name' not rendered in versions more recent than 2.9.7
Title: Message Title Ioannis Moutsatsos commented on JENKINS-39618 Re: HTML in portlet 'Display Name' not rendered in versions more recent than 2.9.7 That is rather unfortunate! It was a really useful feature and I was using it a lot. Any other ideas whether we can enhance the display name tabs? Till then I may have to stick to v2.9.7. Thanks and best regards 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 Ioannis Moutsatsos edited a comment on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Hi [~kinow] Finished testing today and the current snapshot does NOT seem to resolve the issue. After renaming the project I checked the projectName in the config.xml file and it seems to still point to the name of the project before renaming. Attaching before and after project rename ScreenshotsI have also tested COPYing a project to a different name. This works! When the project is copied to a new config.xml the projectName references are updated. I need perhaps to add that I'm currently using Jenkins v2.100. I was just reading some notes 'UI for renaming jobs' has been changed: JENKINS-22936 Could some of these discrepancies be due to different versions of Jenkins? 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 Ioannis Moutsatsos edited a comment on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Hi [~kinow] Finished testing today and the current snapshot does NOT seem to resolve the issue. After renaming the project I checked the projectName in the config.xml file and it seems to still point to the name of the project before renaming. Attaching before and after project rename Screenshots I have also tested COPYing a project to a different name. This works! When the project is copied to a new config.xml the projectName references are updated. 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 Ioannis Moutsatsos commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Hi Bruno P. Kinoshita Finished testing today and the current snapshot does NOT seem to resolve the issue. After renaming the project I checked the projectName in the config.xml file and it seems to still point to the name of the project before renaming. Attaching before and after project rename Screenshots 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 Ioannis Moutsatsos updated an issue Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Change By: Ioannis Moutsatsos Attachment: Untitled_Clipping_082918_104858_AM.jpg 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 Ioannis Moutsatsos updated an issue Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Change By: Ioannis Moutsatsos Attachment: Untitled_Clipping_082918_104650_AM.jpg 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-52413) My First Test
Title: Message Title Ioannis Moutsatsos updated JENKINS-52413 Jenkins / JENKINS-52413 My First Test Change By: Ioannis Moutsatsos Status: Fixed but Unreleased Closed 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-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title Ioannis Moutsatsos commented on JENKINS-49894 Re: Active Choices Reactive Reference Parameter triggering the groovy script twice What version of AC are you working with. Can you please, report if this issue is present in the most recent AC plugin v2.1. Thank you. 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 Ioannis Moutsatsos commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Testing today. Thanks Bruno P. Kinoshita! 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-51501) Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds"
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-51501 Re: Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds" Is it an issue with AC or with the parametrized build plugin . ? Replace the AC with a String parameter , and test by passing in the same string as it is generated by the AC script. 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-51501) Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds"
Title: Message Title Ioannis Moutsatsos commented on JENKINS-51501 Re: Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds" Is it an issue with AC or with the parametrized build plugin. Replace the AC with a String parameter and test by passing in the same string as it is generated by the AC script. 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-52413) My First Test
Title: Message Title Ioannis Moutsatsos updated JENKINS-52413 Someone is doing live tests on JIRA! Jenkins / JENKINS-52413 My First Test Change By: Ioannis Moutsatsos Status: Open Fixed but Unreleased Resolution: Won't Do 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-52644) Active choice plugin - does not run jql query of jira plugin
Title: Message Title Ioannis Moutsatsos commented on JENKINS-52644 Re: Active choice plugin - does not run jql query of jira plugin Please, insure that you are returning a string array as it is required for most Active choices, or formatted HTML if you are using AC Reactive Reference parameter 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-37485) Propagate Job params to script does nothing
Title: Message Title Ioannis Moutsatsos commented on JENKINS-37485 Re: Propagate Job params to script does nothing Dominik Bartholdi Thanks for the guidance. Unfortunately I'm still getting errors trying to access environment variables from the scriptlet using this approach. For example: Execution of script [export_metadata_query.groovy] failed - groovy.lang.MissingPropertyException: No such property: env for class: Script1org.jenkinsci.plugins.scriptler.util.GroovyScript$ScriptlerExecutionException: groovy.lang.MissingPropertyException: No such property: env for class: Script1 at org.jenkinsci.plugins.scriptler.util.GroovyScript.call(GroovyScript.java:131) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) 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-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-50837 [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3 Change By: Ioannis Moutsatsos Issue Type: Bug Improvement 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-51054) Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-51054 Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter Change By: Ioannis Moutsatsos Issue Type: Bug Improvement 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-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-50837 [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3 Change By: Ioannis Moutsatsos Priority: Critical Minor 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-51054) Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter
Title: Message Title Ioannis Moutsatsos commented on JENKINS-51054 Re: Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter The requested feature behavior is not implemented. therefore it's not a bug but rather an improvement request. 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-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: image-2018-05-14-09-29-56-458.png Components: active-choices-plugin Created: 2018-05-14 13:32 Environment: Jenkins v2.100, Active Choices v 2,1 Priority: Minor Reporter: Ioannis Moutsatsos After using the Jenkins UI to rename a project the old name remains in the Active choices configuration and the project form UI breaks. PLATE_EXPLORER was the old project name. The project is now renamed to ASSAY_EXPLORER. Tried the following two workarounds. Reload project configuration-Does not work! Make a small change to the configuration (such as changing the description of one of the parameters) and save the configuration- THIS WORKED! projectName in Active Choice parameters gets updated to the new project name
[JIRA] (JENKINS-37485) Propagate Job params to script does nothing
Title: Message Title Ioannis Moutsatsos commented on JENKINS-37485 Re: Propagate Job params to script does nothing Dominik Bartholdi I have tried the suggestion you provided and instead I get an error: groovy.lang.MissingPropertyException: No such property: BUILD_URL for class 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-49386) Windows Jenkins process locks the Log folder. Can't delete builds
Title: Message Title Ioannis Moutsatsos commented on JENKINS-49386 Re: Windows Jenkins process locks the Log folder. Can't delete builds Unfortunately, I can't get this to run successfully on my Windows server. Trying to bind to the Windows Jenkins PID I get and error com.sun.tools.attach.AttachNotSupportedException: Insufficient memory or insufficient privileges to attach Also trying to run with the http option I get no errors but the JVM starts and then immediately dies. Anyway, will this give me more information than the Windows Process Explorer? For example if some of my embedded groovy code or scriptlets are leaving the file handles open will I be able to detect it with the file-leak-detector? Thanks for the feedback 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 Ioannis Moutsatsos resolved as Not A Defect As it was pointed out by Bruno P. Kinoshita checkboxes in Jenkins UI must have a json attribute. Once this was introduced in the dynamic HTML of the ACtive Choice parameter the build parameter matches the form value. Jenkins / JENKINS-43573 Build form value different than parameter passed to the build Change By: Ioannis Moutsatsos Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-43573) Build form value different than parameter passed to the build
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-43573
Re: Build form value different than parameter passed to the build
Bruno P. Kinoshita Excellent catch! Thank you! With this change the form value is now passed correctly to the build! Got to make a note about how checkboxes must be defined using the json attribute.
"checkbox" json=":${it}" name="value" value=":${it}">
Do you think that there are other such 'features from the Jenkins UI' that we need to note?
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 Ioannis Moutsatsos commented on JENKINS-43573 Re: Build form value different than parameter passed to the build This issue is surfacing again in some of my complex builds. Kindly asking Bruno P. Kinoshita to review possible fixes. Currently the workaround is to pass this parameter to another Active Choices Reactive Reference (as in the example shown) and use that value in the build. Already complex job configuration become even more so (and features are build on bugs ) 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-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Ioannis Moutsatsos Priority: Minor Major 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-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Ioannis Moutsatsos commented on JENKINS-36158 Re: Active choice reactive reference parameter not working on checkbox reference Matthias Zangl thank you for your investigation. I finally can reproduce this bug and I can confirm that is related not only to the jQuery plugin, but also a particular version of the plugin. Active Choice Reactive references are working as expected with jQuery plugin 1.7.2-1 but not with the latest version 1.11.2-0. Hopefully Bruno P. Kinoshita will be able to focus on this particular finding to resolve the bug. Thank you both!! Bruno P. Kinoshita attached is an example to try. With multi-select you get this With Check Boxes you get Note that the checkbox values are not propagated to AC_REFPRAM_C but interestingly, they are propagated to the build! [^config[1].xml] 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-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Ioannis Moutsatsos Attachment: config[1].xml 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-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Ioannis Moutsatsos Attachment: image-2017-03-30-12-27-15-823.png 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-36158) Active choice reactive reference parameter not working on checkbox reference
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference Change By: Ioannis Moutsatsos Attachment: image-2017-03-30-12-27-53-554.png 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-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Title: Message Title Ioannis Moutsatsos commented on JENKINS-42034 Re: Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters Currently away for business. I'll review it when I get back. 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-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Title: Message Title Ioannis Moutsatsos closed an issue as Not A Defect Jenkins / JENKINS-42034 Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters Change By: Ioannis Moutsatsos Status: In Progress Closed Resolution: Not A Defect 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-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Title: Message Title Ioannis Moutsatsos started work on JENKINS-42034 Change By: Ioannis Moutsatsos 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-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-42034
Re: Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Bruno P. Kinoshita I think this works as expected. I have attached a new config[1].xml where I simplified the 'ScriptVariables' parameter script so I can easily explain what I think it's going on. Here is the simplified script:
def a = DummyVar
def FullHTML = """
jQuery(document).on('ready', function() { function updateOutputValue() { jQuery('#value').val('Booya!'); };
updateOutputValue();
});
"value" type="text" class="setting-input " value="$a">
"""
return FullHTML
The original script assigned a value through the jQuery selector on page load. That is the key point I think. The page load script only runs when the build form is first loaded. Not when the parameter is refreshed on a cascade event. So if you are not referencing another parameter the page loads and the script sets the value to 'Booya'. However, if you are referencing another parameter it triggers an update event as soon as the DummyVar is set. Since the original script did not use the DummyVar then the returned value was null. In this example, where I'm using the DummyVar value you see that it updates the value to the DummyVar value
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42034) Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-42034 Reactive Reference parameter with Formated HTML loses script section when binding to other build parameters Change By: Ioannis Moutsatsos Attachment: screenshot-1.png 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.
