mirror of
https://github.com/meilisearch/MeiliSearch
synced 2024-11-05 04:28:55 +01:00
95211e2665
1703: Trigger CodeCoverage manually instead of on each PR r=irevoire a=curquiza Since no one is using it now on the PRs, we would rather get a state of the code coverage once (triggered manually) rather than on each PR. Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com> |
||
---|---|---|
.. | ||
coverage.yml | ||
flaky.yml | ||
publish-binaries.yml | ||
publish-deb-brew-pkg.yml | ||
publish-docker-latest.yml | ||
publish-docker-tag.yml | ||
README.md | ||
release-drafter.yml | ||
rust.yml |
GitHub Actions Workflow for MeiliSearch
Note:
- We do not use cache yet but we could use it to speed up CI
Workflow
- On each pull request, we trigger
cargo test
. - On each tag, we build:
- the tagged Docker image and publish it to Docker Hub
- the binaries for MacOS, Ubuntu, and Windows
- the Debian package
- On each stable release (
v*.*.*
tag):- we build the
latest
Docker image and publish it to Docker Hub - we publish the binary to Hombrew and Gemfury
- we build the
Problems
- We do not test on Windows because we are unable to make it work, there is a disk space problem.