-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Setting up Test Runner (Docker) #6
Comments
Hmmm.. I do see a java version of bqn among the Guix packages. |
Let me worry about docker. That's something I actually know how to do :) I can put together a Dockerfile, which compiles and installs CBQN. I compiled CBQN on my own machine and it was trivial. Regarding maintenance, I am used to gitlab, where if the Dockerfile changes, the docker image ist automatically build. I looked at other test-runners. For example wren another rather niche/new language also just gets the compiler from git and compiles it. |
I have opened the exercism issue to get the repository. |
Sounds good. Thanks. |
We have a repo now. I have uploaded the dockerfile there. |
so, CBQN seems to have official releases now: https://github.com/dzaima/CBQN/tags |
To get the Test Runner up we'll need to set up a Docker instance.
Currently there are no plans to set up official releases with versions for BQN, so we'll likely have to pin our builds to a specific commit. This opens up longer term questions about how we maintain this Docker instance, but I think having anything up and running is probably worth doing first.
There's a reference to a GUIX build here, but no link. Searching found references to a build, but it's not listed among the packages. Perhaps it hasn't been accepted yet? I don't know much about Guix, but if possible, I'd like to leverage other people's work.
The NIX build I found appears to be deprecated. Not sure if there's another one floating around.
And it's always an option to set up a build from scratch by hook or by crook. Nothing saying we can't change this later.
The text was updated successfully, but these errors were encountered: