| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
PAPR now provides pull request tests with the branch that the test is
targeting. Let's use that instead of querying the GitHub API and
possibly running through the unauthenticated limit.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Current PAPR tests are failing because we're using an outdated image
tag. Switch to auto-magically determining which image tag to use based
on the branch the PR we're running in is targeting, which lets us not
have to worry about the tag version becoming stale again. This is
similar to what the containerized tests from `aos-cd-jobs` are doing
(i.e. use `git describe --abbrev=0` in the target branch to determine
the image tag to use).
Also bump to the brand new f27 release, which allows us to drop the
temporary workaround for the glibc/libsolv bug.
|
| |
|
|
|
| |
Now that we updated the test nodes to F26, let's also update the
extended tests container to match.
|
| |
|
|
|
|
|
| |
This is a temporary workaround to make sure the action plugin in the
openshift_health_checker role can read the correct value specified in
the OPENSHIFT_IMAGE_TAG environment variable, instead of a jinja2
template expression.
|
| |
|
|
|
|
| |
Don't duplicate the actual image tag used in the context. Just print it
in the logs instead. That way there's no risk of it being outdated when
we bump the tag in the YAML.
|
|
|
The project was renamed to PAPR, see:
https://github.com/projectatomic/papr
|
