See this post about this change in behavior, it was made for security reasons. https://www.jenkins.io/blog/2016/05/11/security-update/
On Fri, Dec 11, 2020 at 7:12 AM Fabian Cenedese <[email protected]> wrote: > At 14:30 11.12.2020, Slide wrote: > > >You need to give more information about what version you are upgrading > from and upgrading to. Be aware that moving from Jenkins 1.x to a recent > 2.x is NOT a drop-in replacement, can you tell me where you saw this? > > Well, it doesn't mention a specific version unless it's really only 2.0[00] > https://www.jenkins.io/2.0/#compat > > >The last Jenkins 1.x release was over 4 years ago, there have been lots > of changes in that time, so expecting things to work perfect after that > amount of time is not really reasonable. You'll need to give more > information about what plugin you are using and check the logs for error > messages. It is possible you will need to rework stuff since you are moving > from 1.x to 2.x. > > Thanks for the information. I first updated to the last 1.658 and wanted to > continue from there. I checked 2.0 or so and everything still looked fine. > As the underlying linux was also ancient I decided to make a completely > new Jenkins Master with a current Ubuntu 20, install whatever Jenkins > it has in its repositories (using now 2.269) and copy the whole Jenkins > home folder from the old master over to the new. > Of course the plugins were now all old and I had to update them as > well. Apart from that it was quite effortless. > > I checked the log and found messages like this: > > Skipped parameter `FW_VERSION` as it is undefined on > `FW_GENERIC_Copy2Desktop`. Set > `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow > undefined parameters to be injected as environment variables or > `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to > whitelist specific parameter names, even though it represents a security > breach or `-Dhudson.model.ParametersAction.keepUndefinedParameters=false` > to no longer show this message. > > I'm not sure if one of these arguments would help in my case or if it > would rather mask the problem. If the problem is easily solvable > then I can apply it to the current system. If not then I can also start > over again as I still have the old one and if you can tell me the best > way to go about. > > Thanks > > bye Fabi > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/20201211141142.D58CE43764DA%40macserver.private > . > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcRpZzAnCvpGoUCiM2LqM6%3DbUeckF9%2ByBtNTDw1OAuTyg%40mail.gmail.com.
