-
Notifications
You must be signed in to change notification settings - Fork 733
[WIP] CI, build NEXT #3991
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
[WIP] CI, build NEXT #3991
Conversation
ea0ae7f to
c8fba63
Compare
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
03f0c07 to
d9eeb54
Compare
Signed-off-by: apostasie <spam_blackhole@farcloser.world>
d9eeb54 to
159af36
Compare
|
Alternative for the Go version hack: |
|
Also, I thought the direction was to remove the integration test stages from the Dockerfile eventually. The Go version for the building the binaries will still have to be specified in the Dockerfile, but probably there is no need to add Go installer to the Makefile. |
The runtime test stage, yes - not the build part IMHO. Retracting (see #3986 ) |
No description provided.