rpm-ostree

keremet/rpm-ostree

Fork 0

Commit Graph

Author	SHA1	Message	Date
Colin Walters	f81626d359	ci: Ensure fahc builds win over base Right now due to rdgo using `git describe` we have `v2017.4.65`, which is lower than `v2017.5`. Closes: #770 Approved by: jlebon	2017-05-09 13:32:25 +00:00
Colin Walters	a284b64479	ci: Use FAHC for build container Conceptually: we're going to move rpm-ostree and ostree at the same cadence most of the time; for both releases and for git master. The problem so far has been the latter part. Reusing FAHC for the build gets us half of the problem. The other trick I realized we can do - just pull ostree out from the build container. This avoids fetching it from the internet, and makes my workflow for hacking on both nicer - I just `sudo make install` in my build container for ostree. It's tempting to make the whole thing symmetric and require `sudo make install` for rpm-ostree and not do the insttree thing but...perhaps after. Closes: #758 Approved by: jlebon	2017-05-01 19:10:05 +00:00
Colin Walters	4bbea19a31	ci: Delete dockerfile, move to common scripts, consolidate gcc/clang The Dockerfile is problematic since we can't update it atomically. I also really dislike reliance on the Hub. Further, I think rather than caching our build deps as built containers, we should be caching RPMs in CI. And we should be using rpm-ostree at some point to assemble filesystem trees faster. Also, consolidate the clang to be serial with gcc, since while we lose a tiny bit of parallelism, it's not really worth its own context right now. Closes: #759 Approved by: jlebon	2017-04-28 21:17:18 +00:00

Author

SHA1

Message

Date

Colin Walters

f81626d359

ci: Ensure fahc builds win over base

Right now due to rdgo using `git describe` we have `v2017.4.65`, which
is lower than `v2017.5`.

Closes: #770
Approved by: jlebon

2017-05-09 13:32:25 +00:00

Colin Walters

a284b64479

ci: Use FAHC for build container

Conceptually: we're going to move rpm-ostree and ostree at the same
cadence most of the time; for both releases *and* for git master.
The problem so far has been the latter part.  Reusing FAHC
for the build gets us half of the problem.

The other trick I realized we can do - just pull ostree out from the build
container. This avoids fetching it from the internet, and makes my workflow for
hacking on both nicer - I just `sudo make install` in my build container for
ostree.

It's tempting to make the whole thing symmetric and require `sudo make install`
for rpm-ostree and not do the insttree thing but...perhaps after.

Closes: #758
Approved by: jlebon

2017-05-01 19:10:05 +00:00

Colin Walters

4bbea19a31

ci: Delete dockerfile, move to common scripts, consolidate gcc/clang

The Dockerfile is problematic since we can't update it atomically. I also really
dislike reliance on the Hub. Further, I think rather than caching our build deps
as built containers, we should be caching RPMs in CI. And we should be using
rpm-ostree at some point to assemble filesystem trees faster.

Also, consolidate the clang to be serial with gcc, since while we lose a tiny
bit of parallelism, it's not really worth its own context right now.

Closes: #759
Approved by: jlebon

2017-04-28 21:17:18 +00:00

3 Commits