OpenShift.io has a Build/Jenkins/Pipeline problem. What can be done?

Updated -

I add a new QuickStart project but the build doesn't start on the Pipelines page.

This happens because of a bug in the jenkins-sync plugin which restarts all old builds. Since, we have a restriction of only allowing 1 build at a time, the newly created project's build pipeline falls low into the build queue. To fix this, abort all the queued up builds except the one which was created 'just now'.

- On the Pipelines UI, click on the Jenkins URL ( this part needs better instructions )
- In the Jenkins UI, locate the queue visualisation on the left-hand side of the page.
- Click on the red abort button for each build.

Jenkins is not responding, says "Application is not available"

"When I goto https://jenkins-username-jenkins.8a09.starter-us-east-2.openshiftapps.com I just get Application Not Available"

This happens when your Jenkins service is struggling to load because of resource issues.

Workaround :

- Login to https://console.starter-us-east-2.openshift.com
- Navigate to https://console.starter-us-east-2.openshift.com/console/project/your-username-jenkins/overview by clicking on the *-jenkins project.
- Scale the "jenkins" service to 0 pods and then to 1. This might take upto 5 minutes to take effect.

My pipeline seems to have updated staging but my latest commit isn't there

It's likely that the staging server hasn't actually been updated. OpenShift.io (IO) updates the staging application version number when the new deployment configuration is sent to OpenShift Online (OSO). If your resource quota in OSO has been exceeded, you won't be able to update the existing staging pod. In this case click on the build number link in the Pipelines tab in IO to open in OSO. Once in the OSO console, look at the -stage project and watch for running staging servers from older spaces.

My Pipeline build fails with out-of-memory exceptions

[Pipeline] End of Pipeline
java.lang.OutOfMemoryError: Metaspace
Finished: FAILURE

Restart the Jenkins pod, either through the console or via CLI:

oc scale dc/jenkins --replicas=0 -n youruser-jenkins
oc scale dc/jenkins --replicas=1 -n youruser-jenkins

How do I enable or disable integration tests in my pipelines?

You can edit your Jenkinsfile to comment out the mavenIntegrationTest section on a per app basis.

If speed is essential (i.e. you are demonstrating OpenShift.io) you can make a faster demonstration by disabling integration tests. To do that you can globally configure pipelines (once the new Tenant is released) to disable integration tests via updating your fabric8-pipelines ConfigMap.

Type:

oc edit cm fabric8-pipelines

Then add the following to the data: section of the ConfigMap to disable the CD and/or CI integration tests

data:
disable-itests-cd: 'true'
disable-itests-ci: 'true'

My Pipelines are not being properly filtered by my Space?

When switching between spaces the Pipelines tab should filter by those apps created in the space.

To work around this from the openshift command line type:

oc edit bc foo

then ensure that the metadata.labels has a value of space: cheese like this:

metadata:
name: foo
labels:
space: cheese
...

that will then ensure that the foo pipeline is filtered to only show on the cheese space.

Which version should my Jenkins be at at ?

To find out the intended version, visit http://central.maven.org/maven2/io/fabric8/online/packages/fabric8-online-jenkins/1.0.167/fabric8-online-jenkins-1.0.167-openshift.yml and look for the section:

provider: fabric8
project: jenkins-openshift
version: 3.0.37

Re-construct the above URL by replacing 1.0.167 with the value in the file "TEAM_VERSION" in https://github.com/fabric8io/fabric8-init-tenant/commit/COMMIT_HASH where COMMIT_HASH is the hash in https://github.com/openshiftio/saas/blob/master/dsaas-services/f8-tenant.yaml#L2

Whenever my build completes it starts another one

This could have happened if lots of builds were triggered and never got provisioned due to quotas and there's lots of Build resources left over.

Delete all the build resources by doing a oc delete build --all

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.