We are moving heavily into automation and have literally hundreds of teams and 1000's of developers. We get many requests on a daily basis to change a variety of settings in BitBucket projects, Jira projects and Confluence Spaces. We have full time dedicated admins who handle all this work using tickets and manual work but this is obviously not an ideal situation
We would like to introduce "Configuration as Code" across all our tooling (not just Atlasian products) as well as for things like access management and networking (all again being done by hand today)
We are looking at using Jenkins pipelines to read yaml files that contain all our tooling configurations that can be updated wither through pull requests or self service portals
Has anybody had any experience of doing this? Are there any good patterns we should be following or pitfalls to be aware of?
Would hate to spend a lot of time perfecting something that has already been done or abandoned as being unfeasible.
Also does anybody know if the various REST API's Atlassian supply cover everything that we need to do to administer the teams. In particular CRUD for each of the following
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
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