On Sun, 12 Jul 2020 at 02:42, Sam Ruby <ru...@intertwingly.net> wrote: > > On Sat, Jul 11, 2020 at 8:26 PM sebb <seb...@gmail.com> wrote: > > > > However there is an issue in testing, in that SVN is only updated > > every 10 minutes, so the workspace won't show the updated files > > immediately. > > Almost, but not quite, a year ago, you asked this question: > > https://lists.apache.org/thread.html/64cfda89066f658480f0997517555609ca06649d6971808bfba01c61%40%3Cusers.infra.apache.org%3E > > A little over two months ago I mentioned that there was progress: > > "The infrastructure team has already enabled pubsub for LDAP data, and > is working on pubsub for private svn repositories. " > > https://lists.apache.org/thread.html/r5a9b6b61a9b4300d9e40003c58f9e87ac34cbe8dada7eaf2f3b02fbd%40%3Cdev.whimsical.apache.org%3E > > Search #whimsy in slack for "pubsub" in April of this year for more status. > > We have an existing cron job using pubsub to watch for changes in the > whimsy source code and, when a change occurs, initiates a puppet run. > These updates complement but don't replace the running of puppet by > the infrastructure team. > > In the (possibly near) future, we could have different cron job using > pubsub to watch for changes in svn repositories, match changes against > repository.yml, and if found do a full or partial "rake svn:update". > These updates could complement but not replace the running of svn > update every 10 minutes. If this were done, a number of mail > subscriptions could be retired. > > I suggest two separate cron jobs as these two tasks would need to run > under separate user ids.
Some possible alternatives: - Whimsy knows when it has updated SVN, so it could send a message to a server job asking for the relevant SVN workspace to be updated. This would not catch external changes, but most of the work is done by Whimsy now - emeritus listings could be cached by Whimsy internally, rather than as externally maintained listing files. Given that the changes are infrequent, and the numbers of files are likely to be small, it should not be too much of an overhead. Should not be a problem with karma, as only members get to see the links anyway. - add more commit email subscriptions to catch updates to more busy private repos
