2c1af70c06
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
19 lines
629 B
Groovy
19 lines
629 B
Groovy
branchName = 'main'
|
|
|
|
library identifier: "zorg-shared-lib@${branchName}",
|
|
retriever: modernSCM([
|
|
$class: 'GitSCMSource',
|
|
remote: "https://github.com/llvm/llvm-zorg.git",
|
|
credentialsId: scm.userRemoteConfigs[0].credentialsId
|
|
])
|
|
|
|
common.testsuite_pipeline(label: 'macos-x86_64') {
|
|
timeout(30) {
|
|
sh """
|
|
LNT_FLAGS+=" -C config/tasks/cmake/caches/target-arm64-iphoneos.cmake"
|
|
LNT_FLAGS+=" -C config/tasks/cmake/caches/opt-Oz.cmake"
|
|
config/tasks/task jenkinsrun config/tasks/lnt-ctmark.sh -a compiler="${params.ARTIFACT}" -D LNT_FLAGS="\${LNT_FLAGS}"
|
|
"""
|
|
}
|
|
}
|