You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I filed #10834 because the link check failures were so common people were ignoring them.
#10872 was put up to ignore all links from the checker that are release jars in sonatype.
That is not a good long term solution. It is us putting on blinders to not look at something that is actually wrong/broken. We don't want to have docs in the default branch of our github repo that point to unreleased jars. We need to update our process so that we can stage docs in a way so we are ready for a release, but they do not show up on the default branch where users might try to click on them until we are actually doing the release.
The text was updated successfully, but these errors were encountered:
Hi @NvTimLiu , can we try this to monitor the status of released jar links on the download webpage?(Maybe you have a better way.) Set the desired notification preferences such as email or Slack when the build fails is good enough, we don't want to block the PR checks.
Is your feature request related to a problem? Please describe.
I filed #10834 because the link check failures were so common people were ignoring them.
#10872 was put up to ignore all links from the checker that are release jars in sonatype.
That is not a good long term solution. It is us putting on blinders to not look at something that is actually wrong/broken. We don't want to have docs in the default branch of our github repo that point to unreleased jars. We need to update our process so that we can stage docs in a way so we are ready for a release, but they do not show up on the default branch where users might try to click on them until we are actually doing the release.
The text was updated successfully, but these errors were encountered: