> On 24 Apr 2018, at 17:29, sebb <seb...@gmail.com> wrote: > > The buildbot job attic-site [1] is now working. > > It does the following: > - checkout attic/site (fresh) > - rm -rf docs/projects > - runs ./build.sh > - svn add docs -force > - svn commit (currently disabled) Is a svn commit really the only way to update the site ? Would be nicer if we could just copy the files somewhere.
As I wrote elsewhere I have a talk pending with infra, how the trigger (our “real” attic site) will work if we move attic to git (Something that again would help edit from anywhere). > > Note that it is necessary to remove the generated files to ensure any > deletions are noticed > Probably should not happen in the case of Attic, but it would pick up > any files that have not got generated for any reason. > > The builds are listed at: > > https://ci.apache.org/builders/attic-site > > The job does not currently seem to send any mails to the attic general > list though it is configured do so on changes of status > (success/failure). > Not sure why; I would have expected some. > > Let me know when the site is in a fit state to try enabling checkin. If you by checkin means overwriting the production site, then as pr my review I am -1 on it. If you by checking means having the existing production site untouched (very important), and site-jekyll, site-lua and site-json somehow below the production site, then I do not see the reason why not to commit. DO NOT touch the production site, before we have a clear decision on which of the 3 sites shall replace production. My opinion. rgds Jan I. > > [1] > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/attic-site.conf > (requires committer karma)
