On Sat, Feb 06, 2016 at 11:30:52PM -0800, Krzysztof Kosiński wrote:
One thing that wasn't mentioned so far is the broader hosted tools ecosystem. GitHub works with Travis CI - this means we wouldn't need to maintain our Jenkins installation, which suffers from space constraints. (It stopped working again a couple of weeks ago.)
Running out of space is not the issue, it's just a symptom.
The real problem is more that we don't have anyone looking after it. (The person that set it up left the project, and the task sort of devolved to me but I've had zero time for it since, and evidently it's bitrotting quickly.) I'm also not sure if anyone's actually acting on the issues it's flagging, which makes running it a bit pointless I suppose.
Note that it's probably possible to set up a bzr->git import on our current tree without having to wait on transitioning, and then set up travis or jenkins or whatever on top of that.
Anyway, if someone(s) is willing to adopt this task, and someone can follow up on fixing the issues, I'd love to hand over the responsibility, and let you implement and drive it however you want.
Another very useful thing is that Github can be used to easily publish HTML Doxygen documentation with the gh-pages feature. It can even be done from Travis CI. Maybe we can use our website and a Launchpad commit hook to do that, though.
Right, there are many ways to skin that particular cat. I seem to recall we were thinking of doing this with Jenkins, too.
Bryce