Hide Forgot
Description of problem: Did not remove message about jenkins autoprovision in samplepipeline.yaml template, Should remove it, because dropped jenkins autoprovision in 4.0 version Version-Release number of selected component (if applicable): openshift v4.0.0-0.49.0 How reproducible: always Steps to Reproduce: 1.Check the jenkins pipeline template, which include " A Jenkins server will be automatically instantiated in this project" 2.Create pipeline build, also include"A Jenkins server will be automatically instantiated in this project" $oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.yaml $ oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.yaml Pipeline Build Example --------- This example showcases the new Jenkins Pipeline integration in OpenShift, which performs continuous integration and deployment right on the platform. The template contains a Jenkinsfile - a definition of a multi-stage CI/CD process - that leverages the underlying OpenShift platform for dynamic and scalable builds. OpenShift integrates the status of your pipeline builds into the web console allowing you to see your entire application lifecycle in a single view. A Jenkins server will be automatically instantiated in this project to manage the Pipeline BuildConfig created by this template. You will be able to log in to it using your OpenShift user credentials. 3. Actual results: It has message about jenkins autoprovision info in jenkins pipeline template Expected results: Should remove jenkins autoprovision info in jenkins pipeline template Additional info: bluegreen-pipeline.yaml has the same issue
PR https://github.com/openshift/origin/pull/21451
OK PR https://github.com/openshift/origin/pull/21451 has merged moving onto QA
Yes, it's already fixed in ose,thanks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758