3 ms·
I might be an absolute DevOps Newbie, but getting GitLab CI to do a simple "copy to this ssh destination" buildscript seems very complicated. From what I could
by Roritharr 11y ago
I might be an absolute DevOps Newbie, but getting GitLab CI to do a simple "copy to this ssh destination" buildscript seems very complicated.
From what I could gather it means that I have to create a specific runner whose login credentials are in its config, which aren't accessible via the WebUi, only as a file on the server where the runner is running and give it an unique tag. Then in my repofile i have to select that specific runner so it then "runs the build" on my deployment target.
Hopefully i'm completely wrong about this, but this seems horribly complicated and very inflexible for deployment purposes.
Why would I specify my deployment target in my repo?
Maybe simple deployment jobs like I'd build them in Jenkins aren't in the scope for GitLab CI?
- sytse 11y agoThanks for the feedback. Deployment with GitLab CI is still harder than it should be and we're working on it in https://gitlab.com/gitlab-org/gitlab-ce/issues/3286 https://gitlab.com/gitlab-org/gitlab-ce/issues/3286 If you want to securely store login credentials consider using secure variables http://doc.gitlab.com/ce/ci/variables/README.html http://doc.gitlab.com/ce/ci/variables/README.html
- Roritharr 11y agoWhy so complicated? As a first step Please give me a Deployments Page that gives me the option to run simples SH Scripts in the Runner on click, parameterised please. All I need is a nice GUI for my QA people that allows them to deploy(which for our PHP site basically just means copy and DB Import) Branch x on Server y. Jenkins is total Overkill for that but GitLab CI doesnt leave me with enough GUI to skip it either.
- sytse 11y agoI agree that we should have a simple page that shows you an overview, our issue for this is https://gitlab.com/gitlab-org/gitlab-ce/issues/750910 https://gitlab.com/gitlab-org/gitlab-ce/issues/750910