initialization script for creating temporary branch

No parameter of more than 1 triggers the usage display

Automatic mode (1 parameter provided)

Value of the parameter will be AUTO.

This script will detect:

1. the current integration-scripts-priv checked out branch (BRANCH)
2. the latest HF available on connect for this branch (HF) (see NXBT-1660)
3. the revision of the HF found (REV)

Then it will checkout the same branch in nuxeo-dm-hotfixes repository and create and checkout a temporary branch based on the following labelling:

tmp-<BRANCH>-<HF+1>-1.0.0

For example, if the latest 8.10 HF published on connect is HF04, the branch name will be:

tmp-8.10-HF05-1.0.0

If a branch with an identical name already exists the script must fail saying so, returning a code greater than 0.

Manual mode (1 parameter provided)

Value of the parameter will be a revision (x.y.z).

This will handle the use case of publishing a later revision of an already pusblished HF. The script will behave identically to the automatic scenario except it will not detect the HF version and HF revision but will take them as parameters.
Only the revision is needed and the HF version will be the one of the latest HF published. It does not make sense to publish a revision of an older HF.

If a branch with an identical name already exists the script must fail saying so.

If a tag matching the current version and revision exists then the script must fail saying so.

Generating release notes

1. create folder misc if does not exists mkdir -p misc
2. add the folder to git tracking with git add misc
3. generate into the misc/releaseNotes.md file (Markdown format, see NXBT-1618) using a command like:

   <integration-scripts-priv>/hfBuilder/releaseNotes.sh md <BRANCH>-HF<HF> > misc/releaseNotes.md
   

4. add misc/releaseNotes.md to git tracking git add misc/releaseNotes.md

Generating package.xml file

package.xml will be generated using the releaseNotes.sh script (see NXBT-1619) using a command like:

<integration-scripts-priv>/hfBuilder/releaseNotes.sh xml <BRANCH>-HF<HF> > > src/main/resources/package.xml

Generating pom.xml file

Pom.xml will be generated using the genPom.sh script (see NXBT-1584) using a command like:

<integration-scripts-priv>/hfBuilder/genPom.sh > ./pom.xml