Closed yegor256 closed 5 years ago
@rultor release, tag is 0.4.2
@rultor release, tag is
0.4.2
@yegor256 OK, I will release it now. Please check the progress here
@rultor release, tag is
0.4.2
@yegor256 Oops, I failed. You can see the full log here (spent 7min)
remote: Default types for buildpack -> console, rake\u001b[K
remote:
remote: -----> Compressing...\u001b[K
remote: Done: 37.8M\u001b[K
remote: -----> Launching...\u001b[K
remote: Released v123\u001b[K
remote: https://zerorsk.herokuapp.com/ deployed to Heroku\u001b[K
remote:
remote: Verifying deploy... done.\u001b[K
To heroku.com:zerorsk.git
+ 2a3204f...8c2fd97 __rultor -> master (forced update)
+ git reset HEAD~1
+ rm -f target/pgsql-config.yml
+ LC_ALL=en_US.UTF-8
+ bundle exec rake liquibase
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building pgtk 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- liquibase-maven-plugin:3.2.2:update (update) @ pgtk ---
[INFO] ------------------------------------------------------------------------
[INFO] Executing on Database: jdbc:postgresql://ec2-54-197-234-117.compute-1.amazonaws.com:5432/d1ml7e466rish3?user=frhhktcnppxbwt&password=1936d8add2e4b3cf43ed799582f1475c497d75d3086de7ecfe87b322becc5e8c&ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory
INFO 5/3/19 5:54 AM: liquibase: Successfully acquired change log lock
INFO 5/3/19 5:54 AM: liquibase: Reading from databasechangelog
INFO 5/3/19 5:54 AM: liquibase: Successfully released change log lock
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.502 s
[INFO] Finished at: 2019-05-03T05:54:32+00:00
[INFO] Final Memory: 13M/152M
[INFO] ------------------------------------------------------------------------
+ rm -rf config.yml
+ curl -f --connect-timeout 15 --retry 5 --retry-delay 30 https://www.0rsk.com
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 30 seconds. 5 retries
Warning: left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 30 seconds. 4 retries
Warning: left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 30 seconds. 3 retries
Warning: left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 30 seconds. 2 retries
Warning: left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 30 seconds. 1 retries
Warning: left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
container 1e5c1f6eed49401839291c78080ed714b5914576757eb8caa9b3b0994ca1bde4 is dead
Fri May 3 07:57:54 CEST 2019
Now they may die and nobody will notice. And they won't restart.