We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
you did an amazing work. I currently do some testing (using docker based on different version of node, npm etc.)
To Help supporting these, is it possible to start
the only way to mark an image as "a specific version to test" is the commit ID ...
If we are start using a real version schema, i can also start pushing images to docker-hub.
So creating a SparkSever Running a specific version will be only a "one-line" like
docker run spark-server:1.0.1
The text was updated successfully, but these errors were encountered:
Yeah, sounds good. The code is churning so fast right now that it will be a pain to version everything.
I think once we close a few of these current issues we'll put out a release.
Sorry, something went wrong.
No branches or pull requests
Hi,
you did an amazing work.
I currently do some testing (using docker based on different version of node, npm etc.)
To Help supporting these, is it possible to start
the only way to mark an image as "a specific version to test" is the commit ID ...
If we are start using a real version schema, i can also start pushing images to docker-hub.
So creating a SparkSever Running a specific version will be only a "one-line" like
The text was updated successfully, but these errors were encountered: