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

CI: Publish reports #2568

Closed
nomeata opened this issue Jun 9, 2021 · 2 comments
Closed

CI: Publish reports #2568

nomeata opened this issue Jun 9, 2021 · 2 comments
Labels
P1 high priority, resolve before the next milestone testing Related to test suite

Comments

@nomeata
Copy link
Collaborator

nomeata commented Jun 9, 2021

Our old CI was able to publish reports of various kinds (profiling reports, rendered documentation etc.) for each build. It even had a stable URL for “latest build report on branch X”, which we could link from the top-level README.

It would be good to recreate that using our Github Actions CI somehow. I am not sure what the best way is, though, so this needs some good ideas/research.

@nomeata nomeata mentioned this issue Jun 9, 2021
8 tasks
@rossberg rossberg added P1 high priority, resolve before the next milestone testing Related to test suite labels Jun 29, 2021
@nomeata
Copy link
Collaborator Author

nomeata commented Aug 21, 2021

@krpeacock recommends netlify, which we already use in the agent-* repos.

If someone in the org can configure the NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID secrets for the motoko repo, I can set up the deployment.

@nomeata
Copy link
Collaborator Author

nomeata commented May 24, 2022

I guess with #3113 I can close this. We could also use netlify if we want per-PR reports, but so far that is not a strong demand, it seems.

@nomeata nomeata closed this as completed May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 high priority, resolve before the next milestone testing Related to test suite
Projects
None yet
Development

No branches or pull requests

2 participants