Hi guys,
first of all: THANK YOU SO MUCH for your support! I really love this forum - it has been such a great inspiration over the last years.
Concerning BUILD-TIME: The main reason for my 4 hour build-time are my chimp-based acceptance tests which are just running ultra-long. If I would start from scratch I’d do it a bit differently, use react to test components via SSR, etc… but at the current state there is NOT really an easy way to reduce build. But also my integrational-tests run for 80 minutes…
CURRENT STATE:
Codeship
I spent some time on this one. The support is really good. My main problem is that I am hitting timeouts here…
Codeship Basic will stop after 4 hours and single calls after 1 hour. It’s a pitty, but it will NOT work for me… this is way I went back to Gitlab…
Gitlab
Yesterday I continued with the self-hosted GitLab option as suggested by @serkandurusoy. I started from scratch with DigitalOceans 1-click install, am using https (via my own domain) and so far things look pretty interesting. It feels pretty awesome to have a tool in my hand, where I have unlimited build-time and ALL options in my own hand. Email-notifications work out of the box, which I find awesome.
I’ll try to get this one to work and if I do I’ll post a mini-tutorial here.
Right now I am hitting a wall - does someone have an idea how I could solve it?
The problem: Calling meteor list --allow-superuser gives a warning about --allow-superuser, then hangs and hence the process is being killed after 1 hour…
The error message is
/bin/bash: line 89: 2363 Killed meteor list --allow-superuser
ERROR: Job failed: execution took longer than 1h0m0s seconds
I am using this docker image https://hub.docker.com/r/blurri/meteor-node/~/dockerfile/
This is my current Gitlab script
# see https://hub.docker.com/r/blurri/meteor-node/~/dockerfile/
image: blurri/meteor-node
variables:
METEOR_ALLOW_SUPERUSER: "true"
METEOR_NO_RELEASE_CHECK: "true"
before_script:
- echo "======================================"
- echo "==== START auto full script v0.1 ====="
- echo "======================================"
cache:
paths:
- "node_modules"
- "~/.npm"
- "~/.meteor"
- "~/meteor"
- ".yarn"
stages:
- test
run_all_tests:
stage: test
script:
- node --version
- meteor --version
- pwd
- ls -al
- sudo sh ./continuous-integration/upgrade_chrome_version.sh
- google-chrome --version
- cd src
- pwd
- curl https://install.meteor.com?release=1.4.4.1 | /bin/sh 2>&1 | cat # NOTE: ALWAYS sync to the version we have on
- meteor --version --allow-superuser
- meteor list --allow-superuser # HANGS RIGHT HERE… TIMEOUT AFTER 1 hour
# ...
THE LOGS LOOK LIKE:
$ node --version
v6.11.3
$ meteor --version
Even with METEOR_ALLOW_SUPERUSER or --allow-superuser, permissions in your app
directory will be incorrect if you ever attempt to perform any Meteor tasks as
a normal user. If you need to fix your permissions, run the following command
from the root of your project:
sudo chown -Rh <username> .meteor/local
Meteor 1.5.2
$ pwd
...
$ google-chrome --version
Google Chrome 69.0.3497.92
$ cd src
$ pwd
/builds/thebarty/theproject/src
$ curl https://install.meteor.com?release=1.4.4.1 | /bin/sh 2>&1 | cat
% 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
100 7786 0 7786 0 0 14155 0 --:--:-- --:--:-- --:--:-- 14156
Removing your existing Meteor installation.
Downloading Meteor distribution
Meteor 1.4.4.1 has been installed in your home directory (~/.meteor).
Writing a launcher script to /usr/local/bin/meteor for your convenience.
To get started fast:
$ meteor create ~/my_cool_app
$ cd ~/my_cool_app
$ meteor
Or see the docs at:
docs.meteor.com
$ meteor --version --allow-superuser
Even with METEOR_ALLOW_SUPERUSER or --allow-superuser, permissions in your app
directory will be incorrect if you ever attempt to perform any Meteor tasks as
a normal user. If you need to fix your permissions, run the following command
from the root of your project:
sudo chown -Rh <username> .meteor/local
Meteor 1.4.4.1
$ meteor list --allow-superuser
Even with METEOR_ALLOW_SUPERUSER or --allow-superuser, permissions in your app
directory will be incorrect if you ever attempt to perform any Meteor tasks as
a normal user. If you need to fix your permissions, run the following command
from the root of your project:
sudo chown -Rh <username> .meteor/local
/bin/bash: line 89: 2363 Killed meteor list --allow-superuser
Pulling docker image gitlab/gitlab-runner-helper:x86_64-35e8515d ...
ERROR: Job failed: execution took longer than 1h0m0s seconds
@arturs @rohanray @idmontie @macrozone you’ve been there before. Can you help out and post your current working Gitlab configuration?
@idmontie: is this your current Gitlab setup working? https://gitlab.com/memosa/meteor-gitlab-ci? Any tips?
