Gitlab CI about spread HOT 6 OPEN

My understanding is

• you will run spread via gitlab runner
• put your credentials etc as project variable. see http://docs.gitlab.com/ce/ci/variables/README.html

from spread.

My first concern, that doesn't seem too safe to have deployment credentials in your code base. I'm working on a fork. It also doesn't seem like deployment works all too well with spread. You also can't choose a namespace.

from spread.

I haven't used this feature, but project variables seems to live in gitlab, not in source code, and will be injected to CI env.

from spread.

hey @clanstyles - thanks for bringing this up. Going to look into this over the next few days. sorry for the delayed response!

from spread.

You can indeed setup Variables for your project in Gitlab, so everything looks good on that part.

I do however seem to run into an issue because the spread command is initiated from the entrypoint instead of the Gitlab CI script section of my build. This takes away the possibility to do conditional deploys using trigger variables in Gitlab. It would be better to not actually run the command automatically and just let the user define it in the script section themselves.

from spread.

I believe this issue can be closed - actually after renaming it into something like "GitLab CI - credentials management" to reflect the actual contents..

@T-Grave could you open another issue for that?

from spread.