New answers tagged

1

If you prefer ssh connection use this: after_script: - git --version - git remote remove origin - git remote add origin git@gitlab.com:$CI_PROJECT_PATH.git - git tag -a v-$CI_COMMIT_SHORT_SHA -m "Version created by gitlab-ci Build" - git push --tags


0

The way we do this is to use EC2 User data to run a cloud-init script after the EC2 instance has been launched. With Terraform this user data can be templated and parameterized for different environments using Terraform's templatefile and passing in variables via parameter files. I would suggest you also read up on AWS Auto scaling groups and launch ...


0

You can use when: on_failure, in your case you can create a new job for rollback when your some more tests have failed. Example: cleanup_build_job: stage: cleanup_build script: - cleanup build when failed when: on_failure For more example: https://docs.gitlab.com/ee/ci/yaml/#when


1

The answer to this question is no. I merely forgot to export the AWS_SECRET_ACCESS_KEY variable in the before_script section.


1

You are not able to create multiple .gitlab-ci.yml but you can manage to have what you want. You currently have multiple software in the same repository with the same CI/CD Pipeline or jobs for your softwares. You can use include in order to include local files from your repository, so you would get include: - local: 'my_folder/.gitlab-ci.yml' You can ...


Top 50 recent answers are included