W00t! This is super awesome. Thank you so much!!! On Sun, Apr 4, 2021 at 2:22 PM Ismael Juma <ism...@juma.me.uk> wrote:
> Hi all, > > As part of KAFKA-12614 <https://issues.apache.org/jira/browse/KAFKA-12614 > >, > I have created a Jenkinsfile-based job for trunk, 2.8 and future release > branches: > > https://ci-builds.apache.org/job/Kafka/job/kafka/ > > This has several advantages (many of these are already the case for PR > builds): > > 1. The configuration is in source control. > 2. PR and branch build configuration share most of the logic. > 3. Unstable (tests failed) and unsuccessful (compile, checkstyle, etc. > failed) builds are given different status and color (red vs amber). > 4. Reporting within a build is improved (each stage is shown as part of > the build graph) > 5. Improved parallelism (each JDK+Scala combination is built in > parallel) > 6. Release branches get better JDK version coverage (instead of only JDK > 8 as it used to be) > 7. Instead of creating a new job for each new release, we can adjust the > configuration to allow the new release branch. > > There is currently an open PR <https://github.com/apache/kafka/pull/10473> > to > extend the Jenkinsfile with functionality desired for branch builds. Once > that is merged and has been shown to work correctly, I will delete legacy > Jenkins jobs like: > > - https://ci-builds.apache.org/job/Kafka/job/kafka-2.8-jdk8/ > - https://ci-builds.apache.org/job/Kafka/job/kafka-trunk-jdk11/ > > Let me know if you have questions or comments. > > Ismael > -- Gwen Shapira Engineering Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter | blog
