elastic / elastic/integrations

Exact build version is not emitted for some builds

Open
#13,553 1 comment 0 reactions 0 assignees View on GitHub
ci Stalled Team:Ecosystem
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

In CI, the build logs include the stack component versions, but for some builds the version is essentially constant. For example in a flaky test report for the serverless flavour, I see this

```
╭───────────────┬───────────────────────┬───────────────────╮
│ SERVICE │ VERSION │ STATUS │
├───────────────┼───────────────────────┼───────────────────┤
│ kibana │ serverless (security) │ healthy │
│ fleet │ serverless (security) │ healthy │
│ elasticsearch │ serverless (security) │ healthy │
│ elastic-agent │ 8.17.4 │ running (healthy) │
╰───────────────┴───────────────────────┴───────────────────╯
```
This version gives no useful information to allow a developer to be able to correlate the behaviour with the artefact that gives the behaviour. The version should include either a tag or a sha for each of the artefacts (preferably both).

Ideally, the information about version would be reported to the github issue/pull request that reports the CI outcome since the details shown here are burried deep in extensive logs that are not persisted indefinitely, resulting is unnecessary work and potentially lost useful information.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.