[all-commits] [llvm/llvm-project] 2c1af7: [Green Dragon] add green dragon jenkinsfile defini...

[Justice Adams via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 2c1af70c0688b5518f46c617a5ffa443e22ba522
      https://github.com/llvm/llvm-project/commit/2c1af70c0688b5518f46c617a5ffa443e22ba522
  Author: Justice Adams <107649528+justice-adams-apple at users.noreply.github.com>
  Date:   2026-02-11 (Wed, 11 Feb 2026)

  Changed paths:
    A .ci/green-dragon/clang-san-iossim.groovy
    A .ci/green-dragon/clang-stage1-RA-as.groovy
    A .ci/green-dragon/clang-stage1-RA-cmake-incremental.groovy
    A .ci/green-dragon/clang-stage1-RA-expensive.groovy
    A .ci/green-dragon/clang-stage1-RA.groovy
    A .ci/green-dragon/clang-stage2-Rthinlto.groovy
    A .ci/green-dragon/clang-stage2-cmake-RgSan.groovy
    A .ci/green-dragon/clang-stage2-cmake-RgTSan.groovy
    A .ci/green-dragon/lnt-ctmark-aarch64-O0-g.groovy
    A .ci/green-dragon/lnt-ctmark-aarch64-O3-flto.groovy
    A .ci/green-dragon/lnt-ctmark-aarch64-Os.groovy
    A .ci/green-dragon/lnt-ctmark-aarch64-Oz.groovy
    A .ci/green-dragon/relay-clang-stage2-sanitizers.groovy
    A .ci/green-dragon/relay-lnt-ctmark.groovy
    A .ci/green-dragon/relay-test-suite-verify-machineinstrs.groovy
    A .ci/green-dragon/test-suite-verify-machineinstrs-aarch64-O0-g.groovy
    A .ci/green-dragon/test-suite-verify-machineinstrs-aarch64-O3.groovy
    A .ci/green-dragon/test-suite-verify-machineinstrs-aarch64-globalisel-O0-g.groovy
    A .ci/green-dragon/test-suite-verify-machineinstrs-x86_64-O0-g.groovy
    A .ci/green-dragon/test-suite-verify-machineinstrs-x86_64-O3.groovy
    A .ci/green-dragon/test-suite-verify-machineinstrs-x86_64h-O3.groovy

  Log Message:
  -----------
  [Green Dragon] add green dragon jenkinsfile definitions for multibranch pipelines (#180793)

Add CI job definitions using our new templated pipelines to
llvm-project, this way we can enable multi branch pipelines which
trigger for changes on a given branch.

By storing the Jenkinfile definitions in llvm-project, we gain the
benefit of enabling Jenkins multi branch pipelines. This means in the
future, expanding a job configuration to build with a new branch is as
simple as updating a regular expression in Jenkins (the regular
expression represents which branches should be built). The work required
for enabling testing new branches becomes minimal, and furthermore we
would have a great deal of confidence that job configurations across
branches remain identical.


I will verify these new jenkinsfiles work before deprecating the old
definitions in zorg



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications