Can the coresdk agent support .NET 6 and .NET 7?

[tianxin8206]

What feature do you want to see added?

Can the coresdk agent support .NET 6 and .NET 7?

Upstream changes

No response

[dduportal]

Hi @tianxin8206 , the Platform SIG meeting of Jenkins has started a discussion about stopping to provide agent images other than the base ones (jenkinsci/agent, jenkinsci/inbound-agent and jenkinsci/ssh-agent) for maintainenance reasons.

The main reason is because we lack maintainers. If this feature request is important to you, I'm siuggesting you to send a Pull Request and to help maintaining these (or ask someone you know who could be interested)

[tianxin8206]

Ok, I'll send a pr.

[dduportal]

Some important elements are to be covered:

• What design should be used at code level: adding duplicated Dockerfile is not acceptable because changing an element in one will requires duplicating the effort on each.
  • Could build-arg be a solution?
• What are the expected tags of these new versions?
• What is the LTS/support status of .NET version (current, 6 and 7)?
• What is the update lifecycle? Do we accept rebuilding and overridng the images to always have the latest 6.x and 7.x available (and not the older versions)?

[tianxin8206]

@dduportal Reply to your questions:

• Adding build-arg is a good idea. Do we need to add a separate Makefile under coresdk and maintain a version list?

• .NET 6.0 is the LTS version and will be supported until November 12, 2024. .NET 7.0 is a standard term support version and will be supported until May 14, 2024.

• Regarding image tags and lifecycle, currently, the latest .NET image version is used as a dependency. If we accept the rebuilding and overriding images, we need to maintain the minor versions of .NET releases in the version list, which will require some effort.