Gitlab pages CI pipeline stuck forever

[papanito]

Maybe not related at all to the them, still as I am fishing maybe somebody here can help. I build my page since forever with Gitlab and using Gitlab pages. Recently the build stucks always at the same place

Related discussion in Gitlab Forum is here: https://forum.gitlab.com/t/gitlab-ci-times-out-building-hugo-site/133033

[h-enk]

I updated the Doks GitLab Pages example project for the latest Doks (v1.9.1) using the .gitlab-ci.yml recommended by Hugo – see also: Host on GitLab Pages

And, that deploys nicely: https://doks-gitlab-pages-h-enk-7f8afcd083c32d5a189605c5aab5a86eda737b2.gitlab.io/

[papanito]

I updated the Doks GitLab Pages example project for the latest Doks (v1.9.1) using the .gitlab-ci.yml recommended by Hugo – see also: Host on GitLab Pages

yeah I saw that, switched my workflow to it about 1-2 months back when I switched to 1.8. However it's where the issue started.

[h-enk]

I updated it like in this morning. Did you notice the updated workflow: https://gitlab.com/h-enk/doks-gitlab-pages/-/blob/main/.gitlab-ci.yml?ref_type=heads

[papanito]

no the latest changes I did not see. I adjusted the flow according to https://gitlab.com/gitlab-com/content-sites/handbook/-/blob/main/.gitlab-ci.yml?ref_type=heads so it runs in the branch as well.

However it seems, it is the Hugo binary call that stalls/hands forever, so not sure if its related to the workflow.

[h-enk]

Check your repository against the Doks main branch (or the Doks v1.8 and Doks v1.9 upgrade guides) to see any significant differences that could cause your issue (using for example GitHub Copilot)

[papanito]

I followed the update guide, but what seemed also to help is copy postcss.config.js

[h-enk]

Since you process a significant number of images, make sure to check the resources directory into source control – see also Performance

[papanito]

Thanks, that helps to improve build speed. Still the issue above persists as soon as I run the build process in a docker image

docker run -it --rm -v $(pwd):/src -w /src hugomods/hugo:exts  /bin/sh -c "hugo --destination /tmp/pub
lic --logLevel debug  "

[papanito]

Found the culprit after let the build run in docker fro 25h. I referenced an external image which

DEBUG Fetched remote resource: https://upload.wikimedia.org/wikipedia/commons/thumb/5/51/Overview_of_a_three-tier_application_vectorVersion.svg/512px-Overview_of_a_three-tier_application_vectorVersion.svg.png
ERROR template: _partials/picture.html:256:27: executing "partials/inline/capture-resource.html" at <resources.GetRemote>: error calling GetRemote: Get "https://upload.wikimedia.org/wikipedia/commons/thumb/5/51/Overview_of_a_three-tier_application_vectorVersion.svg/512px-Overview_of_a_three-tier_application_vectorVersion.svg.png": retry timeout (configured to 25h0m0s) fetching remote resource: 429 Too Many Requests. See blog/2021-05-what-is-a-service-mesh/index.md

Don’t ask me why I did that, but certainly not the best idea. Nevertheless, thanks for your help, appreciate it - as always!

[papanito]

However now there is another issue

INFO  postcss: use config file "/builds/wyssmann/website/config/postcss.config.js"
INFO  exec: resolve "postcss" using node_modules/.bin
INFO  postcss: Error: Cannot find module 'purgecss-whitelister'
Require stack:
- /builds/wyssmann/website/config/postcss.config.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1420:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1058:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1063:22)
    at Module._load (node:internal/modules/cjs/loader:1226:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)
    at Module.require (node:internal/modules/cjs/loader:1503:12)
    at require (node:internal/modules/helpers:152:16)
    at Object.<anonymous> (/builds/wyssmann/website/config/postcss.config.js:3:21)
    at Module._compile (node:internal/modules/cjs/loader:1760:14) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/builds/wyssmann/website/config/postcss.config.js' ]
}
INFO  build:  step postProcess duration 1.402392885s
INFO  build:  duration 4.255680498s
Total in 4339 ms
Error: error building site: POSTCSS: failed to transform "main.css" (text/css): Error: Cannot find module 'purgecss-whitelister'
Require stack:
- /builds/wyssmann/website/config/postcss.config.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1420:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1058:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1063:22)
    at Module._load (node:internal/modules/cjs/loader:1226:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)
    at Module.require (node:internal/modules/cjs/loader:1503:12)
    at require (node:internal/modules/helpers:152:16)
    at Object.<anonymous> (/builds/wyssmann/website/config/postcss.config.js:3:21)
    at Module._compile (node:internal/modules/cjs/loader:1760:14) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/builds/wyssmann/website/config/postcss.config.js' ]
}

[papanito]

I followed the update guide, but what seemed also to help is copy postcss.config.js

[h-enk]

Yes, I can imagine. So, no more issues now?