[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Ioannis Moutsatsos now I noticed, you were using the `projectName` property of the parameter. That is a helper variable, used when the project is created via its constructor. But if it is loaded via serializer/Stapler/etc, then I am not sure if the constructor will always be called. There is a logic that tries to use that variable, but when it is not found, we fallback to locating a project with a parameter UUID (every active choices has a random UUID). However, we do not save the project to `projectName`. For the current implementation - which is a bit complex, and may need to improvements - the best way to access the Jenkins project is via the variable `jenkinsProject`, that the plugin populates automatically. Tried with a groovy script that returned `return [jenkinsProject.name]`, and it worked before & after renaming the project. Hope that makes sense? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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-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-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Ioannis Moutsatsosuno-choice.hpi as promised, here's the hpi Just checked out the project and `mvn clean package`'d. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita commented on JENKINS-51296 Re: Project renaming is not propagated to Active Choices projectName Fixed in pull request 20 by sebcworks (thanks!) https://github.com/jenkinsci/active-choices-plugin/pull/20 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName
Title: Message Title Bruno P. Kinoshita updated JENKINS-51296 Jenkins / JENKINS-51296 Project renaming is not propagated to Active Choices projectName Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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
