Proposal: Jenkins baseline selection

[Ulli 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?


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CBD37C05-163D-4701-9CF1-86A687E45BD0%40gmail.com.

[Gavin Mogan]

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

On Wed, Aug 12, 2020 at 10:14 AM Ullrich Hafner <[hidden email]> wrote:

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?


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CBD37C05-163D-4701-9CF1-86A687E45BD0%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutgBhwmUTQ3WO65xdDbcZExeS1hDyPO6zj%2BA5pC5AgwYA%40mail.gmail.com.

[Mark Waite-2]

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

On Wed, Aug 12, 2020 at 12:03 PM 'Gavin Mogan' via Jenkins Developers <[hidden email]> wrote:

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

On Wed, Aug 12, 2020 at 10:14 AM Ullrich Hafner <[hidden email]> wrote:

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?


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CBD37C05-163D-4701-9CF1-86A687E45BD0%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutgBhwmUTQ3WO65xdDbcZExeS1hDyPO6zj%2BA5pC5AgwYA%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG9xCthcTYFc9NGkXP21h4B%3Dpe02VPuFgSbB3tNWztEyg%40mail.gmail.com.

[Daniel Beck]

> On 12. Aug 2020, at 19:13, Ullrich Hafner <[hidden email]> 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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/85CC18B2-93A6-4317-B7C5-0A0432287D3F%40beckweb.net.

[Ulli Hafner]

> Am 13.08.2020 um 07:58 schrieb Daniel Beck <[hidden email]>:
>
>
>
>> On 12. Aug 2020, at 19:13, Ullrich Hafner <[hidden email]> 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.

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7E239A62-1345-4B83-91C5-2E675CF8E972%40gmail.com.