GitLab CI Start job manually (deployment)

gitlab continuous-deployment gitlab-ci continuous-delivery gitlab-ci-runner
Pekarcik Patrick picture Pekarcik Patrick · Apr 16, 2016 · Viewed 13.1k times · Source

Is it possible to mark gitlab ci jobs to start manually?

I need it for deploying application but I want to decide if it's going to be deployed

Answer

MOnsDaR picture MOnsDaR · Sep 30, 2016

This has changed since the first answer has been posted. Here's the link to the original Gitlab Issue. It is now supported to do something like

production:
  stage: deploy
  script: run-deployment $OMNIBUS_GITLAB_PACKAGE
  environment: production
  when: manual

Note the when: manual attribute. The UI updates itself to provide a way for users to trigger the job.

Related questions

How to deploy to Heroku directly from my Gitlab repository

In my team, we use Gitlab as a remote repository, so we are looking for a solution to auto deploy our apps to Heroku. We found Codeship for auto deploying apps to Heroku from Github. Any tips? Tricks?

Read More
Continuous Deployment of a NodeJS using GitLab

I have an API developed in NodeJS and have successfully set up continuous integration via a .gitlab-ci.yml file. The next stage is to set up continuous deployment to Heroku if all tests pass on the master branch. There are …

Read More
GitLab remote: HTTP Basic: Access denied and fatal Authentication

I am on mac OS unlike this post: 'git push origin MyBranchName' throws error "HTTP Basic: Access denied" I have password configured in GitLab. I have SSL key created AFTER the project was made on GitLab. When I use an …

Read More