CODEWITHSUNDEEP
amazon-web-servicesgitlabamazon-elastic-beanstalkgitlab-ci
Ivor Baric
Ivor Baric

Reputation: 55

Gitlab CI/CD Pipeline doesn't exit while having a custom runner available and gitlab-ci.yml existing

Maybe I'm just tired or something, but I've registered a runner on an EC2 instance on AWS and my project has a gitlab-ci.yml like below. When I commit nothing happens - like there are no pipelines according to Gitlab. Did anyone experience anything like this ?

Example gitlab-ci.yml (looks exactly the same just different project name and dev branch).

deploy:
    stage: deploy
    environment: production
    # Pull docker image
    image: 'mjsarfatti/gitlab-ci-pipeline-php-aws:latest'
    # Setup AWS CLI to have proper credential keys
    before_script:
        - 'mkdir ~/.aws/'
        - 'touch ~/.aws/credentials'
        - 'printf "[eb-cli]\naws_access_key_id = %s\naws_secret_access_key = %s\n" "$AWS_ACCESS_KEY_ID" "$AWS_SECRET_ACCESS_KEY" >> ~/.aws/credentials'
    # Run deployment using EB CLI deploy on master branch
    script:
        - 'git checkout master'
        - 'eb deploy $AWS_EB_ENVIRONMENT'
    # Ensure to run deployment only on master branch
    only:
        - master

Runner Availability

Pipeline Status

Upvotes: 1

Views: 340

Answers (1)

William Arias
William Arias

Reputation: 197

Could you try again removing the ' ' around your commands in the script

Upvotes: 1

Related Questions