[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Sridevi Sangaiah commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure Looks like the Jenkins project is configured to load source from a Stream. A valid build toolkit is required to retrieve certain details in a step that is performed in the master before checkout runs in the slave. We will update the teamconcert plugin wiki page with this limitation, shortly. 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.168320.1455716302000.21435.1557371400261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Sridevi Sangaiah commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure The console output should have information on whether the build was executed on the master or slave. 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.168320.1455716302000.20788.1557323100575%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Sridevi Sangaiah commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure From the logs it is not evident if the build ran on the master or slave? Can you please confirm that the build ran on the slave and not the master. 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.168320.1455716302000.20769.1557322740209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Sridevi Sangaiah commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure Wolf Molnar What is the error displayed in the console log? The buildtoolkit is still required for few operations performed in the master. The error logged could clarify this. 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.168320.1455716302000.20737.1557318840388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah commented on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" At the moment we can not comment on if and when will this behavior be fixed as it has to go through internal discussions. We released 1.3.0 version of the plugin this week and yet to start planning for the next release. Will provide an update as soon as we have more clarity. 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in[Allowed characters in Linux environment variable names| [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] ] See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in 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,
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [|http://example.com/] [https://stackoverflow.com/questions/2821043/allowed- Allowed characters - in -linux- Linux environment - variable - names| http://example.com/] [ ||http://example.com/] [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] [ ] |http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in 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
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [|http://example.com/] [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] [||http://example . com/] [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] []|http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in 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
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names| | http://example.com/] [https://stackoverflow . com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] []|http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in 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
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names| | http://example.com/] [https://stackoverflow . com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] []|http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in 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
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have ' _ __ ' _ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. ' _ __ ' _ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '_' in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to ' _ ' by the teamconcert plugin when creating the corresponding environment variables in 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained_ retained . '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have ' _ ' in the property names in the build definition and ignores ' _ ' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__' _ can be included in the name of the environment variables, if the build property name contains _ ' __ ___ ' _ it should be retained retained_ . '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have _ in the property names in the build definition and ignores _ when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com / ].See comment 28 in[259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131]Having said that since ' _ __ ' can be included in the name of the environment variables, if the build property name contains ' _ __ ' it should be retained. '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have _ in the property names in the build definition and ignores _ when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah commented on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" Bernd Wanko The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names. See comment 28 in 259131: HPI: Expose RTC Build properties in the Jenkins build environment Having said that since '' can be included in the name of the environment variables, if the build property name contains '' it should be retained. '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have _ in the property names in the build definition and ignores _ when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix. In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in 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-38357) Cannot use Jenkins Node properties as load directory for Team Concert plugin
Title: Message Title Sridevi Sangaiah commented on JENKINS-38357 Re: Cannot use Jenkins Node properties as load directory for Team Concert plugin Rob Leach Can you please clarify if the problem with using Node properties Environment variables in the Load Directory field, is happening with a free style job or a pipeline job? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title
Sridevi Sangaiah edited a comment on JENKINS-38224
Re: The html select element added by the dropdownlist.jelly form control needs to have a name attribute
I realized that when creating this enhancement I mentioned Id attribute instead of name attribute. Fixed it now. Sorry for the confusion. Explaining the requested enhancement with more details, below. Copying below a snippet from https://github.com/jenkinsci/ui-samples-plugin/blob/master/src/main/resources/jenkins/plugins/ui_samples/DropdownList/index.jelly{code:xml}selected="${fruit!=null}" staplerClass="${descriptor.clazz.name}"> {code} This jelly, after processing, will be converted to the following html structure.{code:xml}FruitsApple Banana {code} Notice that the name specified on the dropdownList jelly tag is set as the name for the table control that contains the html block for the current dropdown selection. The select element doesn't have any identifier. This is not a problem when doing a submit/save as the html controls are parsed and the data is formatted to json before it is sent to the server. From the formatted data it will be possible to identify the current selection in the dropdown. But in case of validation, say I have to validate some behavior depending on the current selection in the dropdown, there is no way to get the current selection as the select element doesn't have a name attribute. https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls - clearly states that there should be a name associated with the input control, for it to be sent to the server for validation. I believe this is because validate uses the html form submit to pass data to the server, which would in turn do a lookup of html controls with the specified name.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title
Sridevi Sangaiah commented on JENKINS-38224
Re: The html select element added by the dropdownlist.jelly form control needs to have a name attribute
I realized that when creating this enhancement I mentioned Id attribute instead of name attribute. Fixed it now. Sorry for the confusion. Explaining the requested enhancement with more details, below. Copying below a snippet from https://github.com/jenkinsci/ui-samples-plugin/blob/master/src/main/resources/jenkins/plugins/ui_samples/DropdownList/index.jelly
"fruit" title="Fruits">
"descriptor" items="${it.fruitDescriptors}" varStatus="loop">
"fruit" value="${descriptor==currentFruit.descriptor?currentFruit:null}"/>
"${descriptor.displayName}" value="${loop.index}"
selected="${fruit!=null}" staplerClass="${descriptor.clazz.name}">
"${descriptor.configPage}" from="${descriptor}"/>
This jelly, after processing, will be converted to the following html structure.
"setting-leftspace">
"setting-name">Fruits
"setting-main">
"setting-input dropdownList">
"0">Apple
"1">Banana
"setting-no-help">
"dropdownList-container">
"2">
"2">
"100%" name="fruit">
"dropdownList-start rowvg-start">
"dropdownList-end rowvg-end">
"dropdownList-start rowvg-start" style="display: none;" field-disabled="true">
"dropdownList-end rowvg-end">
Notice that the name specified on the dropdownList jelly tag is set as the name for the table control that contains the html block for the current dropdown selection. The select element doesn't have any identifier. This is not a problem when doing a submit/save as the html controls are parsed and the data is formatted to json before it is sent to the server. From the formatted data it will be possible to identify the current selection in the dropdown. But in case of validation, say I have to validate some behavior depending on the current selection in the dropdown, there is no way to get the current selection as the select element doesn't have a name attribute. https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls - clearly states that there should be a name associated with the input control, for it to be sent to the server for validation. I believe this is because validate uses the html form submit to pass data to the server, which would in turn do a lookup of html controls with the specified name.
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title
Sridevi Sangaiah updated an issue
Jenkins / JENKINS-38224
The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Change By:
Sridevi Sangaiah
Comment:
I realized that when creating this enhancement I mentioned Id attribute instead of name attribute. Fixed it now. Sorry for the confusion. Explaining the requested enhancement with more details, below.Copying below a snippet from https://github.com/jenkinsci/ui-samples-plugin/blob/master/src/main/resources/jenkins/plugins/ui_samples/DropdownList/index.jelly selected="${fruit!=null}" staplerClass="${descriptor.clazz.name}"> This jelly, after processing, will be converted to the following html structure. Fruits AppleBanana Notice that the name specified on the dropdownList jelly tag is set as the name for the table control that contains the html block for the current dropdown selection. The select element doesn't have any identifier. This is not a problem when doing a submit/save as the html controls are parsed and the data is formatted to json before it is sent to the server. From the formatted data it will be possible to identify the current selection in the dropdown.But in case of validation, say I have to validate some behavior depending on the current selection in the dropdown, there is no way to get the current selection as the select element doesn't have a name attribute. https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls - clearly states that there should be a name associated with the input control, for it to be sent to the server for validation. I believe this is because validate uses the html form submit to pass data to the server, which would in turn do a lookup of html controls with the specified name.
Add Comment
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title
Sridevi Sangaiah commented on JENKINS-38224
Re: The html select element added by the dropdownlist.jelly form control needs to have a name attribute
I realized that when creating this enhancement I mentioned Id attribute instead of name attribute. Fixed it now. Sorry for the confusion. Explaining the requested enhancement with more details, below. Copying below a snippet from https://github.com/jenkinsci/ui-samples-plugin/blob/master/src/main/resources/jenkins/plugins/ui_samples/DropdownList/index.jelly" varStatus="loop"> "/> " value="$ {loop.index} " selected="$ {fruit!=null} " staplerClass="$ {descriptor.clazz.name} "> " from="$ {descriptor} "/>This jelly, after processing, will be converted to the following html structure. Fruits Apple BananaHere goes the html when Apple is selected-> Here goes the html when Banana is selected-> Notice that the name specified on the dropdownList jelly tag is set as the name for the table control that contains the html block for the current dropdown selection. The select element doesn't have any identifier. This is not a problem when doing a submit/save as the html controls are parsed and the data is formatted to json before it is sent to the server. From the formatted data it will be possible to identify the current selection in the dropdown. But in case of validation, say I have to validate some behavior depending on the current selection in the dropdown, there is no way to get the current selection as the select element doesn't have a name attribute. https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls - clearly states that there should be a name associated with the input control, for it to be sent to the server for validation. I believe this is because validate uses the html form submit to pass data to the server, which would in turn do a lookup of html controls with the specified name.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title
Sridevi Sangaiah updated an issue
Jenkins / JENKINS-38224
The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Change By:
Sridevi Sangaiah
Comment:
I realized that when creating this enhancement I mentioned Id attribute instead of name attribute. Fixed it now. Sorry for the confusion. Explaining the requested enhancement with more details, below.Copying below a snippet from [https://github.com/jenkinsci/ui-samples-plugin/blob/master/src/main/resources/jenkins/plugins/ui_samples/DropdownList/index.jelly] {{selected="${fruit!=null}" staplerClass="${descriptor.clazz.name}"> }}This jelly, after processing, will be converted to the following html structure. {{Fruits AppleBanana }} Notice that the name="fruit" specified on the dropdownList jelly tag is set as the name for the table control that contains the html block for the current dropdown selection. The select element doesn't have any identifier. This is not a problem when doing a submit/save, as the html controls are parsed and the data is formatted to json before it is sent to the server. From the formatted data it will be possible to identify the current selection in the dropdown.But in case of validation, say I have to validate some behavior depending on the current selection in the dropdown, there is no way to get the current selection as the select element doesn't have a name attribute. [https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls] - clearly states that there should be a name associated with the input control, for it to be sent to the server for validation. I believe this is because validate uses the html form submit to pass data to the server, which would in turn do a lookup of html controls with the specified name.
Add Comment
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title
Sridevi Sangaiah commented on JENKINS-38224
Re: The html select element added by the dropdownlist.jelly form control needs to have a name attribute
I realized that when creating this enhancement I mentioned Id attribute instead of name attribute. Fixed it now. Sorry for the confusion. Explaining the requested enhancement with more details, below. Copying below a snippet from [https://github.com/jenkinsci/ui-samples-plugin/blob/master/src/main/resources/jenkins/plugins/ui_samples/DropdownList/index.jelly ] {{ " varStatus="loop"> "/> " value="$ {loop.index} " selected="$ {fruit!=null} " staplerClass="$ {descriptor.clazz.name} "> " from="$ {descriptor} "/> }} This jelly, after processing, will be converted to the following html structure. {{ Fruits Apple BananaHere goes the html when Apple is selected-> Here goes the html when Banana is selected-> }} Notice that the name="fruit" specified on the dropdownList jelly tag is set as the name for the table control that contains the html block for the current dropdown selection. The select element doesn't have any identifier. This is not a problem when doing a submit/save, as the html controls are parsed and the data is formatted to json before it is sent to the server. From the formatted data it will be possible to identify the current selection in the dropdown. But in case of validation, say I have to validate some behavior depending on the current selection in the dropdown, there is no way to get the current selection as the select element doesn't have a name attribute. [ https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls] - clearly states that there should be a name associated with the input control, for it to be sent to the server for validation. I believe this is because validate uses the html form submit to pass data to the server, which would in turn do a lookup of html controls with the specified name.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title Sridevi Sangaiah updated an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have a name attribute Change By: Sridevi Sangaiah The html select element added by the dropdownlist.jelly form control needs to have an id a name attribute. In the validation flow, unlike save, the data submitted is not formatted. So, without the id attribute it is not possible to get the current selection in the validation flow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title Sridevi Sangaiah updated an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have a name attribute Change By: Sridevi Sangaiah Summary: The html select element added by the dropdownlist.jelly form control needs to have an id a name attribute Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have a name attribute
Title: Message Title Sridevi Sangaiah updated an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have a name attribute Change By: Sridevi Sangaiah The html select element added by the dropdownlist.jelly form control needs to have a name attribute. In the validation flow, unlike save, the data submitted is not formatted. So, without the id name attribute it is not possible to get the current selection in the validation flow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have an id attribute
Title: Message Title Sridevi Sangaiah updated an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have an id attribute Change By: Sridevi Sangaiah The html select element added by the dropdownlist.jelly form control need needs to have an id attribute. In the validation flow, unlike save, the data submitted is not formatted. So, without the id attribute it is not possible to get the current selection in the validation flow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38224) The html select element added by the dropdownlist.jelly form control needs to have an id attribute
Title: Message Title Sridevi Sangaiah created an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have an id attribute Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Sep/15 4:36 AM Priority: Minor Reporter: Sridevi Sangaiah The html select element added by the dropdownlist.jelly form control need to have an id attribute. In the validation flow, unlike save, the data submitted is not formatted. So, without the id attribute it is not possible to get the current selection in the validation flow Add Comment
[JIRA] [teamconcert-plugin] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Sridevi Sangaiah commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure Is the build toolkit configured in the slave node? If not, I believe it should be available in the same path as in the master. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in [#388284 https : Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1 //jazz . 655] net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388284. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in [# 388284: Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1.655 ] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in [ 388284: Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1.655 #https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388284] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah commented on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in 388284: Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1.655#https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388284 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
