zecfoundation
/
zebra
mirror of https://github.com/ZcashFoundation/zebra.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zebra/.github/workflows/ci-coverage.patch.yml

24 lines
434 B
YAML
Raw Normal View History

fix (actions): add duplicated workflows with path-ignore (#3405) GitHub does not support skipped but required checks by default, this an official workaround to allow this feature; which requires to duplicate the same workflow using path-ignore and just executing a step that will always pass, for each job. Reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
2022-01-25 19:19:43 -08:00
name: Coverage
on:
pull_request:
fix(actions): typo on paths filtering (#3516) The keyword is `paths` and the actions were using `path` That's the reason why most actions have been running, and there's been no impact in time savings
2022-02-11 06:05:19 -08:00
paths-ignore:
fix (actions): add duplicated workflows with path-ignore (#3405) GitHub does not support skipped but required checks by default, this an official workaround to allow this feature; which requires to duplicate the same workflow using path-ignore and just executing a step that will always pass, for each job. Reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
2022-01-25 19:19:43 -08:00
- '**/*.rs'
- '**/*.txt'
fix(ci): update CI job path triggers (#3692) * ci(test): re-run tests when snapshot data changes * fix(ci): rebuild state when disk format changes * fix(ci): rebuild rust docs when code or dependencies change * doc(ci): explain why we run jobs when files change Co-authored-by: Gustavo Valverde <gustavo@iterativo.do>
2022-03-02 06:23:05 -08:00
- '**/*.snap'
fix (actions): add duplicated workflows with path-ignore (#3405) GitHub does not support skipped but required checks by default, this an official workaround to allow this feature; which requires to duplicate the same workflow using path-ignore and just executing a step that will always pass, for each job. Reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
2022-01-25 19:19:43 -08:00
- '**/Cargo.toml'
- '**/Cargo.lock'
ci(test): run build and test jobs on cargo and clippy config changes (#4941) Previous behavior: If warnings or error are added in `.cargo/config.toml` or `clippy.toml`, and those could generate CI failures, we wouldn't catch those new as the pipelines are not run when this files are changed Expected behavior: If warnings or error are added in `.cargo/config.toml` or `clippy.toml`, run all the builds and test jobs which also track a `Cargo.toml`. Solution: Add `.cargo/config.toml` and `clippy.toml` as paths to all the required jobs which needs to be triggered when these files changes. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-08-26 11:06:32 -07:00
# configuration files
- '.cargo/config.toml'
- '**/clippy.toml'
fix (actions): add duplicated workflows with path-ignore (#3405) GitHub does not support skipped but required checks by default, this an official workaround to allow this feature; which requires to duplicate the same workflow using path-ignore and just executing a step that will always pass, for each job. Reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
2022-01-25 19:19:43 -08:00
- 'codecov.yml'
ref(workflows): consolidate workflows based on their purpose (#7616) * ref(workflows): consolidate workflows based on their purpose This also renames the workflows to make their naming more consistent and adding a naming convention Fixes: #6166 Fixes: #6167 * fix(workflows): use correct name for patch * fix(workflow): docker unit tests * fix(release): validation error Error: ``` Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} ``` Fixes: https://github.com/release-drafter/release-drafter/issues/1125 * fix(workflows): reference correct name * fix: remove extra workflow * fix(workflows): use larger runners * fix(workflow): remove code already in docker unit-test * fix(unit-tests): start zebra the right way * fix: typo in patch name * chore: move job to logical order * imp(workflows): use better name for gcp tests * add: missing merge changes * chore: use better name for find-disks * fix(ci): use the `entrypoint.sh` to change the Network * fix(ci): add missing `ZEBRA_CONF_PATH` variable * fix(ci): allow to build the entrypoint file with testnet * fix(entrypoint): allow to create a dir and file with a single variable * refactor: test config file in CI and CD with a reusable workflow * fix(ci): wrong name used * fix(ci): use checkout * fix(ci): improve docker config tests * fix(ci): use better name for protection rules * Fix changed workflow file name in docs patch file * Apply suggestions from code review Co-authored-by: teor <teor@riseup.net> Co-authored-by: Arya <aryasolhi@gmail.com> * fix(cd): depend on file tests * fix(docs): adapt to new workflow name * fix: revert test coverage on CD * chore: reduce diff * fix(ci): allow using variable images for reusable workflows * fix(dockerfile): use variables or default for config path and file * fix(entrypoint): if `$ZEBRA_CONF_PATH` is set, do not override it * Fix patch job names and remove failure job testnet dependencies --------- Co-authored-by: teor <teor@riseup.net> Co-authored-by: Arya <aryasolhi@gmail.com>
2023-10-17 23:16:02 -07:00
- '.github/workflows/ci-coverage.yml'
fix (actions): add duplicated workflows with path-ignore (#3405) GitHub does not support skipped but required checks by default, this an official workaround to allow this feature; which requires to duplicate the same workflow using path-ignore and just executing a step that will always pass, for each job. Reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
2022-01-25 19:19:43 -08:00
jobs:
coverage:
change(ci): run coverage on stable (#4465) * Run coverage on stable * Update .github/workflows/coverage.yml Co-authored-by: teor <teor@riseup.net> * fix(ci): sync patch file * fix(ci): timeout and docs Co-authored-by: teor <teor@riseup.net> Co-authored-by: Gustavo Valverde <gustavo@iterativo.do> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-05-25 17:28:02 -07:00
name: Coverage on stable
fix (actions): add duplicated workflows with path-ignore (#3405) GitHub does not support skipped but required checks by default, this an official workaround to allow this feature; which requires to duplicate the same workflow using path-ignore and just executing a step that will always pass, for each job. Reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
2022-01-25 19:19:43 -08:00
runs-on: ubuntu-latest
steps:
fix(actions): run coverage collection when pushing to main (#3561) * Run Coverage collection on main Resolves #3533 * fix(coverage): just run coverage on specific file changes to main Co-authored-by: Gustavo Valverde <gustavo@iterativo.do>
2022-02-22 01:48:00 -08:00
- run: 'echo "No build required"'