To keep the jacuzzi allocations up to date, we need to run some tasks periodically. Currently on cruncher we run 'make' to update, generate and push the new allocations to github: https://github.com/bhearsum/static-jacuzzis/blob/master/Makefile And then on relengadm we periodically pull from github. In the short term, we should change this to run on relengadm directly, and push the results out to github. This means we're not reliant on github for normal operations.

Where does this occur on cruncher? I'll copy the auth key from there.

for my reference: 16:51 <catlee> the bit on cruncher right now just has this magic in .git/config: 16:51 <catlee> [remote "origin"] 16:51 <catlee> url = https://github.com/bhearsum/static-jacuzzis.git 16:51 <catlee> pushurl = https://catlee:SECRETTOKEN@github.com/bhearsum/static-jacuzzis.git

Catlee, can you take a look at relengwebadm:/data/releng/src/jacuzzi-allocator/crontask.sh and let me know if it includes everything required? I'll set this up to run a crontask with emails sent to you. And of course you can modify the crontask script as you see fit. If it looks good, I'll coordinate with you to kill the screen sessions and stop syncing from cruncher, then enable this crontask every 10m.

I updated the crontask to add --delete to the rsync call. Other than that, looks great, thanks!

crontask is enabled on relengwebadm, but not pushing to the area of the NFS share currently being shared. We'll wait to see some pushes to github.

Pushes look good. I'm just waiting for a thumbsup from catlee.

/(| ( : __\ \ _____ (____) `| (____)| | (____).__| (___)__.|_____

OK, we're live!