Deploy to DEV pipeline's stage FAILS about openshift-jenkins-demo HOT 8 OPEN

@ssdowd for this problem, you can follow this step.

If pipeline execution fails with error: no match for "jboss-eap70-openshift", import the jboss imagestreams in OpenShift.

oc login -u system:admin
oc create -f https://raw.githubusercontent.com/jboss-openshift/application-templates/master/jboss-image-streams.json -n openshift

from openshift-jenkins-demo.

@Johnny2136 @tenderitaf
I used this one from troubleshooting section:

oc create -f https://raw.githubusercontent.com/jboss-openshift/application-templates/ose-v1.4.14/eap/eap70-image-stream.json -n openshift

See if this work for you guys.

from openshift-jenkins-demo.

This link is dead, could you please provide another one ?

from openshift-jenkins-demo.

I have the same issue.

from openshift-jenkins-demo.

Seeing error at same stage. Mine fails with this output:

[cicd-tasks-pipeline] Running shell script
+ oc new-build --name=tasks --image-stream=jboss-eap70-openshift:1.5 --binary=true --labels=app=tasks -n dev
error: no match for "jboss-eap70-openshift:1.5"

The 'oc new-build' command will match arguments to the following types:

  1. Images tagged into image streams in the current project or the 'openshift' project
     - if you don't specify a tag, we'll add ':latest'
  2. Images in the Docker Hub, on remote registries, or on the local Docker engine
  3. Git repository URLs or local paths that point to Git repositories

--allow-missing-images can be used to force the use of an image that was not matched

See 'oc new-build -h' for examples.
+ true

I've tried adding --allow-missing-images=true and --allow-missing-imagestream-tags=true, but get the same error.

from openshift-jenkins-demo.

@mrgleam Thanks! That fixed it.

from openshift-jenkins-demo.

Yes 404 error on the link

from openshift-jenkins-demo.

@ptrckq ecellent! your solution worked for me, Thanks so much!!! 😃

from openshift-jenkins-demo.