Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

jgitflow release-start non interactive


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.









1 answer



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 semantic versioning.




* 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
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

179 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you