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

Provide easy public access to CI artifacts #250

Closed
BenjaminPelletier opened this issue Oct 12, 2023 · 1 comment
Closed

Provide easy public access to CI artifacts #250

BenjaminPelletier opened this issue Oct 12, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@BenjaminPelletier
Copy link
Member

Is your feature request related to a problem? Please describe.
uss_qualifier produces a large amount of useful output on every CI invocation, which happens (among other times) whenever a PR is merged to the main branch. This includes artifacts like templated reports, tested requirements reports, sequence view reports, HTML representations of the raw report structure, and the raw reports themselves, usually in .json format. However, it is currently somewhat difficult to show these outputs to users (developers, regulators, etc) because they are not part of the repo and can only be obtained by either running uss_qualifier directly or navigating into the most recent CI run, downloading the applicable artifact, unzipping it locally, and finding the desired artifact.

Describe the solution you'd like
It would be fantastic to have a fixed public URL that would make the artifacts produced by the CI run for the most recent commit to the main branch accessible. For HTML artifacts, a subpath of this fixed public URL should directly show the artifact in the browser (rather than having to download a zip and view the HTML locally).

Describe alternatives you've considered
This seems like it shouldn't be too unusual of a use case, so perhaps GitHub already has tools that do this. Or, perhaps use readthedocs.io. Or perhaps create an "artifacts" GitHub repo and commit into it from the GitHub CI worker. Or, perhaps host (and possibly even make, in an extreme case) our own simple webserver that can receive pushes from the GitHub CI worker to update its content.

@BenjaminPelletier BenjaminPelletier added the enhancement New feature or request label Oct 12, 2023
@BenjaminPelletier
Copy link
Member Author

Resolved by #252

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

No branches or pull requests

1 participant