Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,382
Community Members
 
Community Events
176
Community Groups

jgitflow release-start non interactive

Hi,

I would like your input on how to best release pom, parent module and a group of submodules using Bamboo and jgitflow release.

I have completed setting up the maven build deploy in the Build stage, and the outputs are the pom, parent module and submodules artifacts with version-SNAPSHOT.

Next plan is to look at the jgitflow to release the individual projects pom, and parent + subprojects.

 

1. I have done the SSh setup and now I'm stuck here on how to handle the version release of the project pom.

When I ran "mvn jgitflow:release-start", it prompt user for the release version and development version. Can I skip the interactive and accept the default versions ?

2) If the above is not possible, another approach is to use <releaseVersion> and <developmentVersion>.but how do I get the two versions?

 

Any other suggestion is appreciated.

 

Thanks,

andrew

 

 

 

 

 

1 answer

Hello,

 

Alternatively, I'd like to add three optional arguments for this non-interactive goal:

 

* incrementMajor : if set, will not ask for a version number, increment the major number and set to 0 the minor and patch numbers

* incrementMinor : if set, will not ask for a version number, increment the minor number and set to 0 the patch number

* incrementPatch : if set, will not ask for a version number, increment the patch number

 

Based on https://semver.org/ semantic versioning.

 

Why?

 

* With the SSH problem on Windows, all developers can't execute the release-start goal => we need to automate it on GitLab

* On GitLab, there is no parameter to be passed to pipelines we run manually, so I'd create 3 pipelines:

 

** "Start a major release"

** "Start a minor release"

** "Start a patch release"

 

All setting the correct parameters for the release start to be done without any prompt.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events