-
Notifications
You must be signed in to change notification settings - Fork 1
/
.gitlab-ci.yml
119 lines (102 loc) · 3.89 KB
/
.gitlab-ci.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
---
# Build JAVA applications using Apache Maven (http://maven.apache.org)
# For docker image tags see https://hub.docker.com/_/maven/
#
# For general lifecycle information see https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
#
# This template will build and test your projects as well as create the documentation.
#
# * Caches downloaded dependencies and plugins between invocation.
# * Verify but don't deploy merge requests.
# * Deploy built artifacts from master branch only.
# * Shows how to use multiple jobs in test stage for verifying functionality
# with multiple JDKs.
# * Uses site:stage to collect the documentation for multi-module projects.
# * Publishes the documentation for `master` branch.
variables:
# This will supress any download for dependencies and plugins or upload messages which would clutter the console log.
# `showDateTime` will show the passed time in milliseconds. You need to specify `--batch-mode` to make this work.
MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=WARN -Dorg.slf4j.simpleLogger.showDateTime=true -Djava.awt.headless=true"
# As of Maven 3.3.0 instead of this you may define these options in `.mvn/maven.config` so the same config is used
# when running from the command line.
# `installAtEnd` and `deployAtEnd` are only effective with recent version of the corresponding plugins.
MAVEN_CLI_OPTS: "--batch-mode --errors --fail-at-end --show-version -DinstallAtEnd=true -DdeployAtEnd=true"
# Cache downloaded dependencies and plugins between builds.
# To keep cache across branches add 'key: "$CI_JOB_REF_NAME"'
#cache:
# paths:
# - .m2/repository
# This will only validate and compile stuff and run e.g. maven-enforcer-plugin.
# Because some enforcer rules might check dependency convergence and class duplications
# we use `test-compile` here instead of `validate`, so the correct classpath is picked up.
#.validate: &validate
# stage: build
# script:
# - 'mvn $MAVEN_CLI_OPTS test-compile'
# For merge requests do not `deploy` but only run `verify`.
# See https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
.verify: &verify
stage: test
script:
- 'mvn verify'
except:
- master
#STyle images
#maven:3.5.3-jdk-10
#maven:3.5-jdk-10
#maven:3-jdk-10
# Validate merge requests using JDK8
#validate:jdk8:
# <<: *validate
# image: maven:3-jdk-8
# Validate merge requests using JDK9
#validate:jdk9:
# <<: *validate
# image: maven:3-jdk-9
# Validate merge requests using JDK10
#validate:jdk10:
# <<: *validate
# image: maven:3-jdk-10
# Verify merge requests using JDK8
verify:jdk8:
<<: *verify
image: maven:3-jdk-8
# Verify merge requests using JDK9
#verify:jdk9:
# <<: *verify
# image: maven:3-jdk-9
# Verify merge requests using JDK10
#verify:jdk10:
# <<: *verify
# image: maven:3-jdk-10
# For `master` branch run `mvn deploy` automatically.
# Here you need to decide whether you want to use JDK7 or 8.
# To get this working you need to define a volume while configuring your gitlab-ci-multi-runner.
# Mount your `settings.xml` as `/root/.m2/settings.xml` which holds your secrets.
# See https://maven.apache.org/settings.html
#deploy:jdk8:
# # Use stage test here, so the pages job may later pickup the created site.
# stage: test
# script:
# - 'mvn $MAVEN_CLI_OPTS deploy site site:stage'
# only:
# - master
# # Archive up the built documentation site.
# artifacts:
# paths:
# - target/staging
# image: maven:3-jdk-8
#pages:
# image: busybox:latest
# stage: deploy
# script:
# # Because Maven appends the artifactId automatically to the staging path if you did define a parent pom,
# # you might need to use `mv target/staging/YOUR_ARTIFACT_ID public` instead.
# - mv target/staging public
# dependencies:
# - deploy:jdk8
# artifacts:
# paths:
# - public
# only:
# - master