> Is a Jenkins rebuild > going to happen once the > https://github.com/apache/sling-tooling-jenkins/pull/16 is merged or > will the potential failures be exposed once a new CI job runs? > No, not automatically. But either through a dedicated build (due to some commits in the affected module repository) or latest through the automatic weekly build (https://github.com/apache/sling-tooling-jenkins/blob/a9f5de4236ed657118a9561e3367c107856a72ef/vars/slingOsgiBundleBuild.groovy#LL64C56-L64C56) it will be triggered. I don’t think there is the need to rebuild all Modules immediately after this change (also to not overload the ASF Jenkins). Konrad
- Automatically build on ASF Jenkins with Java 11/17 on Linu... Konrad Windszus
- RE: Automatically build on ASF Jenkins with Java 11/1... Stefan Seifert
- Re: Automatically build on ASF Jenkins with Java 11/1... Robert Munteanu
- RE: Automatically build on ASF Jenkins with Java ... Stefan Seifert
- Re: Automatically build on ASF Jenkins with J... Robert Munteanu
- RE: Automatically build on ASF Jenkins wi... Stefan Seifert
- Re: Automatically build on ASF Jenki... Robert Munteanu
- Re: Automatically build on ASF Jenkins with Java ... Konrad Windszus
- Re: Automatically build on ASF Jenkins with J... Robert Munteanu
- Re: Automatically build on ASF Jenkins with Java 11/1... Konrad Windszus
- Re: Automatically build on ASF Jenkins with Java 11/1... Robert Munteanu
- Re: Automatically build on ASF Jenkins with Java ... Konrad Windszus
- Re: Automatically build on ASF Jenkins with J... Robert Munteanu
