Proposal: Jenkins baseline selection

[Ullrich Hafner]

In our developer documentation we currently have a very vague description on how to select the Jenkins baseline: https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/

Recently a lot of my builds failed (my baseline was 2.204.4) because some frequently used base plugins updated their minimum Jenkins version to a higher LTS minor version (like 2.222.1) or a higher patch version (2.204.6).

So I thought it would make sense to make the baseline selection more concrete:
https://github.com/jenkins-infra/jenkins.io/pull/3630

Note that it still might sense to use newer versions when a plugin requires some modern core features. So this section should provide a suggestion only for those plugins that actually have no strict Jenkins core dependency.

What do you think? Does it make sense?

[Gavin Mogan]

Mark often replies with a string like that, so i like it being on jenkins.io +1 from me

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CBD37C05-163D-4701-9CF1-86A687E45BD0%40gmail.com.

[Mark Waite]

+1 from me.  I like the recommendations very much.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutgBhwmUTQ3WO65xdDbcZExeS1hDyPO6zj%2BA5pC5AgwYA%40mail.gmail.com.

[Daniel Beck]

> On 12. Aug 2020, at 19:13, Ullrich Hafner <ullrich...@gmail.com> wrote:
>
> Recently a lot of my builds failed (my baseline was 2.204.4) because some frequently used base plugins updated their minimum Jenkins version to a higher LTS minor version (like 2.222.1) or a higher patch version (2.204.6).

I'm interested in understanding exactly what you're doing -- update sites since May should offer exactly the versions of plugins compatible with your chose core version unless it's older than a year.

[Ullrich Hafner]

The build does not break because a version is not available, it breaks because of insufficient version constraints:
- maven-enforcer complains
- integration tests do not start a plugin because they require a newer core version
- ATH does not install plugins because they require a newer core version