Skip to content

Latest commit

 

History

History
104 lines (88 loc) · 3.79 KB

exercise-005.md

File metadata and controls

104 lines (88 loc) · 3.79 KB

Exercise 005 - Deploy to Nexus, and bump the version

After build and test are successful it is time to create a deployment to some artifactory. In the training Nexus is used. Storing it in an artifactory helps to distribute and share software with others.

Create the deployment job.

The goal here is to place an artifact in Nexus and also make a tag in the source control system to make visible what the version contains. To achieve this, take these steps:

  • Extend the pipeline.yml file with a new job called deploy. This job consists of 3 tasks, getting the sources, tag, version bump and deploy to nexus step and pushing the changes to git.
- name: deploy # Name of the job
  serial: true # No parallel execution of the plan
  plan:
  - get: sources # Download the sources
    trigger: true
    passed: [test] # Trigger after job test has passed
  - task: tag, publish and publish new version
    file: sources/CI/task-deploy.yml
  - put: sources-write
    params: {repository: sources-output} # Push latest version after tagging en version bump
  • Add a new resource for writing to the pipeline.yml, this is because the [ci skip] is not honored within a pipeline.
- name: sources-write # Name of the resource
  type: git # Resource type
  source:
    uri: git@github.com:Hylke1982/DevOpsTraining.git
    private_key: ((private-repo-key))
    branch: master
  • Create a new task definition for tag, version bump and deploy in the CI directory, with the file name task-deploy.yml. In this task a release version is created and published into Nexus, an empty commit is created for the version bump and the version is stored in the Consul key-value store for later usage. The contents of this file should be:
platform: linux

image_resource:
  type: docker-image
  source: {repository: openjdk, tag: 8}

inputs:
- name: sources

outputs:
- name: sources-output # Output to special name space
- name: new-version

caches:
  - path: ["sources/application/build","sources/application/.gradle"]

run: # Gradle release + version bumping
  path: sh
  args:
  - -exc
  - |
    git config --global user.email "concourse@build.com"
    git clone sources sources-output
    cd sources-output/application
    ./gradlew printVersion
    ./gradlew tag -Prelease build uploadArchives
    ./gradlew printVersion
    git commit --allow-empty -a -m "[ci skip] version bump"
    ./gradlew -PbumpComponent=patch
    ./gradlew printVersion
    git status
    VERSION=$(git describe --abbrev=0 --tags)
    echo $VERSION
    curl -X PUT -d "$VERSION" http://consul.service.consul:8500/v1/kv/version
  • Commit the changes and push them
  • After a few moments a new build is triggered
  • Update the pipeline with $ fly -t lite set-pipeline -p devops-training -c pipeline.yml --load-vars-from secrets.yml
  • A script is executed within in the run section of the tasks, which basically creates a for the version, uploads the artifact to artifactory and bumps the version. A output is used to store the changes and these changes are then pushed to the git repository
  • Open nexus to view the published artifact. Nexus release
  • Also view the git log for the tags Git tags

Additional notes

It could be that the task fails, because the tag already exists for example. A good way to correct is, is to remove the tag with the following commands.

# First get the latest version 
git pull
# Locally delete the tag
git tag -d TAGNAME
# Delete tag remote
git push --delete origin TAGNAME

Bonus

Extend the deploy task with an on_failure* situtation. Remove the previous place tag.

Now it is time to run the software in the next exercise.