Updated .gitlab-ci.yml and pom.xml
This commit is contained in:
1 parent
a84e19de21
commit
68b529fa51
2 files changed
+11
-84
No files matched your search
+11
-77
@@ -1,93 +1,27 @@
|
|||||||
# This file is a template, and might need editing before it works on your project.
|
image: maven:latest
|
||||||
---
|
|
||||||
# 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:
|
variables:
|
||||||
# This will supress any download for dependencies and plugins or upload messages which would clutter the console log.
|
MAVEN_CLI_OPTS: "-s .m2/settings.xml --batch-mode"
|
||||||
# `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"
|
||||||
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:
|
cache:
|
||||||
paths:
|
paths:
|
||||||
- .m2/repository
|
- .m2/repository/
|
||||||
|
- target/
|
||||||
|
|
||||||
# This will only validate and compile stuff and run e.g. maven-enforcer-plugin.
|
build:
|
||||||
# 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
|
stage: build
|
||||||
script:
|
script:
|
||||||
- "mvn --batch-mode --errors --fail-at-end --show-version test-compile"
|
- "mvn -s .m2/settings.xml --batch-mode compile"
|
||||||
|
|
||||||
# For merge requests do not `deploy` but only run `verify`.
|
test:
|
||||||
# See https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
|
|
||||||
.verify: &verify
|
|
||||||
stage: test
|
stage: test
|
||||||
script:
|
script:
|
||||||
- "mvn --batch-mode --errors --fail-at-end --show-version verify"
|
- "mvn -s .m2/settings.xml --batch-mode test"
|
||||||
except:
|
|
||||||
- master
|
|
||||||
|
|
||||||
# Validate merge requests using JDK8
|
deploy:
|
||||||
validate:jdk8:
|
|
||||||
<<: *validate
|
|
||||||
image: maven:3.3.9-jdk-8
|
|
||||||
|
|
||||||
# Verify merge requests using JDK8
|
|
||||||
verify:jdk8:
|
|
||||||
<<: *verify
|
|
||||||
image: maven:3.3.9-jdk-8
|
|
||||||
|
|
||||||
|
|
||||||
# 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 --batch-mode --errors --fail-at-end --show-version deploy"
|
|
||||||
only:
|
|
||||||
- master
|
|
||||||
# Archive up the built documentation site.
|
|
||||||
artifacts:
|
|
||||||
paths:
|
|
||||||
- target/staging
|
|
||||||
image: maven:3.3.9-jdk-8
|
|
||||||
|
|
||||||
|
|
||||||
pages:
|
|
||||||
image: busybox:latest
|
|
||||||
stage: deploy
|
stage: deploy
|
||||||
script:
|
script:
|
||||||
# Because Maven appends the artifactId automatically to the staging path if you did define a parent pom,
|
- "mvn -s .m2/settings.xml --batch-mode deploy"
|
||||||
# you might need to use `mv target/staging/YOUR_ARTIFACT_ID public` instead.
|
|
||||||
- mv target/staging public
|
|
||||||
dependencies:
|
|
||||||
- deploy:jdk8
|
|
||||||
artifacts:
|
|
||||||
paths:
|
|
||||||
- public
|
|
||||||
only:
|
only:
|
||||||
- master
|
- master
|
||||||
@@ -13,13 +13,6 @@
|
|||||||
</properties>
|
</properties>
|
||||||
|
|
||||||
<distributionManagement>
|
<distributionManagement>
|
||||||
<repository>
|
|
||||||
<uniqueVersion>false</uniqueVersion>
|
|
||||||
<id>nn1</id>
|
|
||||||
<name>Net Neutrality</name>
|
|
||||||
<url>scp://repo/maven2</url>
|
|
||||||
<layout>default</layout>
|
|
||||||
</repository>
|
|
||||||
<downloadUrl>https://gitlab.xtremcommunity.com/nn.jar</downloadUrl>
|
<downloadUrl>https://gitlab.xtremcommunity.com/nn.jar</downloadUrl>
|
||||||
</distributionManagement>
|
</distributionManagement>
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user