on master help sign in
CURATORS: Update timing section with how the build script builds even if there's already a nightly
commit1901c31a11de095caa7574954d432752e550f9c5 authorAdam Bergmark <adam@bergmark.nl> dateTue 3 May 2016, 09:51 (10 years ago) parent2be94a6
1 file changed+4−4
CURATORS.md+4−4
CURATORS.md+4−4
@@ -123,11 +123,11 @@ develop this advice over time. For now: if you're not sure, ask Michael for
123123guidance.
124124
125125### Timing
126−A cronjob on the build server keeps trying to build nightly unless it has already succeeded.
127126
128−(Nightly builds should be run once a day. A common technique I use is, after a
129−build succeeds, write something like `sleep 20h;
130−/opt/stackage-build/stackage/automated/build.sh nightly-2015-01-02`.)
127+A looping script on the build server keeps trying to build nightly
128+with `sleep 30m` interleaved. It only publishes the nightly once per
129+day. This way new package versions or build failures can be caught
130+early and hopefully the nightlies will be timely.
131131
132132LTS minor bumps typically are run on Sundays.
133133