MeiliSearch/.github/workflows
bors[bot] 95211e2665
Merge #1703
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>
2021-09-27 13:55:05 +00:00
..
coverage.yml Trigger CodeCoverage manually instead of on each PR 2021-09-14 18:59:20 +02:00
flaky.yml run cargo flaky only 100 times 2021-06-21 17:36:54 +02:00
publish-binaries.yml Proposed fix for ARM binary on RHEL 2021-09-02 01:01:46 +00:00
publish-deb-brew-pkg.yml Remove COMMIT_SHA and COMMIT_DATE build arg 2021-08-31 17:01:58 +02:00
publish-docker-latest.yml Remove COMMIT_SHA and COMMIT_DATE build arg 2021-08-31 17:01:58 +02:00
publish-docker-tag.yml Remove COMMIT_SHA and COMMIT_DATE build arg 2021-08-31 17:01:58 +02:00
README.md Update release process for stable releases 2020-05-12 11:10:55 +02:00
release-drafter.yml Update release-drafter.yml 2021-03-16 14:46:08 +01:00
rust.yml chore(ci): use smarter dependencies cache 2021-09-07 19:56:38 +03:00

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

Problems

  • We do not test on Windows because we are unable to make it work, there is a disk space problem.