You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SLC have tons of dependencies, from different sources (Ubuntu, CRAN, PyPi, GCloud(Swig), Docker, Github , Exasol Website).
Many times one of those sources has connection issues, and hence the Nightly/CI build break.
We could try to host some small, stable artifacts on S3, and pull them during the build from there. Currently this is already done for SWIG. Also, some Exasol specific artificats could be hosted there (Check https://console.cloud.google.com/cloud-build/builds;region=global/fcae648f-da77-4ec6-bee3-a8ddf0a77312?project=script-languages-build)
Acceptance Criteria
Create a public bucket on S3 (public readonly access)
Deploy specific artifacts there:
Exasol ODBC driver
SWIG
Change path in Dockerfiles to pull artifacts from there
Note: Exasol JDBC Driver will be moved to Maven Central, and can be fetched from there.
The text was updated successfully, but these errors were encountered:
Background
SLC have tons of dependencies, from different sources (Ubuntu, CRAN, PyPi, GCloud(Swig), Docker, Github , Exasol Website).
Many times one of those sources has connection issues, and hence the Nightly/CI build break.
We could try to host some small, stable artifacts on S3, and pull them during the build from there. Currently this is already done for SWIG. Also, some Exasol specific artificats could be hosted there (Check https://console.cloud.google.com/cloud-build/builds;region=global/fcae648f-da77-4ec6-bee3-a8ddf0a77312?project=script-languages-build)
Acceptance Criteria
Note: Exasol JDBC Driver will be moved to Maven Central, and can be fetched from there.
The text was updated successfully, but these errors were encountered: