Background
Currently, the only way to discover the version of a (pre-)installed SLC is to search for the SLC directory in the (default) BucketFS.
The slc connection string for the preinstalled SLC, which can be found in the database system tables, is like:
PYTHON=builtin_python R=builtin_r JAVA=builtin_java PYTHON3=builtin_python3
-> It does not contain any useful information.
We should somehow store the version information when creating a release SLC under /build_info and optionally provide an UDF in exa-toolbox which prints the version stored under /build_info.
Acceptance Criteria
Under discussion
- Extend docker_build task with new parameter
version, which then will be copied to /build_info
- Adjust script-languages-container-ci to forward the version info to
build and release.
Background
Currently, the only way to discover the version of a (pre-)installed SLC is to search for the SLC directory in the (default) BucketFS.
The slc connection string for the preinstalled SLC, which can be found in the database system tables, is like:
-> It does not contain any useful information.
We should somehow store the version information when creating a release SLC under
/build_infoand optionally provide an UDF in exa-toolbox which prints the version stored under/build_info.Acceptance Criteria
Under discussion
version, which then will be copied to/build_infobuildandrelease.