rpm-ostree

Author SHA1 Message Date

Author	SHA1	Message	Date
Jonathan Lebon	289af613a9	ci/jenkins: don't pass `GIT_COMMIT` to ci-commitmessage-submodules.sh Jenkins is tricky: it does an initial checkout, merges the PR head into the target branch, then creates the pod. Once in the pod, we do a `checkout scm` which also merges the PR head into the target branch. However, the `change.GIT_COMMIT` variable we get from that is set to the SHA of the first merge, not the second one. Which... yeah is super confusing since we explicitly assign `change` from that `checkout scm` operation. So that's probably a valid bug. This was then throwing off `ci-commitmessage-submodules.sh` since it didn't find the merge commit in the graph. Anyway, not going to spend more time on this. Let's just not pass any commit at all. The git range `origin/master..HEAD` already does what we want (go through all the commits in HEAD not in master).	2019-10-03 13:39:11 -07:00
Jonathan Lebon	677c3c8b29	ci: Also bump MSRV to 1.37.0 for CCI Jenkins Just split it out into a separate script for easier sharing.	2019-10-01 11:26:29 -04:00
Jonathan Lebon	46ab7d1ae8	ci: Add Jenkins pipeline This is an experiment in using Jenkins pipelines for our CI. See similar initiatives in coreos-assembler[1] and fedora-coreos-config[2]. For now, this only does the following testing: - checks commit for unintended submodule bumps - checks the minimum Rust version - builds RPMs - builds FCOS (with the new RPMs both for executing the build itself, as well as included in the built OS) There are dummy placeholders for where we'd actually run the vmcheck and the compose testsuites. Let's address those trickier parts as follow-ups. [1] https://github.com/coreos/coreos-assembler/pull/667 [2] https://github.com/coreos/fedora-coreos-config/pull/131 Closes: #1899 Approved by: cgwalters	2019-09-18 15:15:28 +00:00

Jonathan Lebon

289af613a9

ci/jenkins: don't pass GIT_COMMIT to ci-commitmessage-submodules.sh

Jenkins is tricky: it does an initial checkout, merges the PR head into
the target branch, then creates the pod. Once in the pod, we do a
`checkout scm` which *also* merges the PR head into the target branch.
However, the `change.GIT_COMMIT` variable we get from that is set to the
SHA of the first merge, not the second one. Which... yeah is super
confusing since we explicitly assign `change` from that `checkout scm`
operation. So that's probably a valid bug.

This was then throwing off `ci-commitmessage-submodules.sh` since it
didn't find the merge commit in the graph.

Anyway, not going to spend more time on this. Let's just not pass any
commit at all. The git range `origin/master..HEAD` already does what we
want (go through all the commits in HEAD *not* in master).

2019-10-03 13:39:11 -07:00

Jonathan Lebon

677c3c8b29

ci: Also bump MSRV to 1.37.0 for CCI Jenkins

Just split it out into a separate script for easier sharing.

2019-10-01 11:26:29 -04:00

Jonathan Lebon

46ab7d1ae8

ci: Add Jenkins pipeline

This is an experiment in using Jenkins pipelines for our CI. See similar
initiatives in coreos-assembler[1] and fedora-coreos-config[2].

For now, this only does the following testing:
- checks commit for unintended submodule bumps
- checks the minimum Rust version
- builds RPMs
- builds FCOS (with the new RPMs both for executing the build
  itself, as well as included in the built OS)

There are dummy placeholders for where we'd actually run the vmcheck
and the compose testsuites. Let's address those trickier parts as
follow-ups.

[1] https://github.com/coreos/coreos-assembler/pull/667
[2] https://github.com/coreos/fedora-coreos-config/pull/131

Closes: #1899
Approved by: cgwalters

2019-09-18 15:15:28 +00:00

3 Commits