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.

Sign up for GitHub

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

Trimming for long-term storage #968

Open
wants to merge 2 commits into
base: slim_pages
Choose a base branch
from
Open

Trimming for long-term storage #968

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
569e8bb
trimmed for long-term storage
therealryan Oct 16, 2024
1744914
fixed linken
therealryan Oct 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@

This branch holds our pages content.
That used to be a rotating set of build artifacts maintained by [this script](regen_index.pl), but since [#940](https://github.com/Mastercard/flow/pull/940) all we need is:
* Static links to the latest artifacts (as determined by bowlby)
* The report content from [#568](https://github.com/Mastercard/flow/pull/568), used as a demo for the report-diffing feature
* A static set of execution reports. These are updated by [the `state_artifacts` workflow](https://github.com/Mastercard/flow/actions/workflows/static_artifacts.yml) whenever something significant changes in the report. We link to these in our documentation as we don't _entirely_ trust the bowlby instance to always be available.
* A static set of execution reports. These are updated by [the `static_artifacts` workflow](https://github.com/Mastercard/flow/actions/workflows/static_artifacts.yml) whenever something significant changes in the report. We link to these in our documentation as we don't _entirely_ trust the bowlby instance to always be available.

23 changes: 10 additions & 13 deletions index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,16 @@
# Build artifacts

One of the main features of the [flow testing framework](https://github.com/Mastercard/flow) is the production of rich execution reports.
Until such a time as [upload-artifact#14](https://github.com/actions/upload-artifact/issues/14) is addressed, we're using the [bowlby](https://github.com/therealryan/bowlby) instance at [https://bowlby.flowty.dev/flow](https://bowlby.flowty.dev/flow) to serve our workflow results.
Until such a time as [upload-artifact#14](https://github.com/actions/upload-artifact/issues/14) is addressed, we're maintaining a set of static reports for demo purposes here.

See the latest results here:
* [Testing](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml)
* [Integrated system](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-itest/target/mctf/latest/index.html)
* [Core service](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-core/target/mctf/latest/index.html)
* [Histogram service](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-histogram/target/mctf/latest/index.html)
* [Queue service](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-queue/target/mctf/latest/index.html)
* [Store service](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-store/target/mctf/latest/index.html)
* [UI service](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-ui/target/mctf/latest/index.html)
* [Web UI service](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/flow_execution_reports/app-web-ui/target/mctf/latest/index.html)
* [Report UI](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/test.yml/angular_coverage/report/index.html)
* [Mutation](https://bowlby.flowty.dev/flow/latest/Mastercard/flow/mutation.yml/mutation_report/index.html)
These reports are generated whenever [the `static_artifacts` workflow](https://github.com/Mastercard/flow/actions/workflows/static_artifacts.yml) is run:

Look at the workflow run summaries for the results of historic runs.
* [Integrated system](https://mastercard.github.io/flow/static/app-itest/target/mctf/latest/index.html)
* [Core service](https://mastercard.github.io/flow/static/app-core/target/mctf/latest/index.html)
* [Histogram service](https://mastercard.github.io/flow/static/app-histogram/target/mctf/latest/index.html)
* [Queue service](https://mastercard.github.io/flow/static/app-queue/target/mctf/latest/index.html)
* [Store service](https://mastercard.github.io/flow/static/app-store/target/mctf/latest/index.html)
* [UI service](https://mastercard.github.io/flow/static/app-ui/target/mctf/latest/index.html)
* [Web UI service](https://mastercard.github.io/flow/static/app-web-ui/target/mctf/latest/index.html)

The same content (along with mutation testing and angular unit testing reports) is available as artifacts from the appropriate workflows.