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 Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

179 views 1 3
Join discussion

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