openshiftio/saas-openshiftio

saas-openshiftio's Issues

ckout master

RHEL images are not starting

% docker run quay.io/openshiftio/rhel-fabric8-services-fabric8-build:latest                                                                                                                           master
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"${PROJECT_NAME}\": executable file not found in $PATH": unknown.
ERRO[0001] error waiting for container: context canceled

Need to add status of various periodic e2e tests to the README.md

Currently there are a few jobs which periodically run e2e tests against different clusters e.g.
https://ci.centos.org/job/devtools-test-e2e-prod-preview.openshift.io-smoketest-pr-us-east-2a-released/
Need to status for all existing periodic jobs to the repos README.md. One could use rh-che README.md [1] as an example:

Last build	Description
	periodic tests against production cluster us-east-2
	periodic tests against prod-preview cluster us-east-2a
	master build
	build compatibility with upstream
	integration tests against latest upstream SNAPSHOT

[1] https://github.com/redhat-developer/rh-che/blob/master/README.md

CI checks not running, preventing merge

I have a trivial PR open [1] for docs update, but I can't merge it because the required checks are not running. It's been sitting there for over a day. Could someone please check what the problem is?

[1] #925

Add @ibuziuk to collaborators

Requested by @aslakknutsen

add a simple / dummy CI pipeline

fabric8 pipelines will now only auto merge PRs providing CI tests have passed which is working great. The issue here is this repo has no CI on it so the commit status remains pending and so tenant + forge pipelines are blocked.

Are there any objections from anyone if I add a dummy Jenkinsfile to this repo so commits in PRs will get a success status? It's a quick win else we'll have to add logic to the pipeline library to work out if a repo has CI enabled on it. RIght now I don't know of a good way to do that so I'd rather not block the release pipelines for now.

@vpavlin @kbsingh any objections?