On 16 February 2015 at 05:54, Alex Harui <[email protected]> wrote: > I’m a big believer in the scalability of decentralized infrastructure. > That’s easy for me to say because I don’t have to maintain a server for each > project. But as Tony mentions, the ASF is placing restrictions on what > plugins you can use in JIRA, re-indexing is a huge pain, performance is > becoming an issue, etc. I wish Infra could find a way to give each project > its own Azure server and host builds and JIRA and a few other things on > that VM. Centralized JIRA was a reason I couldn’t just use the JIRA web > services to do the import. I had to get my own JIRA instance up and running > and play there because if I messed up, I would mess up JIRA for all of the > ASF, and ruin performance for the other projects while pounding on the web > services. That said, some projects may want to share a JIRA in order to > transfer bugs between projects if users file them against the wrong project.
Alex, This is something I have been thinking about for a while now, about how to best scale out JIRA et al. I came to the, albeit early, conclusion, that an instance per project was likely to be the best way. But, I need to look at how we manage that in the sense of single shared codebase, shared config where possible, etc So in principle I agree, but there are whole host of practicalities we need to work out first. Also, as you may not be aware the Infra team is currently massively busy. We are working extremely hard to eradicate all of our technical debt - this in most practical terms means that many of us are working on several significant projects already, plus the daily churn of issues. In other words, it's not likely to be 'fixed' in the next few weeks. -- Cheers, Tony ---------------------------------- Tony Stevenson [email protected] [email protected] http://www.pc-tony.com GPG - 1024D/51047D66 ----------------------------------
