Commit 0c251a47 authored by CS_Birb's avatar CS_Birb Committed by CS_Birb

Let's try some CI/CD

parent 25b5bcac
# Build JAVA applications using Apache Maven (
# For general lifecycle information see
# This template will build and test your projects
# * Caches downloaded dependencies and plugins between invocation.
# * Verify but don't deploy merge requests.
# * Deploy built artifacts from master branch only.
# This will suppress 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: "-Dhttps.protocols=TLSv1.2 -Dmaven.repo.local=.m2/repository -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: " -s .m2/settings.xml --batch-mode --errors --fail-at-end --show-version -DinstallAtEnd=true -DdeployAtEnd=true"
# This template uses jdk8 for verifying and deploying images
image: maven:3.6-jdk-8
# Cache downloaded dependencies and plugins between builds.
# To keep cache across branches add 'key: "$CI_JOB_NAME"'
- .m2/repository
- target
# For merge requests do not `deploy` but only run `verify`.
# See
.verify: &verify
stage: test
- 'mvn $MAVEN_CLI_OPTS verify'
- master
# Verify merge requests using JDK8
<<: *verify
# For `master` branch run `mvn deploy` automatically.
stage: deploy
- 'mvn $MAVEN_CLI_OPTS deploy'
when: manual
<name>Massivecraft Deployment Dependencies</name>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment