Red Hat Bugzilla – Bug 1459219
Broken link to help information about post hooks in edit BuildConfig
Last modified: 2017-08-16 15:51 EDT
Description of problem:
When using the web interface to edit a BuildConfig, and choosing "Show advanced options", there is a "Learn more" link next to "Post Commit Hooks". This link is broken.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In the web interface, edit a BuildConfig
2. Choose "Show advanced options"
3. Click the "Learn more" link next to "Post Commit Hooks"
A broken link to https://docs.openshift.com/container-platform/3.5/dev_guide/builds.html#build-hooks
A working link to https://docs.openshift.com/container-platform/3.5/dev_guide/builds/build_hooks.html
I have not sourced this bug upstream, as it seems to be OCP related.
Correction: I've found the same issue upstream, and submitted a patch
We will get a redirect in place to fix 3.5, thanks for the patch for upstream.
adding alex to CC to let us know when the redirect is ready
There is a partial redirect in place for 3.5 so the link will not 404 but it will not go to the hooks sub-page for builds.
For 3.6 it is fixed in https://github.com/openshift/origin-web-console/pull/1694
Link is correct now in OCP 3.6:
OpenShift Master: v18.104.22.168
Kubernetes Master: v1.6.1+5115d708d7
There are some other "Learn More" links on current page as below, do we need to update them?
There are also many other help links in https://github.com/openshift/origin-web-console/pull/1694/files, do we need to update them as well?
I'm not sure what the question is? As part of the PR I swept through every help link we had in the code, they are all maintained in a single file. There were several other links that no longer resolved to the correct topic so I updated them as well.
The links in origin are all correct now. The OCP links will 404 since the 3.6 docs have not been released yet.
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.