Replies: 3 comments 3 replies
-
@firecow you've answered me:
That's what I've tried, but I'm really a noob with Node.js, and I couldn't find a simple way of importing / requiring Could you suggest me a minimal Node project that imports 🙏 |
Beta Was this translation helpful? Give feedback.
-
Here it is: https://gitlab.com/to-be-continuous/tools/gitlab-ci-test Publishing to npm and dockerhub is still pending but it works |
Beta Was this translation helpful? Give feedback.
-
Hey, @pismy I've been out skiing for a while, so haven't had time to peak in. |
Beta Was this translation helpful? Give feedback.
-
Context of the request
I am the original creator and maintainer of to-be-continuous, a set of 50+ ready-to-use, configurable, modular and composable CI/CD templates for GitLab.
One of the difficulties with that project is the (un)ability to implement an automated test harness.
Indeed, testing CI/CD templates requires to use all the features of the template, with all possible configurations, and verify it behaves as expected (jobs are successful, produce the expected artifacts and reports, ...)
An initial Proof-of-Concept has been implemented in to-be-continuous that demonstrates
gitlab-ci-local
can be used to mock specific template configuration and execution.What I need
In the initial Proof-of-Concept,
gitlab-ci-local
is executed as an external program, the pipeline execution outcomes can be captured as a whole (stdout) or from the filesystem (generated artifacts).What I would like instead:
gitlab-ci-local
as a Node librarygitlab-ci-local
directly with Node classesgitlab-ci-local
execution outputs (generated artifacts, pipeline and jobs execution status, stdout, stderr...) with programmatic structures (interfaces, objects, maps, ...) in order to be able to implement my test assertions properly.Maybe what I'm asking is already (partially) possible, but I'm far from being a Node expert 😅
Beta Was this translation helpful? Give feedback.
All reactions