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
in our documentation we said that you should download the standard container from the bucketfs, import it to docker and compile your package within this container
In future we want to provide the container of each Exasol Version as docker image at docker hub
Acceptance Criteria
we need to upload the image during a release to docker hub with the right Exasol Version attached
we need an own docker hub repository, such the user can easily browse and search for the Exasol version
Open Questions:
How do we do the release?
a normal release releases all flavors, so if the tag would be an exasol version it is confusing
could we use special tags for exasol standard container releases? Which only releases a specific flavor for a specific version.
Situation:
Acceptance Criteria
Open Questions:
Depends
Depends on:
exasol/script-languages-container-tool#86
exasol/integration-test-docker-environment#131
Future
#396
The text was updated successfully, but these errors were encountered: