Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document generation reports succeeded, but docs are not found #2358

Closed
markweitzel opened this issue Dec 1, 2021 · 5 comments
Closed

Document generation reports succeeded, but docs are not found #2358

markweitzel opened this issue Dec 1, 2021 · 5 comments
Assignees

Comments

@markweitzel
Copy link
Member

In PR #16705 the pipleline reports that it succeeds, however the docs do not appear to be generated and/or in the right place.

image

image

image

@weshaggard
Copy link
Member

@akning-ms @zhenglaizhang who on your side is the right person to investigate this?

@weshaggard weshaggard removed their assignment Dec 1, 2021
@zhenglaizhang
Copy link
Contributor

@akning-ms @zhenglaizhang who on your side is the right person to investigate this?

@weshaggard I will take a look at this

@zhenglaizhang
Copy link
Contributor

Hi @markweitzel I talked with docs team, it's due to the side effect of docs side config branch manual cleanup, I didn't realize that the removal of config branch will leads to page deletion. Now your preview is recovered Azure/azure-rest-api-specs#16705 (comment)
I will use a safer way to do the cleanup automatically.

@markweitzel
Copy link
Member Author

Great! Thank you for looking at this so quickly.

One quick question... What is required of a team to regenerate their docs if the link does not work? I'd like to be able to instruct a team and/or do it for them.

Also, if this is fixed going forward, please feel free to close the issue.

Thanks

@zhenglaizhang
Copy link
Contributor

Great! Thank you for looking at this so quickly.

One quick question... What is required of a team to regenerate their docs if the link does not work? I'd like to be able to instruct a team and/or do it for them.

Also, if this is fixed going forward, please feel free to close the issue.

Thanks

You just need to comment PR with /azp run to rerun the generation, e.g. Azure/azure-rest-api-specs#16705 (comment)
Yes going forward I wont remove such branches, so there wont be such problem, closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants