nspcc-dev/Publish Allure report to NeoFS
This action allows you to publish Allure reports to NeoFS.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| NEOFS_WALLET | N3 wallet for NeoFS network access | yes | — |
| NEOFS_WALLET_PASSWORD | N3 wallet password | yes | — |
| NEOFS_ENDPOINT | RPC endpoint for NeoFS node (e.g. grpcs://st1.storage.fs.neo.org:8082 or grpcs://private-node:9090). | no | grpcs://st1.storage.fs.neo.org:8082 |
| HTTP_URL_PREFIX | Full URL prefix used to build OUTPUT_CONTAINER_URL (e.g. https://rest.fs.neo.org/MYCID/ or https://reports.example.com/). If not set, the container URL will be built as https://rest.fs.neo.org/$STORE_OBJECTS_CID/ and if URL_PREFIX is set, it is appended to https://rest.fs.neo.org/$STORE_OBJECTS_CID/$URL_PREFIX/. | no | "" |
| STORE_OBJECTS_CID | Container ID for your data | yes | — |
| PR_LIFETIME | Expiration period for PRs in epochs | no | 0 |
| MASTER_LIFETIME | Expiration period for master branch in epochs | no | 0 |
| MANUAL_RUN_LIFETIME | Expiration period for manual runs in epochs | no | 0 |
| OTHER_LIFETIME | Expiration period for other events in epochs | no | 0 |
| ALLURE_RESULTS_DIR | Path to Allure result | yes | — |
| ALLURE_GENERATED_DIR | Path to store Allure generated report | no | ./tests/neofs-test-allure-generated-report |
Outputs
| name | description |
|---|---|
| REPORT_NEOFS_URL | Container URL |
| COMBINED_REPORT_DIR | Path to the directory with the combined Allure report and zip attachments |