nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

YUM repositories for Atlassian products

Matt Moldvan

Hello,

I'd like to automate receiving updates for the Atlassian products we are currently using (JIRA, Crowd, etc) and was wondering if there is an official YUM repository we could mirror, or perhaps an "newest version" RPM I could wget from a script. Is any such sort of automation possible or am I stuck with downloading a tar file that may change location?

Thanks,
Matt Moldvan.
Linux Network Engineer
Security Inspection, Inc.

Accepted answers

All comments

Jason Jason16

No there is no offical YUM repo, or even RPM's of Atlassian products.

But there is nothing stopping you from creating RPM's for installing atlassian products and setting up a local yum repo and host it internaly with a webserver.

Though upgrading atlassian tools is kind of complex, not many people would want to leave it to the chance of a "yum update"

Matt Moldvan

Yeah. In the absence of that I'm wondering if there is a stable link that I could wget and rebuild on a regular basis. What got me on this train of thought was I installed 2.2.4 last week and checking this week I found a 2.2.7 ... would like to automate my RPM builds for our upcoming YUM repo automagically.

May take some babysitting on the script side but it's worth the time saved when we have to create multiple new VMs with the Atlassian products.

Thanks for the reply.

Jason Jason16

Well it seems the download links change with each version, now unless atlassian provides a latest.tgz for each product you may want to look into something like the perl module WWW::Mechanize and just pull the links out of the download pages.

Joe Clark

Pinging our maven repository (https://maven.atlassian.com/content/repositories/atlassian-public/) might be easier than trying to scrape the download page.

Gary Weaver

Excellent point. Atlassian suggests looking through release notes of every version between the original and the one you are upgrading to and making manual changes as needed. Despite this, they are still some of the easiest upgrades for a complex Java-based web applications I've seen. If you choose to package it, PLEASE do not rip out Tomcat and depend on the RPM version of Tomcat. IMO, RPM version of Tomcat has historically been a mess, as has been the jar hell that you find on RHEL installs: http://weblogs.java.net/blog/garysweaver/archive/2009/05/peering_into_th.html

Matt Moldvan

Thanks, I'll check out Maven, though I haven't worked with it before.

Matt Moldvan

Good point, Gary. I always worry about having software dependent on system RPMs; I prefer to have apps in a separate self-contained partition with all requirements residing in that area.

rrudnicki

Another way to automate the process could be using Puppet (www.puppetlabs.com). Puppet is very useful to automate tasks and create a standard for your network. You could create a script to download the .tar files and create the .rpm files by rpmbuild. After this, you could create your own repository for the Atlassian products. The advantage using puppet, is that you could manager many other things about your network, not just scripts. Also, you can use Maven as quoted before.

Graham Leggett

To add an answer for the record, I have contributed a number of nosrc SRPMs:

https://jira.atlassian.com/browse/JRASERVER-68379

https://jira.atlassian.com/browse/CWD-4976

https://jira.atlassian.com/browse/BAM-18598

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

crowd

script

automation

repository

rpm

yum