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
The reference validation is done on all Pull Requests for a while. So, new errors should not be introduced.
Notice that if reference errors are found, this doesn't prevent the PR from being merge. So, theoretically, nothing prevents from introducing errors in production but this never happened in the past.
However, it doesn't prevent errors from occurring when porting changes from a version to a new one. This recently happened (see bonitasoft/bonita-doc#2825 for the whole investigation and fix) and broken references (due to missing AsciiDoc attribute) were introduced in production.
In the past, we have only set the production build to fail when Antora generates errors.
There were some old/out-of-support documentation content branches that generated warnings. As they are no longer updated, they prevented to enable "fail on warnings".
Such branches may not exist, and if so, there could be a few warnings to fix.
Tasks
Review production build logs to identify the repository and branches that generate warnings. See files below
All branches of the documentation content repositories have been
reviewed and fixed to no longer generate warnings. Enabling this feature
will prevent from introducing new warnings without being notified.
This has no impact on preview builds: they already configure the log
level that make the build fail.
### Notes
Closes#776
As mentioned in #237
However, it doesn't prevent errors from occurring when porting changes from a version to a new one. This recently happened (see bonitasoft/bonita-doc#2825 for the whole investigation and fix) and broken references (due to missing AsciiDoc attribute) were introduced in production.
In the past, we have only set the production build to fail when Antora generates errors.
There were some old/out-of-support documentation content branches that generated warnings. As they are no longer updated, they prevented to enable "fail on warnings".
Such branches may not exist, and if so, there could be a few warnings to fix.
Tasks
Initial production Logs and warnings detection
The text was updated successfully, but these errors were encountered: