Continuous Deployment for Atlassian Plugins - AtlasCamp 2011
Download as PPTX, PDF0 likes1,018 views
This document discusses continuous deployment for plugins, including what it is, why it's important, and how to get started. It recommends using tools like Bamboo for automation and deploying plugins regularly to speed up development and reduce costs. Getting feedback from users is also advised to further improve plugins. The document provides examples of plugins that use continuous deployment and automation with Bamboo. It concludes by emphasizing making plugins great by deploying often and soliciting feedback.
Continuous Deployment for Atlassian Plugins - AtlasCamp 2011
- 2. Continuous Deployment for Plugins Joseph Clark Plugin Developer, Atlassian 2
- 5. What is it? • Tooling • “Continuous”... or not. 5
- 6. Why should you care? • Speed • Cost • A natural progression from Continuous Integration • User Confidence 6
- 7. 7
- 8. 8
- 9. Getting started… • Plugins 2 • Target System • Some kind of automation • How often? 9
- 10. A simple example curl https://confluence/admin/uploadplugin.action -u admin:admin --location-trusted -k -–header "Content-Type: multipart/mixed“ -–header "X-Atlassian-Token: no-check“ -–form "file_0=@$jar 10
- 11. Getting fancy with Bamboo Compile Deploy Task Task 11
- 13. 13
- 14. Getting feedback… • It takes a certain kind of person • Golden rule: make it simple 14
- 15. Use a plugin, stupid! 15
- 16. 16
- 17. 17
- 19. 19
- 20. Contacting me... @jaysee00 • jclark@atlassian.com • answers.atlassian.com/users/123/joseph-clark-atlassian/ 20
- 21. TAKE-AWAYS “ Make your plugin the best it can be – deploy regularly and encourage user feedback. ” Bamboo & JIRA ftw! ” #atlascamp 21
- 22. Thank you!