pages:deploy now fails without showing an error log - something changed May 7/2017?
Summary
I had a stable static site being generated using a simple pipeline. After making a small template change to a static file, the pipeline has suddenly stopped on the deploy:pages stage - however there is no indication why? My deploy stage is passing and showing a "job succeeded" message, however deploy:pages just shows failed.
Steps to reproduce
Rerun the deploy stage, or checkin a small change to cause the pipeline to re-run.
What is the current bug behavior?
Pages:deploy shows a red X next to its stage (you can't click to see why - there is an issue logged for this from a year ago)
What is the expected correct behavior?
Deploy:pages should succeed, there is a public folder with html assets in it, and it was working May 6th, with more or less the same assets
Relevant logs and/or screenshots
Gitlab doesn't produce any - my build stage shows:
Running with gitlab-ci-multi-runner 9.1.0 (0118d89)
on docker-auto-scale (4e4528ca)
Using Docker executor with image node:7.5.0 ...
Using docker image sha256:63b370559b078fa0439b501b9c807ba5021ab378c99c8116b3263acd5b61174f for predefined container...
Pulling docker image node:7.5.0 ...
Using docker image node:7.5.0 ID=sha256:14b3438205508915bb4daa2162fd2b36af5c385a28d5eedb89ac22cf19479ef2 for build container...
Running on runner-4e4528ca-project-3012138-concurrent-0 via runner-4e4528ca-machine-1494312338-1846385e-digital-ocean-2gb...
Cloning repository...
Cloning into '/builds/macta/website-mtt'...
Checking out 654b76a0 as master...
Skipping Git submodules setup
Checking cache for default...
Successfully extracted cache
$ echo Gitlab build started $(date)
Gitlab build started Tue May 9 06:47:59 UTC 2017
$ npm install --production
npm info it worked if it ends with ok
npm info using npm@4.1.2
npm info using node@v7.5.0
npm info attempt registry request try #1 at 6:48:00 AM
npm http request GET https://registry.npmjs.org/bootstrap
npm info attempt registry request try #1 at 6:48:00 AM
npm http request GET https://registry.npmjs.org/circular-json
npm info attempt registry request try #1 at 6:48:00 AM
npm http request GET https://registry.npmjs.org/handlebars
npm info attempt registry request try #1 at 6:48:00 AM
.... lots of npm load stufff ...
`-- metalsmith-validate@0.1.4
+-- minimatch@0.3.0
| +-- lru-cache@2.7.3
| `-- sigmund@1.0.1
`-- type-check@0.3.2
`-- prelude-ls@1.1.2
npm info ok
$ node build.js --deploy
Build complete @ Tue May 09 2017 06:48:49 GMT+0000 (UTC)
Completed production build.
$ echo $0
/bin/bash
$ pwd
/builds/macta/website-mtt
$ ls -pAl --group-directories-first ./public
total 80
drwxr-xr-x. 6 root root 4096 May 9 06:48 assets/
drwxr-xr-x. 4 root root 4096 May 9 06:48 blog/
drwxr-xr-x. 7 root root 4096 May 9 06:48 pages/
drwxr-xr-x. 4 root root 4096 May 9 06:48 posts/
-rw-rw-rw-. 1 root root 9976 May 9 06:48 404.html
-rw-rw-rw-. 1 root root 25415 May 9 06:48 index.html
Creating cache default...
Created cache
Uploading artifacts...
public: found 291 matching files
Uploading artifacts to coordinator... ok id=15871256 responseStatus=201 Created token=Wvze8rGz
Job succeededOutput of checks
This bug happens on GitLab.com