# Setting up Atlassian Suite via Chef

**URL:** <https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458>\
**Category:** Chef Infra (archive)\
**Created:** [February 16, 2012, 10:01am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458 "2012-02-16T10:01:23Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Torben\_Knerr](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@Torben\_Knerr](https://discourse.chef.io/u/Torben_Knerr)\
**Post date:** [February 16, 2012, 10:01am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/1 "2012-02-16T10:01:23Z")

</div>

Ohai Chefs!

has anyone tried to set up the whole Atlassian Suite via Chef? I know there  
is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd, etc.  
as well. And git or SVN as well. And everything nicely configured. 🙂

I’m wondering whether this is possible at all, as far as I can remember the  
configuration of the Atlassian tools (and especially the linkage between  
them) is heavily web-based…

Cheers,  
Torben

---

<div class="post-metadata">

**Author:** ![Bryan\_Brandau](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_brandau/32/636_2.png) [@Bryan\_Brandau](https://discourse.chef.io/u/Bryan_Brandau)\
**Post date:** [February 16, 2012, 8:08pm UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/2 "2012-02-16T20:08:48Z")

</div>

It's possible to a certain degree. We have crowd, jira, bamboo, svn,  
artifactory, confluence and sonar all installed and configured with chef  
but there are many settings db bound. You can get the base install and some  
generic setup going.

Currently we don't have these cookbooks open sourced. They are on a list  
of many that we need to clean-up and then release.

-Bryan

On Thu, Feb 16, 2012 at 4:01 AM, Torben Knerr [ukio@gmx.de](mailto:ukio@gmx.de) wrote:

> Ohai Chefs!
> 
> has anyone tried to set up the whole Atlassian Suite via Chef? I know  
> there is a JIRA cookbook, but I would need to set up Bamboo, Fisheye,  
> Crowd, etc. as well. And git or SVN as well. And everything nicely  
> configured. 🙂
> 
> I'm wondering whether this is possible at all, as far as I can remember  
> the configuration of the Atlassian tools (and especially the linkage  
> between them) is heavily web-based...
> 
> Cheers,  
> Torben

---

<div class="post-metadata">

**Author:** ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)\
**Post date:** [February 16, 2012, 8:58pm UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/3 "2012-02-16T20:58:26Z")

</div>

On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr [ukio@gmx.de](mailto:ukio@gmx.de) wrote:

> has anyone tried to set up the whole Atlassian Suite via Chef? I know there  
> is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd, etc.  
> as well. And git or SVN as well. And everything nicely configured. 🙂

I wrote these internally at Opscode about a year ago, but they only go  
as far as you would expect. You've still got to load up a web browser  
for all the configuration. Going any further would be a feat of  
engineering and unfortunately probably not stable between upstream  
releases.

Bryan

---

<div class="post-metadata">

**Author:** ![Torben\_Knerr](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@Torben\_Knerr](https://discourse.chef.io/u/Torben_Knerr)\
**Post date:** [February 17, 2012, 8:59am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/4 "2012-02-17T08:59:03Z")

</div>

Hey Bryan,

that sounds good. Do you already know when they are going to be released?  
Or would you mind sharing a preliminary version of what you have?

Thanks a lot,  
Torben

On Thu, Feb 16, 2012 at 9:08 PM, Bryan Brandau [agent462@gmail.com](mailto:agent462@gmail.com) wrote:

> It's possible to a certain degree. We have crowd, jira, bamboo, svn,  
> artifactory, confluence and sonar all installed and configured with chef  
> but there are many settings db bound. You can get the base install and some  
> generic setup going.
> 
> Currently we don't have these cookbooks open sourced. They are on a list  
> of many that we need to clean-up and then release.
> 
> -Bryan
> 
> On Thu, Feb 16, 2012 at 4:01 AM, Torben Knerr [ukio@gmx.de](mailto:ukio@gmx.de) wrote:
> 
> > Ohai Chefs!
> > 
> > has anyone tried to set up the whole Atlassian Suite via Chef? I know  
> > there is a JIRA cookbook, but I would need to set up Bamboo, Fisheye,  
> > Crowd, etc. as well. And git or SVN as well. And everything nicely  
> > configured. 🙂
> > 
> > I'm wondering whether this is possible at all, as far as I can remember  
> > the configuration of the Atlassian tools (and especially the linkage  
> > between them) is heavily web-based...
> > 
> > Cheers,  
> > Torben

---

<div class="post-metadata">

**Author:** ![Torben\_Knerr](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@Torben\_Knerr](https://discourse.chef.io/u/Torben_Knerr)\
**Post date:** [February 17, 2012, 9:03am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/5 "2012-02-17T09:03:29Z")

</div>

On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan [btm@loftninjas.org](mailto:btm@loftninjas.org) wrote:

> On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr [ukio@gmx.de](mailto:ukio@gmx.de) wrote:
> 
> > has anyone tried to set up the whole Atlassian Suite via Chef? I know  
> > there  
> > is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd,  
> > etc.  
> > as well. And git or SVN as well. And everything nicely configured. 🙂
> 
> I wrote these internally at Opscode about a year ago, but they only go  
> as far as you would expect. You've still got to load up a web browser  
> for all the configuration. Going any further would be a feat of  
> engineering and unfortunately probably not stable between upstream  
> releases.
> 
> Bryan

Yeah, that's what I expected. I could imagine to mechanize these steps, but  
not sure if it would be worth the effort given that the webui changes quite  
often between atlassian versions...

Btw: so these are the same cookbooks that Bryan Brandau refers to?

Cheers,  
Torben

---

<div class="post-metadata">

**Author:** ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)\
**Post date:** [February 17, 2012, 2:26pm UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/6 "2012-02-17T14:26:09Z")

</div>

No, these were internal Opscode cookbooks. I doubt we would want to support  
them officially the way we do others, but I probably wrote them such that  
they're modular enough. I'll take a look at pulling them out and putting  
them on github somewhere if you're interested.  
On Feb 17, 2012 4:03 AM, "Torben Knerr" [ukio@gmx.de](mailto:ukio@gmx.de) wrote:

> On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan [btm@loftninjas.org](mailto:btm@loftninjas.org)wrote:
> 
> > On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr [ukio@gmx.de](mailto:ukio@gmx.de) wrote:
> > 
> > > has anyone tried to set up the whole Atlassian Suite via Chef? I know  
> > > there  
> > > is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd,  
> > > etc.  
> > > as well. And git or SVN as well. And everything nicely configured. 🙂
> > 
> > I wrote these internally at Opscode about a year ago, but they only go  
> > as far as you would expect. You've still got to load up a web browser  
> > for all the configuration. Going any further would be a feat of  
> > engineering and unfortunately probably not stable between upstream  
> > releases.
> > 
> > Bryan
> 
> Yeah, that's what I expected. I could imagine to mechanize these steps,  
> but not sure if it would be worth the effort given that the webui changes  
> quite often between atlassian versions...
> 
> Btw: so these are the same cookbooks that Bryan Brandau refers to?
> 
> Cheers,  
> Torben

---

<div class="post-metadata">

**Author:** ![kallistec](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/kallistec/32/23_2.png) [@kallistec](https://discourse.chef.io/u/kallistec)\
**Post date:** [February 17, 2012, 5:08pm UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/7 "2012-02-17T17:08:01Z")

</div>

On Friday, February 17, 2012 at 1:03 AM, Torben Knerr wrote:

> On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan \<[btm@loftninjas.org](mailto:btm@loftninjas.org) ([mailto:btm@loftninjas.org](mailto:btm@loftninjas.org))\> wrote:
> 
> > On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr \<[ukio@gmx.de](mailto:ukio@gmx.de) ([mailto:ukio@gmx.de](mailto:ukio@gmx.de))\> wrote:
> > 
> > > has anyone tried to set up the whole Atlassian Suite via Chef? I know there  
> > > is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd, etc.  
> > > as well. And git or SVN as well. And everything nicely configured. 🙂
> > 
> > I wrote these internally at Opscode about a year ago, but they only go  
> > as far as you would expect. You've still got to load up a web browser  
> > for all the configuration. Going any further would be a feat of  
> > engineering and unfortunately probably not stable between upstream  
> > releases.
> > 
> > Bryan
> 
> Yeah, that's what I expected. I could imagine to mechanize these steps, but not sure if it would be worth the effort given that the webui changes quite often between atlassian versions...  
> Btw: so these are the same cookbooks that Bryan Brandau refers to?
> 
> Cheers,  
> Torben

Having a mix of Chef and backups isn't necessarily a bad thing when you run into tricky applications like this. I recently set up Jenkins so that Chef would install the software and dependencies, install plugins, and install the libraries and such we needed to run the builds. For the actual Jenkins config, I didn't have the time to reverse engineer the job XML files and write an LWRP to generate them, so I decided to just back up the data to S3. It worked pretty well when I tested rebuild/restore. It does require one extra step beyond just running Chef, but I restore the build history when I do this, so I do get some value out of it.

I wouldn't be happy with this if this was for my revenue generating infrastructure, but for one-offs I'm primarily automating to make DR work smoothly so it's an acceptable trade off.

--  
Dan DeLeo

---

<div class="post-metadata">

**Author:** ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)\
**Post date:** [February 18, 2012, 1:09am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/8 "2012-02-18T01:09:35Z")

</div>

On Fri, Feb 17, 2012 at 9:26 AM, Bryan McLellan [btm@loftninjas.org](mailto:btm@loftninjas.org) wrote:

> No, these were internal Opscode cookbooks. I doubt we would want to support  
> them officially the way we do others, but I probably wrote them such that  
> they're modular enough. I'll take a look at pulling them out and putting  
> them on github somewhere if you're interested.

Someone asked for these so I stuck them up on github:

> **[GitHub - btm/btm-cookbooks: Random unsupported cookbooks for Opscode Chef](https://github.com/btm/btm-cookbooks)**
>
> Random unsupported cookbooks for Opscode Chef. Contribute to btm/btm-cookbooks development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![Torben\_Knerr](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@Torben\_Knerr](https://discourse.chef.io/u/Torben_Knerr)\
**Post date:** [February 22, 2012, 8:24am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/9 "2012-02-22T08:24:50Z")

</div>

Hey Bryan,

awesome, thanks! Will check them out as soon as I'm back on a git enabled  
device 🙂

Cheers,  
Torben  
Am 18.02.2012 02:10 schrieb "Bryan McLellan" [btm@loftninjas.org](mailto:btm@loftninjas.org):

> On Fri, Feb 17, 2012 at 9:26 AM, Bryan McLellan [btm@loftninjas.org](mailto:btm@loftninjas.org)  
> wrote:
> 
> > No, these were internal Opscode cookbooks. I doubt we would want to  
> > support  
> > them officially the way we do others, but I probably wrote them such that  
> > they're modular enough. I'll take a look at pulling them out and putting  
> > them on github somewhere if you're interested.
> 
> Someone asked for these so I stuck them up on github:  
> [GitHub - btm/btm-cookbooks: Random unsupported cookbooks for Opscode Chef](https://github.com/btm/btm-cookbooks)

---

<div class="post-metadata">

**Author:** ![Torben\_Knerr](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@Torben\_Knerr](https://discourse.chef.io/u/Torben_Knerr)\
**Post date:** [February 22, 2012, 8:27am UTC](https://discourse.chef.io/t/setting-up-atlassian-suite-via-chef/2458/10 "2012-02-22T08:27:03Z")

</div>

Hi Dan,

Didn't think of this so far, but it's definitely an option. Thanks for the  
hint!

Cheers,  
Torben  
Am 17.02.2012 18:09 schrieb "Daniel DeLeo" [dan@kallistec.com](mailto:dan@kallistec.com):

> On Friday, February 17, 2012 at 1:03 AM, Torben Knerr wrote:
> 
> > On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan \<[btm@loftninjas.org](mailto:btm@loftninjas.org)(mailto:  
> > [btm@loftninjas.org](mailto:btm@loftninjas.org))\> wrote:
> > 
> > > On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr \<[ukio@gmx.de](mailto:ukio@gmx.de) (mailto:  
> > > [ukio@gmx.de](mailto:ukio@gmx.de))\> wrote:
> > > 
> > > > has anyone tried to set up the whole Atlassian Suite via Chef? I  
> > > > know there  
> > > > is a JIRA cookbook, but I would need to set up Bamboo, Fisheye,  
> > > > Crowd, etc.  
> > > > as well. And git or SVN as well. And everything nicely configured.  
> > > > 🙂
> > > 
> > > I wrote these internally at Opscode about a year ago, but they only go  
> > > as far as you would expect. You've still got to load up a web browser  
> > > for all the configuration. Going any further would be a feat of  
> > > engineering and unfortunately probably not stable between upstream  
> > > releases.
> > > 
> > > Bryan
> > 
> > Yeah, that's what I expected. I could imagine to mechanize these steps,  
> > but not sure if it would be worth the effort given that the webui changes  
> > quite often between atlassian versions...  
> > Btw: so these are the same cookbooks that Bryan Brandau refers to?
> > 
> > Cheers,  
> > Torben
> 
> Having a mix of Chef and backups isn't necessarily a bad thing when you  
> run into tricky applications like this. I recently set up Jenkins so that  
> Chef would install the software and dependencies, install plugins, and  
> install the libraries and such we needed to run the builds. For the actual  
> Jenkins config, I didn't have the time to reverse engineer the job XML  
> files and write an LWRP to generate them, so I decided to just back up the  
> data to S3. It worked pretty well when I tested rebuild/restore. It does  
> require one extra step beyond just running Chef, but I restore the build  
> history when I do this, so I do get some value out of it.
> 
> I wouldn't be happy with this if this was for my revenue generating  
> infrastructure, but for one-offs I'm primarily automating to make DR work  
> smoothly so it's an acceptable trade off.
> 
> --  
> Dan DeLeo