On 05/26/18 05:55, Matthew R. Trower wrote:
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?
apt upgrade would only do it for Debian based systems. But there are a
lot more.
I suppose I've to care about a dozen different port and package systems.
Git commands are not a problem, they are automated.
What I'd like to have is a solution that can setup a new system from an
ISO image
with all my custom configuration and scripts. And it must work for all
the different
flavors of Linux, BSD, ...
I'm afraid such thing doesn't exit and it would be a huge project by its
own.
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)?
I've indeed to kick off all my tasks manually, even if the sub-tasks are
running
automatically. And I don't want to change it because I don't do them on
a regular basis
and the order of the tasks and their parameter are often changing.
But anyway, it has never been my intention to write a test environment
for everyone.
Its mainly for testing my own changes.
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.
I would like to keep my VMs running all the time. But it doesn't work
anymore because my main server has "only" 64 gig of ram. That's not enough
for all VMs. An update would be too expensive (just for a hobby project).
So I normally start a group of VMS (all Linux or all BSDs) and test this
group.
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!
Well, to be honest, I don't want to invest more time in this testing suite.
Its only a spin off. I prefer coding much more than testing.
-- Matthew R. Trower
Best regards, Ulrich
--
Ulrich Wilkens
Email: m...@uwilkens.de
------------------------------------------------------------------------------
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
