rultor
commented
5 years ago @rultor release, tag is
0.0.1
@yegor256 OK, I will release it now. Please check the progress here
Closed yegor256 closed 5 years ago
rultor
commented
5 years ago @rultor release, tag is
0.0.1
@yegor256 OK, I will release it now. Please check the progress here
rultor
commented
5 years ago @rultor release, tag is
0.0.1
@yegor256 Oops, I failed. You can see the full log here (spent 4min)
11 files inspected, \u001b[32mno offenses\u001b[0m detected
Running xcop...
Inspecting 2 files...
\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m
2 files checked, everything looks \u001b[32mpretty\u001b[0m
grep -q -r '2019' --include '*.rb' --include '*.txt' --include 'Rakefile' .
2019-04-15 15:57:13.496 UTC [23580] LOG: received smart shutdown request
PostgreSQL killed in PID 23580
+ git remote add heroku git@heroku.com:0rsk.git
+ rm -rf /home/r/.ssh
+ mkdir /home/r/.ssh
+ mv ../id_rsa ../id_rsa.pub /home/r/.ssh
+ chmod -R 600 /home/r/.ssh/id_rsa /home/r/.ssh/id_rsa.pub
+ echo -e 'Host *\n StrictHostKeyChecking no\n UserKnownHostsFile=/dev/null'
+ git fetch
2019-04-15 15:57:13.563 UTC [23580] LOG: worker process: logical replication launcher (PID 23587) exited with exit code 1
2019-04-15 15:57:13.563 UTC [23582] LOG: shutting down
2019-04-15 15:57:14.211 UTC [23580] LOG: database system is shut down
Warning: Permanently added 'github.com,192.30.253.113' (RSA) to the list of known hosts.
+ sed -i 's/0\.0\.0/0.0.1/g' ./version.rb
+ git add ./version.rb
+ git commit -m 'build number set'
[__rultor 79a19e8] build number set
1 file changed, 1 insertion(+), 1 deletion(-)
+ cp ../config.yml config.yml
+ LC_ALL=en_US.UTF-8
+ rake config
---
sentry: https://76e220727f7f4d7ebd21a14698e583a3@sentry.io/1437941
github:
client_id: de30e36d127c23b84d2c
client_secret: 31abd01937d9b26ed550d1ee5843329b34db45e9
encryption_secret: 00pUhoLpEqHHgdS65jKppLmeJsRg3Ytr6
pgsql:
host: ec2-54-197-234-117.compute-1.amazonaws.com
dbname: d1ml7e466rish3
user: frhhktcnppxbwt
port: 5432
password: 1936d8add2e4b3cf43ed799582f1475c497d75d3086de7ecfe87b322becc5e8c
url: jdbc:postgresql://ec2-54-197-234-117.compute-1.amazonaws.com:5432/d1ml7e466rish3?user=frhhktcnppxbwt&password=1936d8add2e4b3cf43ed799582f1475c497d75d3086de7ecfe87b322becc5e8c&ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory
+ git add config.yml
+ git commit -m config.yml
[__rultor 981962c] config.yml
1 file changed, 13 insertions(+)
create mode 100644 config.yml
++ git symbolic-ref --short HEAD
+ git push -f heroku __rultor:master
Warning: Permanently added 'heroku.com,50.19.85.154' (RSA) to the list of known hosts.
! No such app as 0rsk.
!
! SSH Key Fingerprint: fd:55:bd:86:ff:23:d9:63:88:29:57:9c:db:f9:c1:42
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
container a527ef7cc75594a6ca21ebb8e3355101e8b5e4f29aa2391a9ae10d9a4c8ce820 is dead
Mon Apr 15 17:57:27 CEST 2019
yegor256
commented
5 years ago @rultor release, tag is 0.0.1
rultor
commented
5 years ago @rultor release, tag is
0.0.1
@yegor256 OK, I will release it now. Please check the progress here
rultor
commented
5 years ago @rultor release, tag is
0.0.1
@yegor256 Oops, I failed. You can see the full log here (spent 11min)
Success. You can now start the database server using:
pg_ctl -D /home/r/repo/target/pgsql -l logfile start
2019-04-15 16:05:52.131 UTC [23694] LOG: listening on IPv4 address "127.0.0.1", port 35061
2019-04-15 16:05:52.131 UTC [23694] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2019-04-15 16:05:52.131 UTC [23694] HINT: Is another postmaster already running on port 35061? If not, wait a few seconds and retry.
2019-04-15 16:05:52.219 UTC [23694] LOG: listening on Unix socket "/home/r/repo/target/pgsql/.s.PGSQL.35061"
2019-04-15 16:05:52.353 UTC [23695] LOG: database system was shut down at 2019-04-15 16:05:51 UTC
2019-04-15 16:05:52.389 UTC [23694] LOG: database system is ready to accept connections
PostgreSQL is running in PID 23694
[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://localhost:35061/test?user=test&password=test
INFO 4/15/19 4:05 PM: liquibase: Successfully acquired change log lock
INFO 4/15/19 4:05 PM: liquibase: Creating database history table with name: databasechangelog
INFO 4/15/19 4:05 PM: liquibase: Reading from databasechangelog
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: Custom SQL executed
INFO 4/15/19 4:05 PM: liquibase: /home/r/repo/liquibase/master.xml: 001-initial-schema.xml::001::yegor256: ChangeSet 001-initial-schema.xml::001::yegor256 ran successfully in 458ms
INFO 4/15/19 4:05 PM: liquibase: Successfully released change log lock
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.802 s
[INFO] Finished at: 2019-04-15T16:05:57+00:00
[INFO] Final Memory: 10M/154M
[INFO] ------------------------------------------------------------------------
2019-04-15 16:05:57.943 UTC [23694] LOG: received smart shutdown request
PostgreSQL killed in PID 23694
+ 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 --:--:-- --:--:-- --:--:-- 02019-04-15 16:05:57.995 UTC [23694] LOG: worker process: logical replication launcher (PID 23701) exited with exit code 1
2019-04-15 16:05:57.995 UTC [23696] LOG: shutting down
Warning: Transient problem: timeout Will retry in 30 seconds. 5 retries left.
2019-04-15 16:05:58.365 UTC [23694] LOG: database system is shut down
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 30 seconds. 4 retries left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 30 seconds. 3 retries left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 30 seconds. 2 retries left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 30 seconds. 1 retries left.
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: www.0rsk.com
container dde8f96ce213f1b6899587d8f1c848f4a8aeccf37ed05c8b36915707acf93ab3 is dead
Mon Apr 15 18:11:56 CEST 2019
@rultor release, tag is
0.0.1