Skip to content
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.

Backend Hotfix Release Workflow

Gabriel Moraes edited this page Jan 8, 2021 · 1 revision

This workflow will be executed every time a push event occurs to a tag with the following name pattern: *.*.*-backend.

You can see it more detailed in the workflow file.

Overview

Step by step

A job called Generate release is defined witch contains the following steps:

1. Configure environment variables

Setup needed environment variables.

2. Execute fastlane deploy lane

fastlane steps are executed in a lane called deploy.

3. git fetch

Update repository references. This is needed because a new branch will be created from the hotfix tag.

4. Create branch

Creates a new branch from the hotfix tag. It's named newReleaseFromTag*.*.*-backend.

This branch is created only at the virtual machine executing the workflow. This is the branch that will be used to compile the project modules.

5. Create signature

Calls maven_signing.sh script to generate a signature.

6. Compile

Compiles all backend modules.

7. Upload

Uploads all modules that have maven publish gradle plugin to nexus.

8. Generate release notes

Executes release_notes fastlane lane.

This lane uses fastlane-plugin-semantic_release plugin to generate release notes.

9. Delete github release

This step is necessary because we don't have permission to edit a github release.

A first github release is manually created along with the hotfix tag (this is the start of a hotfix release process).

10. Create github release

Creates github release notes for generated version, from release notes generated in step 8.