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
Currently when a docs build is triggered for a branch, the latest version of that branch will always be used. This can cause problem if a subsequent build adds meta-data and hasn't completed in time.
This happened with commit f5f888d which triggered a docs build that actually used afcc780.
If we pass the sha in when we trigger the build, we should be able to git reset the branch before starting Antora.
The text was updated successfully, but these errors were encountered:
Currently when a docs build is triggered for a branch, the latest version of that branch will always be used. This can cause problem if a subsequent build adds meta-data and hasn't completed in time.
This happened with commit f5f888d which triggered a docs build that actually used afcc780.
If we pass the sha in when we trigger the build, we should be able to
git reset
the branch before starting Antora.The text was updated successfully, but these errors were encountered: