action: edge

[v1v]

What

Migrate the edge stage to GitHub actions and will run based on the below events:

1. merge commits in main
2. manually

Checklist

• Implement code
• Add tests
• Update TypeScript typings
• Update documentation
• Add CHANGELOG.asciidoc entry
• Commit message follows commit guidelines

Test

See https://github.com/elastic/apm-agent-nodejs/actions/workflows/edge.yml

Follow ups

• when github command /test-nightly or /test-rc

[v1v]

/test-rc

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-26T08:18:19.717+0000

• Duration: 23 min 28 sec

Test stats 🧪

Test	Results
Failed	0
Passed	323266
Skipped	0
Total	323266

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run module tests for <modules> : Run TAV tests for one or more modules, where <modules> can be either a comma separated list of modules (e.g. memcached,redis) or the string literal ALL to test all modules

• run benchmark tests : Run the benchmark test only.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

/test-rc

[v1v]

/test-rc

[v1v]

/test-nightly

[v1v]

/test-rc

[trentm]

@v1v Is there a pattern that other APM projects use for the "/test..." commands for rebuilds that we could follow for consistency? I notice that apm-agent-python, for example uses:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

... plus the `run` `elasticsearch-ci/docs` one that is out of that repo's control

Ah, and Java and others seem to have "/ test" and "run ..." things.

For what it is worth I like the / test [OPTIONS] or / test-OPTION pattern if that is workable. Probably because it hints towards IRC and Slack commands.

[trentm]

This is great.

[v1v]

@v1v Is there a pattern that other APM projects use for the "/test..." commands for rebuilds that we could follow for consistency?

run ... was the first github command pattern then we moved to
/test ... but kept the run for backward compatibility. Some of those github commands are documented in the oblt-dev repo and https://github.com/elastic/apm-pipeline-library/blob/15602fdc2deeb020c9b67c0ae24bc88f0a2b5fcd/src/co/elastic/NotificationManager.groovy#L491

I think we are in a good position to normalise those names.

OTOH, I tried to configure the github commands within this PR but it seems it won't work until it's available in the default branch :/ For now I'll not implement this now as I'd like to think about your proposal elastic/apm-pipeline-library#1904
so we can use something similar shortly.