[JIRA] (JENKINS-58667) NumberFormatException when parsing deploy url

18 views
Skip to first unread message

reiner.wirtz@ser.de (JIRA)

unread,
Jul 26, 2019, 5:41:02 AM7/26/19
to jenkinsc...@googlegroups.com
Reiner Wirtz updated an issue
 
Jenkins / Bug JENKINS-58667
NumberFormatException when parsing deploy url
Change By: Reiner Wirtz
Summary: NumNumberFormatException NumberFormatException when parsing deploy url
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

robin.jansohn@zf.com (JIRA)

unread,
Jul 26, 2019, 8:03:03 AM7/26/19
to jenkinsc...@googlegroups.com
Robin Jansohn commented on Bug JENKINS-58667
 
Re: NumberFormatException when parsing deploy url

OK, I found out what is causing the problem. In freestyle jobs the configurations are not updated automatically and the newly introduced path variable is undefined and therefore null}. As soon as the configuration is updated (it's enough to just press save without changes) the {{path variable is defined and everything works as expected.

I just took over this plugin and I do not know if this kind of problem could have been prevented somehow. Oleg Nenashev Jesse Glick maybe you can tell us more about this?

robin.jansohn@zf.com (JIRA)

unread,
Jul 26, 2019, 8:04:04 AM7/26/19
to jenkinsc...@googlegroups.com
Robin Jansohn edited a comment on Bug JENKINS-58667
OK, I found out what is causing the problem. In freestyle jobs the configurations are not updated automatically and the newly introduced {{path}} variable is undefined and therefore {{null} }
. As soon as the configuration is updated (it's enough to just press save without changes) the {{path}} variable is defined and everything works as expected.

I just took over this plugin and I do not know if this kind of problem could have been prevented somehow. [~oleg_nenashev] [~jglick] maybe you can tell us more about this?

jglick@cloudbees.com (JIRA)

unread,
Jul 26, 2019, 11:26:04 AM7/26/19
to jenkinsc...@googlegroups.com

I am afraid I know very little about this plugin.

robin.jansohn@zf.com (JIRA)

unread,
Jul 29, 2019, 3:27:02 AM7/29/19
to jenkinsc...@googlegroups.com

Jesse Glick it's more of a general question regarding Jenkins plugins. Is there any best practice to introduce new plugin configuration variables (with a default value) without needing to manually refresh freestyle job configurations?

Here's the actual commit and the line which caused the trouble because it was always null until the job configuration was updated to the new plugin version:
https://github.com/jenkinsci/deploy-plugin/commit/db254d7c8c70214c7da91308c50bedb25fbf4eb8#diff-b2a541c8af2e6626b795634cc9d7143dR48

reiner.wirtz@ser.de (JIRA)

unread,
Jul 29, 2019, 8:03:02 AM7/29/19
to jenkinsc...@googlegroups.com

I did the update to version 1.14 again and followed the hints given by Robin Jansohn.
I saved the job, which used the plugin without any changes.
Now the deploy worked again.
Thanks for the help!

reiner.wirtz@ser.de (JIRA)

unread,
Jul 29, 2019, 8:05:02 AM7/29/19
to jenkinsc...@googlegroups.com

If there is a new version available, please let me know.

jglick@cloudbees.com (JIRA)

unread,
Jul 29, 2019, 11:14:02 AM7/29/19
to jenkinsc...@googlegroups.com

Is there any best practice to introduce new plugin configuration variables (with a default value) without needing to manually refresh freestyle job configurations?

Yes. https://jenkins.io/doc/developer/persistence/

robin.jansohn@zf.com (JIRA)

unread,
Jul 29, 2019, 11:29:02 AM7/29/19
to jenkinsc...@googlegroups.com

Not sure I can follow. The introduced variable is a string and should be automatically serializable? Do you have an example where a new configuration option was introduced and did not require a manual refresh?

jglick@cloudbees.com (JIRA)

unread,
Jul 29, 2019, 12:10:11 PM7/29/19
to jenkinsc...@googlegroups.com

I probably do not know what you are really asking here. Best to ask on the dev list with a concrete example.

snoopi30@web.de (JIRA)

unread,
Aug 1, 2019, 7:16:03 AM8/1/19
to jenkinsc...@googlegroups.com
Robin Jansohn started work on Bug JENKINS-58667
 
Change By: Robin Jansohn
Status: Open In Progress

snoopi30@web.de (JIRA)

unread,
Aug 1, 2019, 7:19:08 AM8/1/19
to jenkinsc...@googlegroups.com
Robin Jansohn resolved as Fixed
 

I just released v1.15 which should solve this kind of problem. It will be available in Jenkins in the next few hours.

Change By: Robin Jansohn
Status: In Progress Resolved
Assignee: Robin Jansohn
Resolution: Fixed
Released As: https://github.com/jenkinsci/deploy-plugin/releases/tag/1.15
Reply all
Reply to author
Forward
0 new messages