You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 5 main stages that run on GitHub actions
4
+
5
+
* Build
6
+
* Lint
7
+
* Notice
8
+
* Test
9
+
* Release
10
+
11
+
There are some other stages that run for every push on the main branches:
12
+
13
+
*[Smoke Tests](./smoke-tests.yml)
14
+
15
+
### Scenarios
16
+
17
+
* Pull Requests that are only affecting the docs files should not trigger any test or similar stages that are not required.
18
+
* Builds do not get triggered automatically for Pull Requests from contributors that are not Elasticians when need to access to any GitHub Secrets.
19
+
20
+
### How to interact with the CI?
21
+
22
+
#### On a PR basis
23
+
24
+
Once a PR has been opened then there are two different ways you can trigger builds in the CI:
25
+
26
+
1. Commit based
27
+
1. UI based, any Elasticians can force a build through the GitHub UI
28
+
29
+
#### Branches
30
+
31
+
Every time there is a merge to main or any release branches the whole workflow will compile and test every entry in the compatibility matrix for Linux and MacOS.
32
+
33
+
#### Release process
34
+
35
+
This process has been fully automated and it gets triggered when a tag release has been created, for further details please refers to the [release](../../RELEASE.md) docs.
36
+
37
+
#### Smoke Tests
38
+
39
+
You can run the [smoke-tests](https://github.com/elastic/apm-aws-lambda/actions/workflows/smoke-tests.yml) using the UI if needed.
40
+
41
+
### OpenTelemetry
42
+
43
+
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).
0 commit comments