Someone needs to fix GLabs CI

[Tony Su]

The continuous integration YAML file throws a critical error and am also unsuccessful cloning a supposedly working repo.

First, based on official documentation, have posted the following in the hexo forums

https://forum.gitlab.com/t/hexo-build-err/17060

Secondly,

I have cloned the following

https://gitlab.com/themes-templates/hexo

Manually running a Pipeline results in the following error

npm info ok 

$ hexo generate

ERROR Local hexo not found in /builds/Putztzu-GL/hexo

ERROR Try running: 'npm install hexo --save'

ERROR: Job failed: exit code 1

Considering that once years ago hexo was able to become endorsed as a supported SSG on Gitlab,

I would think that it'd worth making sure that hexo works, and guides and documentation should be updated as needed.

At the moment,

It looks like hexo has suffered from neglect on Gitlabs.

Am going to next try the generic procedure which is to build locally, then push the contents of the public folder to github or gitlab, but of course this still would not address the problem(s) using Gilab Continuous Integration which would be a nice capability if it can work with hexo.

Thx.

Tony

[Tony Su]

After some thought,

Am thinking that the problem and solution are likely quite simple...

Hexo requires nodejs and npm be installed,

But none of the Hexo shared runners explicitly (tagged) say they support nodejs/npm.

Problem is,

I'm a Gitlab newbie and the documentation is lacking.

Describes how to choose and register Runners, but is completely silent on how to determine a Runner's capabilities beyond any associated tags, and makes no mention how to create a runner with sufficient capability.

So, ideally it would be nice if there was any Users experienced in both Hexo and Gitlabs take the ball and run with ithis.

TIA.