Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
C
ci-tooling
Project overview
Project overview
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
1
Issues
1
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Sysadmin
ci-tooling
Commits
f05bd93b
Commit
f05bd93b
authored
Dec 06, 2018
by
Ben Cooksley
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Start implementing support for separate Pipelines for different Products
parent
f331ca13
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
12 additions
and
1 deletion
+12
-1
dsl/standardjobs.groovy
dsl/standardjobs.groovy
+1
-1
helpers/gather-jobs.py
helpers/gather-jobs.py
+11
-0
No files found.
dsl/standardjobs.groovy
View file @
f05bd93b
...
...
@@ -12,7 +12,7 @@ knownJobs.each {
folder
(
"${it.product}/${it.name}"
)
// Read in the necessary Pipeline template
def
pipelineTemplate
=
readFileFromWorkspace
(
"
pipeline-templates/${it.platform}.template
"
)
def
pipelineTemplate
=
readFileFromWorkspace
(
"
${it.pipelineTemplate}
"
)
// Now we can construct our Pipeline script
// We append a series of variables to the top of it to provide a variety of useful information to the otherwise templated script
// These appended variables are what makes one build different to the next, aside from the template which was used
...
...
helpers/gather-jobs.py
View file @
f05bd93b
...
...
@@ -92,6 +92,16 @@ for product in productHandler.knownProducts():
unstableBuildEmails
=
productHandler
.
notificationsFor
(
product
,
project
,
failuresOnly
=
False
)
unstableBuildEmails
=
', '
.
join
(
unstableBuildEmails
)
# Determine the pipeline we should be using
# Start with a generic template
pipeline
=
"pipeline-templates/{platform}.pipeline"
.
format
(
platform
=
platform
)
# Do we have a product specific one?
# If so, make sure we use it
productPipeline
=
"pipeline-templates/{product}/{platform}.pipeline"
.
format
(
product
=
product
,
platform
=
platform
)
if
os
.
path
.
exists
(
productPipeline
):
pipeline
=
productPipeline
# We have a winner!
jobEntry
=
{
'name'
:
project
.
name
,
...
...
@@ -101,6 +111,7 @@ for product in productHandler.knownProducts():
'branch'
:
branchToBuild
,
'branchGroup'
:
branchGroup
,
'platform'
:
platform
,
'pipelineTemplate:'
pipeline
,
'description'
:
project
.
description
,
'environment'
:
arguments
.
environment
,
'buildFailureEmails'
:
buildFailureEmails
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment