Hi all,
Hoping someone can help me out here... I'd like to add a job to jenkins that runs the depictor command (`python write_website.py`) whenever a commit is made to the dev repo master branch[0] OR stem's master branch. (If I could only have one I'd pick stem's.)
Historically, one of the reasons consensus-health has lagged a little bit has been because in the past there was some tiny change in Stem that wound up breaking it. I don't think that's happened lately, but it's caused me to be conservative about upgrading stem, and usually the changes I need are the latest one added to master. A jenkins job would give me a bit more confidence and enable a bit more proactivity on fixing it for breaking changes.
Who runs jenkins? What would I need to do to set this up? The good news is there's only three commands needed to go from zero to index.html:
git clone https://git.torproject.org/user/tom/depictor.git cd depictor git clone https://git.torproject.org/stem.git ./write_website.py
-tom
Hi Tom, just food for thought but another option would be a cron task that pulls the repos and runs that if there's a change. That's what I do for stem's website so it reflects the changes I push.
Cheers! -Damian
On Tue, Jul 5, 2016 at 5:31 AM, Tom Ritter tom@ritter.vg wrote:
Hi all,
Hoping someone can help me out here... I'd like to add a job to jenkins that runs the depictor command (`python write_website.py`) whenever a commit is made to the dev repo master branch[0] OR stem's master branch. (If I could only have one I'd pick stem's.)
Historically, one of the reasons consensus-health has lagged a little bit has been because in the past there was some tiny change in Stem that wound up breaking it. I don't think that's happened lately, but it's caused me to be conservative about upgrading stem, and usually the changes I need are the latest one added to master. A jenkins job would give me a bit more confidence and enable a bit more proactivity on fixing it for breaking changes.
Who runs jenkins? What would I need to do to set this up? The good news is there's only three commands needed to go from zero to index.html:
git clone https://git.torproject.org/user/tom/depictor.git cd depictor git clone https://git.torproject.org/stem.git ./write_website.py
-tom
[0] https://gitweb.torproject.org/user/tom/depictor.git/ _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On 5 July 2016 at 14:34, Damian Johnson atagar@torproject.org wrote:
Hi Tom, just food for thought but another option would be a cron task that pulls the repos and runs that if there's a change. That's what I do for stem's website so it reflects the changes I push.
I think that's a good model for webpages-backed-by-git, but less so for integration/software testing.
I could probably rig something up like that locally, but I'd have to make it detect a crash and email me. The advantage of jenkins is it will do that automatically, on infrastructure I don't have to worry about maintaining[0], as well as making the crash details public. There's a chance it might even detect a break in stem.
-tom
[0] A problem I've had a lot is that my 'email me stuff' scripts will stop emailing... and I never find out they're failing!