Emit a warning when a plugin depends on a recent weekly

[daniel-beck]

What feature do you want to see added?

(TBH I don't know if it exists, but #2665 was hosted just two days ago and currently depends on 2.359.)

A warning should be emitted in the hosting check when a plugin depends on a recent weekly release. While there are some (limited) reasons this is needed, often it seems to be developers not understanding how this particular dependency works and unnecessarily limit who can use the plugin. https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ should be linked as documentation.

(And dependencies on older weekly releases should probably be pointed out too and that they should just be LTS, but for a different reason.)

Upstream changes

No response

[techaakritisha]

@daniel-beck I wanna work on this issue please assign to me

[MarkEWaite]

@techaakritisha we don't generally assign issues to those who are not maintainers. It has not worked well in the past.

Since you've stated your interest in the issue, you're welcome to start work on it and submit pull requests as needed to improve things.

[techaakritisha]

@MarkEWaite thank you for assigning me...

[MarkEWaite]

@MarkEWaite thank you for assigning me...

Happy to help, but unfortunately, I don't understand your comment. I'm not assigning this issue to you. I won't assign this issue to you. At least not in the sense that I use "assign a GitHub issue".

When I say, "assign a GitHub issue", I mean that the "assignee" in the top right corner of the GitHub issue would show your name. I won't do that because it rarely works positively for the Jenkins project. When we've assigned issues to people that are not maintainers, they very often abandon the effort without completing it and then they fail to tell us that they are abandoning the effort. We are then left with an issue that no one else considers (because it is already assigned to someone).

[techaakritisha]

yeah got it and sorry for misunderstanding