|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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/groups/opt_out.
Ok guys, so the main issue we are having with this is backwards comparability (aka, still support the System Property setting from before and not crash people's already-existing builds that assumed the property to be on).
I'm on the side that the SysProp was hacky to begin with so it shouldn't be supported (people that are currently using it would need to configure their builds and check the "do not fail on empty" checkbox). We could write somewhere that this needs to be done.
Or we could continue to support it (have a duality of new and old builds). If this option, it would be best to automatically transfer people to the new system (by simply hitting "configure" and then save. It would be a simple config.xml change). The issue with this is that it requires code that will only really be used once (for the transfer) and then never used again.
Again, I'm for the former, but I can see the argument for the latter given that it is commonly used (not sure how many people are using the SysProp though).
What do you guys think?