-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Nightlies #41
Comments
working on it, separate issues but related to the missing builds in index.json are missing SHASUM files, this must have been screwed up when I did the last round of work to make releases easier for people who are not @rvagg |
awesome :) |
fixed, but I'm going to leave this open because ... the dirty little secret here is that nightlies aren't triggered automatically yet, I've been doing them myself. It's not a big leap to make them automatic but it's not trivial either. I'm wondering if perhaps @Fishrock123 would like to join me in making sure we get at least one nightly out each day? At the moment I've been doing them towards the end of each day according to UTC time but that's not an absolute essential. We also are not restricted to exactly one per day if we need to throw more out there to test new commits. @Fishrock123 if you'd like to help, have a look at https://jenkins-iojs.nodesource.com/job/iojs+release+nightly/build to see how it's done, you just need to fill in the commit to fetch (it should be HEAD on the v1.x branch), there are instructions there for how to easily get that in 10-character format, as well as the day in UTC time, there's a command to run to get that listed on the page as well. I've done it for 20150207 already. |
Yeah, I had suspected that. XD
Sure. Sounds good. I could set a reminder for like 9pm UTC (4pm my time) and do one if there isn't already there. |
I have long suspected @rvagg is literally a machine. The fact these builds still happen further supports my theory. |
I noticed that the nightlies at https://iojs.org/download/nightly/ have stalled since March 13. Is there anything we can do to automate it? Going by @rvagg's description, it sounds like it could be a simple cron job that POSTs to the Jenkins form once a day. TBD how to handle authentication. I suppose that pasting my session cookies into the script is not the smartest move; for one, they'll probably expire after a while. |
Yeah, sometimes both me and @rvagg are not around on the weekend. Also missed monday tho. :s |
Most stuff is automated now - closing. |
Two issues, possibly connected:
The text was updated successfully, but these errors were encountered: