On 04.01.2017 16:45, Martin Pitt wrote: > Hello all, > > first, a quick intro of myself: I'm Martin Pitt (nicknamed "pitti" on IRC and > IRL) and joined Red Hat's Cockpit team yesterday. Until then I've been a > Debian > developer for about 14 years and an Ubuntu developer for about 12½. I've > touched a lot of things over the years, but most recently I've mostly been > involved in plumbing (systemd, networking, udisks and the like) and Ubuntu's > CI.
Awesome. Welcome :) Cockpit has had to be involved in so many of the same things... > While learning about cockpit and how to test it I put together a small script > [1] > that creates a Fedora 25 based Cockpit development VM out of thin air (using > mkosi). This contains a running cockpit (as it comes with F25) as well as all > build and test dependencies. This helped me personally to figure out some > issues with setting up the tests (like [2]), gives me a tool to get a > reproducible dev environment without cluttering my host system with lots of > build/test depends, and I can use QEMU's snapshots to reset to a clean state. > Stef > mentioned that this might also be useful for improving our isolation in > GitHub's integration tests. > > How does it look like? You call it with the output VM path and cockpit's git > checkout directory as arguments, it will do some grinding and eventually give > you some info how to use it: This is pretty cool. And the experience has gotten you familiar with all sorts of details already. My question is whether you've tried 'vagrant up' in a cockpit git checkout ... and whether that solves the same issue ... or is hopelessly broken :D Stef
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cockpit-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
