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

update: what the CI does #1504

Merged
merged 2 commits into from
Sep 5, 2023
Merged

update: what the CI does #1504

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4e38a98
update: what the CI does
v1v Aug 31, 2023
2ceb04d
Merge branch 'main' into feature/docs-ci
v1v Sep 5, 2023
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
6 changes: 5 additions & 1 deletion .github/workflows/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ The whole process should look like:

`Checkout` -> `Lint` -> `Test` -> `Coverage` -> `Benchmark` -> `Release`

There are some other stages that run for every push on the main branches:

* [Snapshoty](./snapshoty.yml)
* [Microbenchmark](./microbenchmark.yml)

### Scenarios

* Matrix compatibility runs on branches, tags and PRs basis.
Expand Down Expand Up @@ -41,7 +46,6 @@ Every time there is a merge to main or any release branches the whole workflow w

This process has been fully automated and it gets triggered when a tag release has been created, Continuous Deployment based, aka no input approval required.


### OpenTelemetry

There is a GitHub workflow in charge to populate what the workflow run in terms of jobs and steps. Those details can be seen in [here](https://ela.st/oblt-ci-cd-stats) (**NOTE**: only available for Elasticians).