-
Notifications
You must be signed in to change notification settings - Fork 83
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
with gitlab-ci #112
Comments
Working to try to recreate this, will report back how it goes. @SolarisYan: is the repo in question public? If so, it would help in narrowing down the problem. |
I have the same problem. |
Guys, i have the same issue ? Does anybody investigated this ? |
same problem here |
Anything new on this? I would also like some more debugging output and examples on how to use this |
+1 on the issue. Any one found a solution? Thanks |
The docker image Until they push a new one, you can get around it by creating your own custom image with the updated entrypoint.sh, or defining a GItlab secret variable for
|
Thanks @acaire. Why they don't push the current image? It's no longer maintained? |
hello, i want to use spread with gitlab-ci with kubernetes, i use gitlab 8.6, and gitlab-ci-multi-runner version 1.1.0~beta.236.g01105d4 (01105d4), my .gitlab-ci.yml is
variables:
KUBECFG_SERVER: http://xx:yy
deploy:
stage: deploy
image: redspreadapps/gitlabci
script:
the log as follow:
gitlab-ci-multi-runner 1.1.0~beta.236.g01105d4 (01105d4)
Using Docker executor with image redspreadapps/gitlabci ...
Pulling docker image redspreadapps/gitlabci ...
Running on runner-495c5996-project-15-concurrent-0 via gitlab.novalocal...
Cloning repository...
Cloning into '/builds/dev/ci-with-k8s'...
Checking out c65590ef as master...
Note: checking out 'c65590ef562437b653881c220df6e250ff983802'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at c65590e... b
setting up kubectl config
Using project dir...
Failed to deploy: there is nothing deployable
ERROR: Build failed: exit code 1
how this : Failed to deploy: there is nothing deployable.
how to make a deployable?
The text was updated successfully, but these errors were encountered: