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
31 lines
722 B
Groovy
31 lines
722 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
|
|
])
|
|
|
|
clangPipeline(
|
|
jobName: env.JOB_NAME,
|
|
zorgBranch: branchName,
|
|
buildConfig: [
|
|
stage: 1,
|
|
build_type: 'cmake',
|
|
cmake_type: 'default',
|
|
assertions: true,
|
|
projects: 'clang',
|
|
timeout: 150,
|
|
incremental: true
|
|
],
|
|
testConfig: [
|
|
test_type: 'testlong',
|
|
timeout: 150,
|
|
junit_patterns: [
|
|
"clang-build/**/testresults.xunit.xml"
|
|
]
|
|
]
|
|
)
|
|
|