[JIRA] (JENKINS-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title James Murphy commented on JENKINS-41583 Re: job-dsl-plugin is not able to generate paramters is template has empty parameter list. Trying to recreate from scratch using scripts that I can send you, but now in the current version of Jenkins it does not let me create a template project with an empty parameters list anymore. i get the error: Error No Parameters are specified for this parameterized build My original template was created way back when I had Jenkins 1.452 installed and then we have upgraded several times since (and recently upgraded the Job DSL Plugin). Doesn't look like I will be able to reproduce this error and is probably not something that needs to be addressed in current version. Thank you for you time looking into this, we can probably close it. 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-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title James Murphy updated an issue Jenkins / JENKINS-41583 job-dsl-plugin is not able to generate paramters is template has empty parameter list. Change By: James Murphy Attachment: screenshot-1.png 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-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title James Murphy created an issue Jenkins / JENKINS-41583 job-dsl-plugin is not able to generate paramters is template has empty parameter list. Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2017/Jan/31 1:25 AM Environment: job-dsl-plugin 1.57 jenkins version 2.32.1 RHEL 7.2 Priority: Minor Reporter: James Murphy After upgrading Jenkins DSL plugin from 1.47 to 1.57, noticed that my jobs parameters list were empty if the templates being used had the "this build is parameterized" but did not have any parameters listed in the template. However, if the template does not have that check box marked, then the DSL plugin is able to process the parameters that are passed in and create the job with all the parameters. This is minor as the workaround is to not have any empty parameters list in the template, but was annoying to try and figure out why my parameters were missing all of a sudden after upgrading the plugin. Thought it would be good to document it somewhere in case others run into the same issue.
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches I downloaded and built the plugin from the master stream. After loading the pre-release plugin into Jenkins plugins, seems to be working fine. Thanks Mark. 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy edited a comment on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches I downloaded and built the plugin from the master stream branch . After loading the pre-release plugin into Jenkins plugins, seems to be working fine. Thanks Mark. 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Hi Mark, No special reason, it was the previously installed version, and I had known it was working then (plus the downgrade to previously installed version button was conveniently there). Also we were against a deadline, and choose to downgrade instead of going through all the commits searching for messages that had newlines, and that second link you posted to download the build from is no longer pointing to an existing artifact... 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Hi, We hit the same issue during one of our builds, wanted to add that we were able to downgrade the git client plugin back to 1.8.1 to bypass the issue. Not sure how to go back and search each commit that happened for a new line in our case the culprit commit is not the most recent, so we would need to go back and update ones that happened several commits ago... not sure how to do that yet 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] [parameterized-trigger-plugin] (JENKINS-34954) Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin
Title: Message Title James Murphy commented on JENKINS-34954 Re: Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin Hi, I think I am hitting the same issue. I am using Jenkins for our Continuous Integration Pipeline and over the weekend the Jenkins Master upgraded itself from 1.651.1 to 1.651.2, and several of our jobs that are using the parameterized trigger plugin are now failing. While I can revert back to 1.651.1, I am wondering what the solution going forward should be? Right now I have a shell script that runs in JobA, it creates a bunch of variables (for example, location to some of the build artifacts stored on an external file server) and pipes them to a file that I later pass to JobB using "Parameters from properties file". This works extremely well for us because we don't necessarily need to create the parameters in JobB before hand, as long as JobA passes them in via the properties file. Since I see there appear to be several people hitting the same issue with the parameterized trigger pluggin after upgrade to 1.651.2 or greater, I am wondering if there will be some fix to revert back the requirement that the job that is being triggered must pre-define/declare the parameters before they can be passed in? Thanks! 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.
