rpm-ostree

Author SHA1 Message Date

Author	SHA1	Message	Date
Jonathan Lebon	c5fa202378	sync.sh: tweak for container workflow In the container build + vagrant test workflow, we have to run `make vmsync` from the env in which autoconf was run, which is the container. However, when using git worktrees (which is useful in this scenario to avoid having to overwrite your local builds) and a CentOS build container, the git inside is too old to understand worktrees, so let's avoid invoking git in any of the test harness scripts. Also make sure to restorecon after installing the new rpm-ostreed. Closes: #555 Approved by: cgwalters	2016-12-21 20:00:43 +00:00
Jonathan Lebon	12c4b5b16f	vmcheck: adapt for non-vagrant hosts This is just the final bit required to make sure the vagrant and non-vagrant paths can work happily together. It's mostly minor fixes, though the most major change which also affects vagrant is that we now sync to the root home dir, rather than ~vagrant. Closes: #524 Approved by: cgwalters	2016-11-22 17:15:20 +00:00
Colin Walters	2f9d586bdc	Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon	2016-11-16 18:14:23 +00:00

Jonathan Lebon

c5fa202378

sync.sh: tweak for container workflow

In the container build + vagrant test workflow, we have to run `make
vmsync` from the env in which autoconf was run, which is the container.

However, when using git worktrees (which is useful in this scenario to
avoid having to overwrite your local builds) and a CentOS build
container, the git inside is too old to understand worktrees, so let's
avoid invoking git in any of the test harness scripts.

Also make sure to restorecon after installing the new rpm-ostreed.

Closes: #555
Approved by: cgwalters

2016-12-21 20:00:43 +00:00

Jonathan Lebon

12c4b5b16f

vmcheck: adapt for non-vagrant hosts

This is just the final bit required to make sure the vagrant and
non-vagrant paths can work happily together. It's mostly minor fixes,
though the most major change which also affects vagrant is that we now
sync to the root home dir, rather than ~vagrant.

Closes: #524
Approved by: cgwalters

2016-11-22 17:15:20 +00:00

Colin Walters

2f9d586bdc

Redo vmcheck to abstract over ssh-config, drop all building

My development environment is now using "pet" docker containers.
I use VMs for testing things that require that (like rpm-ostree).

This patch builds on work from @jlebon in
https://github.com/projectatomic/rpm-ostree/pull/509
to rework `vmcheck` such that it can work on any `ssh-config`.  By
default we expect this to be Vagrant.

However, I go a lot farther and delete the `vmbuild` code that was
trying to do builds in a container on the target VM.  I think this is
still worth pursuing at some point, but for now I think it's
reasonable to assume that the rpm-ostree developer audience uses Linux
as their host workstation and hence has containers.

(There's another important point here in that for developing lower
 level things like rpm-ostree, there's a strong push to make the VM
 disposable and not a pet)

Closes: #516
Approved by: jlebon

2016-11-16 18:14:23 +00:00

3 Commits