[
https://issues.apache.org/jira/browse/SLING-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715873#comment-17715873
]
Konrad Windszus commented on SLING-11843:
-----------------------------------------
Not sure this would help to be honest. Even with the current config we have
quite some modules failing in Jenkins
(https://ci-builds.apache.org/job/Sling/view/Monitor/) and no one seems to
really care. Not sure what you propose how long to wait after each step. IMHO
the Jenkins build exposes clearly where the failure occurred so I would
actually prefer to fix each module only once (instead of once per baby step),
therefore I would rather change the defaults in one commit.
> Change Default JDK/OS for Jenkins Builds to JDK11/17 on Unix/Windows
> --------------------------------------------------------------------
>
> Key: SLING-11843
> URL: https://issues.apache.org/jira/browse/SLING-11843
> Project: Sling
> Issue Type: Improvement
> Components: CI
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Currently our Jenkins jobs by default only run on JDK8 with Linux.
> I would propose to change the default (mentioned in
> https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor#Slingmoduledescriptor-DefaultValues)
> to
> * Build with JDK 11 and 17 on
> * Windows and Linux
> Although this might break some builds, I think it is time now to make all
> modules compatible with it once we touch it for whatever reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
