search

Open-EO / openeo-geopyspark-driver

OpenEO driver for GeoPySpark (Geotrellis)
Apache License 2.0
25 stars 4 forks source link

include git commit sha in _backend_deploy_metadata #747

Open bossie opened 3 months ago

bossie commented 3 months ago

OpenEO capabilities e.g. https://openeo.vito.be/openeo/ includes a section with our components + their version:

"_backend_deploy_metadata": {
  "date": "2024-03-28T08:12:26Z",
  "versions": {
  "biopar": "1.3.0",
  "cropsar": "1.5.2.dev20231123+14",
  "cropsar_px": "0.1.3",
  "geopyspark": "0.4.7+openeo",
  "geotrellis-extensions-static": "2.4.0_2.12-SNAPSHOT 245c856",
  "nextland_services": "0.2.2.dev20240118+200",
  "openeo": "0.28.0",
  "openeo-geopyspark": "0.28.2a1.dev20240327+1849",
  "openeo_driver": "0.94.1a1.dev20240327+770",
  "openeo_r_udf": "0.5.0",
  "openeo_udf": "1.0.0rc3"
}

The entry for geotrellis-extensions includes the git commit sha; it would be great if the entries for e.g. openeo, openeo_driver and openeo_geopyspark would also include this. Unlike their version numbers (not always updated) or the Jenkins build number (includes multiple commits), this will unambiguously tell us which revision of the software is running.

soxofaan commented 3 months ago

FYI: this would have to be a feature in jenkinslib, where the build info injection happens, so maybe this should be a GDD request instead?