Skip to content
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

Open
SolarisYan opened this issue Mar 25, 2016 · 8 comments
Open

with gitlab-ci #112

SolarisYan opened this issue Mar 25, 2016 · 8 comments

Comments

@SolarisYan
Copy link

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:

  • env

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?

@ethernetdan
Copy link
Member

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.

@oandric
Copy link

oandric commented May 19, 2016

I have the same problem.
I have one *.rc.yaml file in root of my project, and one service in rs folder and it says that there is nothing deployable.
More info:
gitlab-ci-multi-runner 1.1.4 (9e2fd1a)
Using Docker executor with image redspreadapps/gitlabci ...
setting up kubectl config
Using project dir...
Failed to deploy: there is nothing deployable
ERROR: Build failed: exit code 1

@ProgressiveAstronaut
Copy link

Guys, i have the same issue ? Does anybody investigated this ?

@iliocatallo
Copy link

same problem here

@almenjonatan
Copy link

Anything new on this?

I would also like some more debugging output and examples on how to use this

@SaMnCo
Copy link

SaMnCo commented Dec 16, 2016

+1 on the issue. Any one found a solution?

Thanks

@acaire
Copy link

acaire commented Feb 3, 2017

The docker image redspreadapps/gitlabci:latest has a different version of entrypoint.sh than what's currently in the git repo - This means it defaults to / instead of $CI_PROJECT_DIR/ if DEPLOY_DIR isn't defined.

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 DEPLOY_DIR with the value of your project's CI_PROJECT_DIR variable, i.e. mine was basically:

DEPLOY_DIR = /builds/my-projects/helloworld

@umatomba
Copy link

Thanks @acaire.

Why they don't push the current image? It's no longer maintained?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants