Commit 4dcc0e55 authored by Thomas  MENARD's avatar Thomas MENARD
Browse files

Update .gitlab-ci.yml

parent f361b34c
Pipeline #9694 passed with stage
in 2 minutes and 29 seconds
......@@ -39,6 +39,7 @@ cache:
- 'mvn $MAVEN_CLI_OPTS install'
- ls -l $CI_PROJECT_DIR/target
artifacts:
name: LocalZProjector
paths:
- $CI_PROJECT_DIR/target/LocalZProjector-1.0.1-SNAPSHOT.jar
  • Ok this is where I have an issue: What will happen when I will release version 2.3.4? I will have to edit the gitlab-ci file?

    Is there a way to automate this? Such as in the gitlab-ci file grabbing the name of the jar compiled? @tmenard

    Edited by Jean-Yves TINEVEZ
Please register or sign in to reply
......
  • In that case you create gitlab tags and instead of just defining the name with a static name, you use something like : name: LocalZProjector-${CI_COMMIT_TAG}

    But the name will not be predictable....

  • Right Ok, I see how you would do CI in a proper way:

    • During devel on SNAPSHOTs: Have a job triggered for each commit: Just compiles and check that there are no errors.

    • Ready for release: Make a tag, and the CI will catch, compile and deploy it with this trick.

    How can we do that? Is this possible?

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