Release a hotfix

In this tutorial we will describe how to release a hotfix.

• We need clone of git repository with checkout actual branch with hotfix, during the process, we will need the right to write to this repository, example:

 # clone respository
 $ git clone git@github.com:bcvsolutions/CzechIdMng.git
 # change folder
 $ cd CzechIdMng
 # checkouthotfix
 $ git checkout hotfix/<HOTFIX_VERSION>

• install maven to your computer (maven install steps),

If branch with hotfix doesn't exists, you can easily create this branch with this command (you must be on branch master and locally or remote must not exist branch with name hotfix…):

 $ cd Realization/backend/aggregator/
 $ mvn clean -Prelease jgitflow:hotfix-start
 $ git push -u origin hotfix/<HOTFIX_VERSION>:hotfix/<HOTFIX_VERSION>
 

This commands creates new hotfix started from master branch. Sometimes is needed to fix previously released version. For this case, we can find last commit id (= last commit in tag) and start hotfix with command:

 $ mvn clean -Prelease jgitflow:hotfix-start -DstartCommit=<CHANGE_WITH_COMMIT_ID> -DreleaseVersion=<CHANGE_WITH_CURRENT_HOTFIX_VERSION_WITHOUT_SNAPSHOT_SUFFIX>

Execute this three commands in CzechIdm folder.

 $ git fetch -p
 $ git branch -vv
 $ git fetch -p && for branch in `git branch -vv | grep ': gone]' | awk '{print $1}'`; do git branch -D $branch; done

This command create new branch and set up new version in BE poms. FE package.json you must update by self.

After install maven is necessary setup maven via settings.xml, this file you can found in ~/.m2./. If this file don't exists create it. Into file you must put this settings (change username and password yours!):

<settings>
  <servers>
    <!-- Nexus server login information -->
    <server>
      <id>nexus</id>
      <username><USERNAME></username>
      <password><PASSWORD></password>
    </server>
  </servers>
 
  <pluginGroups>
 	 <pluginGroup>external.atlassian.jgitflow</pluginGroup> 
  </pluginGroups>
 
  <mirrors>
    <mirror>
      <id>nexus</id>
      <mirrorOf>*</mirrorOf>
      <url>https://nexus.bcvsolutions.eu/repository/maven-public/</url>
    </mirror>
  </mirrors>
 
  <profiles>
    <profile>
      <id>nexus-repo</id>
      <repositories>
        <repository>
          <id>maven-snapshots</id>
          <url>https://nexus.bcvsolutions.eu/repository/maven-snapshots/</url>
          <releases><enabled>false</enabled></releases>
          <snapshots><enabled>true</enabled></snapshots>
        </repository>
        <repository>
          <id>maven-release</id>
          <url>https://nexus.bcvsolutions.eu/repository/maven-releases/</url>
          <releases><enabled>true</enabled></releases>
          <snapshots><enabled>false</enabled></snapshots>
        </repository>
      </repositories>
    </profile>
</profiles>
  <activeProfiles>
    <activeProfile>nexus-repo</activeProfile>
  </activeProfiles>
</settings>

• Update version in FE package.json is not automatically. You must update this information by self example. This changes you must commit and push before start with release.

Follow the following commands:

 # in your local clone of repository go to 
 $ cd CzechIdMng/Realization/backend/aggregator
 # start with release hotfix
 $ mvn clean -Prelease jgitflow:hotfix-finish -DupdateDependencies=false -DdocumentationOnly=true -DallowUntracked=true -DdevelopmentVersion=<CHANGE_WITH_CURRENT_DEVELOPMENT_BRANCH>

If you get during process this error: The authenticity of host 'git.bcvsolutions.eu' can't be established. add into parameters this:

 $ mvn ... -DenableSshAgent=true
 

If you have untracked files which will definitely not cause GIT conflicts, add the following parameter:

 $ mvn ... -DallowUntracked=true

• After mvn finish with build, test and update just enter this on hotfix branch:

 $ git push
 $ git push --tags