Comments (5)
We use the Artifactory to know which versions are available, we process the JSON there and store the builds IDs when they are available. These are the snippets we use, we can give you the URL of our version file one is in the apm-pipeline-library, @v1v Do we have some other file?
We also have the updated channels we use for the bolt clusters. It is a JSON file with the latest build we have tested
7.x versions available
NO_KPI_URL_PARAM="x-elastic-no-kpi=true"
curl -sSf "https://artifacts-api.elastic.co/v1/versions?${NO_KPI_URL_PARAM}" | jq '.aliases[]|select(.|startswith("7"))'
Two latest builds for 7.17
NO_KPI_URL_PARAM="x-elastic-no-kpi=true"
VERSION=7.17
curl -sSf "https://artifacts-api.elastic.co/v1/versions/${VERSION}/builds?${NO_KPI_URL_PARAM}"|jq '.builds[:2]'
8.x versions available
NO_KPI_URL_PARAM="x-elastic-no-kpi=true"
curl -sSf "https://artifacts-api.elastic.co/v1/versions?${NO_KPI_URL_PARAM}" | jq '.aliases[]|select(.|startswith("8"))'
Two latest builds for 8.14
NO_KPI_URL_PARAM="x-elastic-no-kpi=true"
VERSION=8.15
curl -sSf "https://artifacts-api.elastic.co/v1/versions/${VERSION}/builds?${NO_KPI_URL_PARAM}"|jq '.builds[:2]'
8 SNAPSHOT versions
NO_KPI_URL_PARAM="x-elastic-no-kpi=true"
curl -sSf "https://artifacts-api.elastic.co/v1/versions?${NO_KPI_URL_PARAM}" | jq '[.aliases[]|select(.|startswith("8"))|select(.|endswith("SNAPSHOT"))]'
No 8 SNAPSHOT versions
NO_KPI_URL_PARAM="x-elastic-no-kpi=true"
curl -sSf "https://artifacts-api.elastic.co/v1/versions?${NO_KPI_URL_PARAM}" | jq '[.aliases[]|select(.|startswith("8"))|select(.|endswith("SNAPSHOT")|not)]'
latest 8 version
curl -sSf "https://artifacts-api.elastic.co/v1/versions?${NO_KPI_URL_PARAM}" | jq '[.aliases[]|select(.|startswith("8"))|select(.|endswith("SNAPSHOT")|not)][-1:]'
latest 8 SNAPSHOT version
curl -sSf "https://artifacts-api.elastic.co/v1/versions?${NO_KPI_URL_PARAM}" | jq '[.aliases[]|select(.|startswith("8"))|select(.|endswith("SNAPSHOT"))][-1:]'
from apm-server.
Do we have some other file?
Yes, there is a Google Bucket with the latest releases for 8.x
and 7.x
and the upcoming minor or patches releases:
- Current version in main: https://storage.googleapis.com/artifacts-api/releases/edge/main
- Current release for
8.x
: https://storage.googleapis.com/artifacts-api/releases/current/8 - Current release for
7.x
: https://storage.googleapis.com/artifacts-api/releases/current/7 - Next patch release for
8.x
: https://storage.googleapis.com/artifacts-api/releases/next/patch-8 - Next patch release for
7.x
: https://storage.googleapis.com/artifacts-api/releases/next/patch-7 - Next minor release for
8.x
: https://storage.googleapis.com/artifacts-api/releases/next/minor-8
Those entries change based on the artifacts-api.elastic.co
, it does some transformation to be able to use the aliases edge
, next
, current
, patch
and minor
.
from apm-server.
Regarding the build-id
, there is another entry in the Google bucket to know the latest available snapshot for a release branch:
<branch-name>
can be main
, 7.17
, 8.14
and so on.
For instance:
curl https://storage.googleapis.com/artifacts-api/snapshots/8.14.json
{
"start_time": "Thu, 25 Apr 2024 04:05:10 GMT",
"release_branch": "8.14",
"prefix": "",
"end_time": "Thu, 25 Apr 2024 05:58:07 GMT",
"manifest_version": "2.1.0",
"version": "8.14.0-SNAPSHOT",
"branch": "8.14",
"build_id": "8.14.0-055b54fd",
"build_duration_seconds": 6777
}
or
{
"start_time": "Thu, 25 Apr 2024 02:02:24 GMT",
"release_branch": "master",
"prefix": "",
"end_time": "Thu, 25 Apr 2024 04:01:35 GMT",
"manifest_version": "2.1.0",
"version": "8.15.0-SNAPSHOT",
"branch": "master",
"build_id": "8.15.0-eb13af64",
"build_duration_seconds": 7151
}
This is handy since it stores the latest available snapshot for any release branch, while artifacts-api.elastic.co
deletes any references to any branch with artefacts older than 30 days.
That's the reason we cannot query the latest snapshot for 8.9
in artifacts-api.elastic.co
but we can using the Google bucket:
curl https://storage.googleapis.com/artifacts-api/snapshots/8.9.json
{
"start_time": "Tue, 29 Aug 2023 08:20:45 GMT",
"release_branch": "8.9",
"prefix": "",
"end_time": "Tue, 29 Aug 2023 12:34:12 GMT",
"manifest_version": "2.1.0",
"version": "8.9.2-SNAPSHOT",
"branch": "8.9",
"build_id": "8.9.2-a804d52d",
"build_duration_seconds": 15207
}
from apm-server.
I assume the latest is supposed to test the latest 7.x and 8.x versions that are not yet released. We need to have smoke tests running for unreleased versions.
Upon creating #13147 , I wonder if I understand the task correctly. Do we want to test latest unreleased version (staging DRA) or latest snapshot version?
from apm-server.
Fixed via #13147
from apm-server.
Related Issues (20)
- Document release process with the automation workflow HOT 4
- [DOCS] Create openAPI specifications for public APM APIs
- Fix automation, bring back openAPI spec HOT 1
- API UI failing for error events derived from traces with Jaeger agent
- APM Server 8.14.0 Test Plan HOT 7
- ci: minor-release automation is not aligned with expectations HOT 4
- ci: minor-release automation does not sign commits HOT 3
- release: review test plan template
- Consider flattening headers and cookies HOT 8
- Perf regression, too many small bulk requests HOT 7
- Document 7.17.20 being broken for apm-server managed by Fleet with self-signed certificates HOT 1
- APM Event Intake: All errors are considered exceptions. HOT 1
- APM Integration Check Not Compatible With Elastic APM Data Option HOT 4
- Flaky tests due to changes in the geoip database
- custom ILM policy for specific event types in integrated APM server HOT 1
- Kibana does not remove index template for removed data streams on integrations upgrade HOT 2
- Update docs to remove requirement for installing the integration HOT 1
- Validate go-docappender metrics are produced when monitoring is enabled HOT 3
- Revisit docappender config autosizing values
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from apm-server.