I'm using a custom runner, but it seems like the Gitlab.com CI coordinator
isn't sending some jobs down. It runs the "build" stage, but doesn't move
on to the "test" stage.
http://screencast.com/t/BZJg6PnmMF
http://screencast.com/t/gIiCq11zfX
It seems to be starting the jobs, but it takes a re
It definitely gives notifications for the status of a build through the CI
system, but I haven't seen any other notifications. Do you use GitLab CI?
If so, try leaving the MR browser tab open while the build is running and
you should get notifications when it succeeds or fails.
On Mon, Nov 7, 2016
Hey all,
I'm trying out Review Apps and I'm having a problem. I'm trying to spin up
a new Heroku app for each Review App, but the problem is that my branch
name in $CI_BUILD_REF_NAME contains characters that Heroku doesn't support.
I can create the Heroku app just fine by running the name throu
Hi Ashwini,
You can totally do that! Go to the "Edit Project" settings and scroll down
to the Merge Requests section. Check the checkbox that says "Only allow
merge requests to be merged if all discussions are resolved".
Here's a screenshot: http://screencast.com/t/ol65L6nNhYKo
Enjoy! 😄
Alex
On
Yes there is a typo. My bad! But that isn't the problem. Even with the
correct sed syntax, the command isn't being run 😔
On Mon, Dec 26, 2016 at 15:30 Michael Cox wrote:
> environment:
> url: https://$(echo $CI_BUILD_REF_NAME | sed 's/_/-').herokuapp.com
>
> Typo? The sed regex should be
> 's/_