Bamboo - how much functionality to put in a task?

I'm creating a Bamboo server plugin to simplify integration with another product (Puppet Enterprise).  At a minimum, this just requires an API call to the other product which I figured could be a simple task.

I'd like to do some testing too, since that's kind of the point of a CI server ;-)

I had a few ideas how the plugin could do this:

  • Functionality on/off switches on the config screen for a single task (eg 'test', 'lint', 'syntax', etc)
  • Ship multiple tasks in the same plugin which perform discreet tasks, user responsible for selecting the appropriate steps
  • Ship muliple plugins each implementing discreet tasks

But I'm not sure what a typical Bamboo user would expect or prefer?  My goal here is make the end-to-end process as simple as possible.

Does anyone have a strong opinion on this or other ideas for how this should be done?

 

Thanks,

Geoff

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,080 views 0 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot