Description of problem: visiting the link in deprecation note for pipeline build strategy gives 404 error Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-02-092336 How reproducible: Always Steps to Reproduce: 1. Create Jenkins server and Pipeline BC $ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/jenkins-ephemeral-template.json $ oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.yaml 2. Admin user login console and view Build Configs via Builds -> Build Configs -> sample-pipeline 3. Check message on BC details Actual results: 3. There is a deprecation note for Pipeline build strategy: Pipeline build strategy deprecation With the release of OpenShift Pipelines based on Tekton, the pipelines build strategy has been deprecated. Users should either use Jenkins files directly on Jenkins or use cloud-native CI/CD with Openshift Pipelines.Try the OpenShift Pipelines tutorial In the message, there are two external links, 'OpenShift Pipelines based on Tekton' and 'Try the OpenShift Pipelines tutorial', visiting the former link https://openshift.github.io/pipelines-docs/docs/docs/index.html gives 404 Page Not Found error. Expected results: 3. The link should be correct and existing Additional info:
PR fix https://github.com/openshift/console/pull/3218
Changes are not in 4.3.0-0.nightly-2019-11-05-164935, will check on newer builds
With the release of OpenShift Pipelines based on Tekton, the pipelines build strategy has been deprecated. Users should either use Jenkins files directly on Jenkins or use cloud-native CI/CD with Openshift Pipelines.Try the OpenShift Pipelines tutorial Now `OpenShift Pipelines based on Tekton` links to https://openshift.github.io/pipelines-docs/docs/docs/0.7/index.html Verified on 4.3.0-0.nightly-2019-11-06-215135
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-2020:0062