Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
X
xwiki-platform
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
XWiki
xwiki-platform
Commits
71af726e
Commit
71af726e
authored
4 years ago
by
Vincent Massol
Browse files
Options
Downloads
Patches
Plain Diff
[Misc] Don't run docker-all outside non weekends, see code comments for explanations
parent
405a9e65
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Jenkinsfile
+8
-2
8 additions, 2 deletions
Jenkinsfile
with
8 additions
and
2 deletions
Jenkinsfile
+
8
−
2
View file @
71af726e
...
...
@@ -217,7 +217,7 @@ private void buildStandardAll(builds)
// Run the quality checks
builds
[
'Quality'
].
call
()
}
/* TODO: 27/4/2020: Disable sonar build to check the hyp
p
theis that it's causing kills on agents by using too
/* TODO: 27/4/2020: Disable sonar build to check the hyp
o
the
s
is that it's causing kills on agents by using too
much memory.
,
'sonar': {
...
...
@@ -339,11 +339,17 @@ private def getCustomJobProperties()
// Note: it's the xwikiBuild() calls from the standard builds that will set the jobProperties and thus set up the
// job parameter + the crons. It would be better to set the properties directly in this Jenkinsfile but we haven't
// found a way to merge properties and calling the properties() step will override any pre-existing properties.
//
// Notes:
// - We use @midnight so that Jenkins doesn't execute all jobs from various branches at the same time
// - We don't use @weekly for docker-all since we want them to execute on weekends only so that they don't execute
// at the same time as docker-latest during standard week days, as it'll mean that all agents will be used and
// be available for standard builds during the working days.
return
[
parameters
([
string
(
defaultValue:
'standard'
,
description:
'Job type'
,
name:
'type'
)]),
pipelineTriggers
([
parameterizedCron
(
'''@midnight %type=docker-latest
@weekly
%type=docker-all
H 0 * * 6
%type=docker-all
@monthly %type=docker-unsupported'''
),
cron
(
"@monthly"
)
])
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment