Ulrich Wilkens <m...@uwilkens.de> writes: > The main effort is not the testing, it can run over night. Main effort > is holding the test systems up to date. > I'm doing it manually now and I'm searching for a better solution. Okay, what's the process here? Updating the system and repository (e.g. apt upgrade && git fetch) seems straightforward to script; is there more manual work required? Or are you referring to the fact that you need to manually check for new commits, then manually kick off the update process, instead of your machines initiating this process automatically (like CI would)?
Do you keep your VMs running (or at least some master control area which can start/stop VMs and run scripts)? If so, we might be able to leverage SourceForge's WebHooks to initiate the process. > > Well, that depends. You can never know how difficult it is to find a > fix and how many time you need. > Certainly true. Let me know if anything I've mentioned seems interesting, or if additional compute resources would be useful. Otherwise, I'll stay out of your way =). Thanks for your hard work! -- Matthew R. Trower ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
