summaryrefslogtreecommitdiffstats
path: root/.papr.sh
Commit message (Collapse)AuthorAgeFilesLines
* papr: use new PAPR_PULL_TARGET_BRANCHJonathan Lebon2017-11-211-19/+1
| | | | | | 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.
* papr: auto-detect image tag to use and bump to f27Jonathan Lebon2017-11-171-9/+45
| | | | | | | | | | | | | 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.
* papr: use F26 container for extended testsJonathan Lebon2017-09-271-1/+2
| | | | | Now that we updated the test nodes to F26, let's also update the extended tests container to match.
* PAPR: define openshift_image_tag via command lineRodolfo Carvalho2017-06-161-1/+3
| | | | | | | 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.
* papr: add documentation to YAML and simplify contextJonathan Lebon2017-06-141-0/+2
| | | | | | 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.
* papr: rename redhat-ci related files to paprJonathan Lebon2017-06-131-0/+28
The project was renamed to PAPR, see: https://github.com/projectatomic/papr