Windows: Update default jenkins version to 2.410

[Jonny-vb]

Update default jenkins version.

Based on #1490 the windows docker version is lagging behind.
The current version provided (2.356) gives the following issues:

So this is a quick fix to resolve the vulnerabilities in the current issue, before any work is done to actually fix the build process.

Testing done

Submitter checklist

Preview Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[Jonny-vb]

Hi @dduportal , @timja - is there anything else required to get this merged? Perhaps all the default versions should be bumped at the same time (like in commit 4d817e0)?
If not I am keen to get this merged so that I can remove the long standing warnings I've had on my instance!

[dduportal]

Hi @Jonny-vb Thansk for this PR!

It make sense to fix "now" and change the default value to all Dockerfile:

• For coherency between Linux and Windows images
• To ensure all Windows images are updated at once (all available JDK and Windows distributions)

Are you ok to do this here?

[Jonny-vb]

Hi @dduportal - yep makes sense - additional changes made. I realised the source branch name doesn't make sense now either though - is that okay or do you want me to create a new PR with a better name?

[dduportal]

No worries about the soure branch name. The PR title is the important thing as it will be both commit and changelog message once merged.

thanks for the change !

[dduportal]

LGTM thanks!

[Jonny-vb]

Thanks for merging - one last thing - what actually triggers the builds? I have a feeling that might rely on a new jenkins tag being published, which means a wait until this change gets through to the windows docker image. Is there any change it could be manually started to get this through?

[dduportal]

Thanks for merging - one last thing - what actually triggers the builds? I have a feeling that might rely on a new jenkins tag being published, which means a wait until this change gets through to the windows docker image. Is there any change it could be manually started to get this through?

Hi @Jonny-vb you are correct, since #1630 the builds are triggered when a tag is created, during Jenkins releases.
As they are no such thing as "latest available image", and since the process should not rebuild a given tag, you'll have to wait tomorrow's weekly release to see the image published.

Once we'll fix the full windows build, though, we should be able to run a few manual builds to only build latest Weekly and LTS (but we need a fully fixed build first).

[Jonny-vb]

Just to confirm that the new windows image has been published using 2.410 as intended.

[dduportal]

Just to confirm that the new windows image has been published using 2.410 as intended.

Oooh cool you rock ! Thanks for confirmation. I’ll bring this subject to the platform SIG meeting today to pave the way for next steps