gitlab-ci regression, trying to run dpl in deploy script
I have looked at the existing issues, and did not find one matching what I'm encountering, so here I am.
Summary
When pushing to heroku using gitlab-ci, I'm using the dpl
gem, and it's not working anymore, whereas it was working only two days ago.
Steps to reproduce
gitlab-ci.yml script:
before_script:
- apt-get update
- apt-get install apt-transport-https
- echo "deb https://cli-assets.heroku.com/branches/stable/apt ./" > /etc/apt/sources.list.d/heroku.list
- wget -O- https://cli-assets.heroku.com/apt/release.key | apt-key add -
- apt-get update
- apt-get install -y heroku
- gem install dpl
production:
type: deploy
variables:
HEROKU_API_KEY: $HEROKU_PRODUCTION_API_KEY
script:
- heroku run --app=$HEROKU_PRODUCTION_APP bundle exec rake resque:unregister_workers
- heroku maintenance:on --app=$HEROKU_PRODUCTION_APP
- heroku dyno:scale --app=$HEROKU_PRODUCTION_APP web=0 worker=0
- heroku pg:backups:capture --app=$HEROKU_PRODUCTION_APP
- dpl --provider=heroku --app=$HEROKU_PRODUCTION_APP --api-key=$HEROKU_PRODUCTION_API_KEY
- […] # other actions non-relevant to this issue
only:
- tags
What is the current bug behavior?
here's the job's log output:
Running with gitlab-runner 10.8.0-rc3 (5470b911)
on docker-auto-scale 72989761
Using Docker executor with image ruby:2.5 ...
Pulling docker image ruby:2.5 ...
Using docker image sha256:dbba669987acb32d37b3f9dad5cc40a49feb70687d87e706bf9c744cf9ab5a9c for ruby:2.5 ...
Running on runner-72989761-project-4050705-concurrent-0 via runner-72989761-srm-1527194876-8532b586...
Cloning repository...
Cloning into '/builds/PROJECT/PROJECT'...
Checking out 11a4a31f as 16.6.6...
Skipping Git submodules setup
$ apt-get update
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://deb.debian.org/debian stretch Release.gpg [2434 B]
Get:6 http://deb.debian.org/debian stretch-updates/main amd64 Packages [12.1 kB]
Get:7 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [440 kB]
Get:8 http://deb.debian.org/debian stretch/main amd64 Packages [9530 kB]
Fetched 10.3 MB in 1s (7898 kB/s)
Reading package lists...
$ apt-get install apt-transport-https
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
apt-transport-https
0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
Need to get 171 kB of archives.
After this operation, 243 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian stretch/main amd64 apt-transport-https amd64 1.4.8 [171 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 171 kB in 0s (2395 kB/s)
Selecting previously unselected package apt-transport-https.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29391 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_1.4.8_amd64.deb ...
Unpacking apt-transport-https (1.4.8) ...
Setting up apt-transport-https (1.4.8) ...
$ echo "deb https://cli-assets.heroku.com/branches/stable/apt ./" > /etc/apt/sources.list.d/heroku.list
$ wget -O- https://cli-assets.heroku.com/apt/release.key | apt-key add -
[…]
$ apt-get update
[…]
$ apt-get install -y heroku
[…]
Unpacking heroku (7.0.57-1) ...
Setting up heroku (7.0.57-1) ...
$ gem install dpl
Successfully installed dpl-1.9.6
1 gem installed
$ heroku run --app=$HEROKU_PRODUCTION_APP bundle exec rake resque:unregister_workers
Running bundle exec rake resque:unregister_workers on PROJECT... starting, run.8509 (Standard-1X)
Running bundle exec rake resque:unregister_workers on PROJECT... connecting, run.8509 (Standard-1X)
Running bundle exec rake resque:unregister_workers on PROJECT... up, run.8509 (Standard-1X)
[…]
$ heroku maintenance:on --app=$HEROKU_PRODUCTION_APP
Enabling maintenance mode for PROJECT... done
$ heroku dyno:scale --app=$HEROKU_PRODUCTION_APP web=0 worker=0
Scaling dynos... done, now running web at 0:Performance-M, worker at 0:Standard-1X
$ heroku pg:backups:capture --app=$HEROKU_PRODUCTION_APP
Starting backup of postgresql-PROJECT... done
[…]
$ dpl --provider=heroku --app=$HEROKU_PRODUCTION_APP --api-key=$HEROKU_PRODUCTION_API_KEY
/bin/bash: line 90: dpl: command not found
ERROR: Job failed: exit code 1
What is the expected correct behavior?
Running with gitlab-runner 10.7.0 (7c273476)
on docker-auto-scale 4e4528ca
Using Docker executor with image ruby:2.5 ...
Pulling docker image ruby:2.5 ...
Using docker image sha256:fb664b54b956d2571c75d565162bb96036cc3967ce6b231178c6e7ef0ec69431 for ruby:2.5 ...
Running on runner-4e4528ca-project-4050705-concurrent-0 via runner-4e4528ca-srm-1526509647-3c045469...
Cloning repository...
Cloning into '/builds/PROJECT/PROJECT'...
Checking out 30d5c978 as 16.6.4...
Skipping Git submodules setup
$ apt-get update
[…]
$ apt-get install apt-transport-https
[…]
Unpacking apt-transport-https (1.4.8) ...
Setting up apt-transport-https (1.4.8) ...
$ echo "deb https://cli-assets.heroku.com/branches/stable/apt ./" > /etc/apt/sources.list.d/heroku.list
$ wget -O- https://cli-assets.heroku.com/apt/release.key | apt-key add -
[…]
$ apt-get update
[…]
$ apt-get install -y heroku
[…]
Unpacking heroku (7.0.46-1) ...
Setting up heroku (7.0.46-1) ...
$ gem install dpl
Successfully installed dpl-1.9.6
1 gem installed
$ heroku run --app=$HEROKU_PRODUCTION_APP bundle exec rake resque:unregister_workers
Running bundle exec rake resque:unregister_workers on PROJECT... starting, run.6849 (Standard-1X)
Running bundle exec rake resque:unregister_workers on PROJECT... connecting, run.6849 (Standard-1X)
Running bundle exec rake resque:unregister_workers on PROJECT... up, run.6849 (Standard-1X)
[…]
$ heroku maintenance:on --app=$HEROKU_PRODUCTION_APP
Enabling maintenance mode for PROJECT... done
$ heroku dyno:scale --app=$HEROKU_PRODUCTION_APP web=0 worker=0
Scaling dynos... done, now running web at 0:Performance-M, worker at 0:Standard-1X
$ heroku pg:backups:capture --app=$HEROKU_PRODUCTION_APP
[…]
$ dpl --provider=heroku --app=$HEROKU_PRODUCTION_APP --api-key=$HEROKU_PRODUCTION_API_KEY
Installing deploy dependencies
[…]
-----> Launching...
Released v541
https://PROJECT.herokuapp.com/ deployed to Heroku
No stash found.
[…]
Job succeeded
Output of checks
This bug happens on GitLab.com
Edited by Guyz Zmo