Hey everyone is anyone u…

Hey everyone is anyone using NX on GitlabCI, could you share your NX+GilabCI workflow?

Responses:

Hello

Following as I’m interested in this too :slightly_smiling_face:

I do use NX with Gitlab CI but haven’t had time to optimize the pipelines yet.

There’s an interesting related issue on Github: https://github.com/nrwl/nx/issues/633

At the moment, the gitlab pipeline config I’m using looks like this: https://gist.github.com/dsebastien/aff0276b2e9e04fb801e5e109b6aa184

I’m not really satisfied (still tons of things to do), but for now it’s enough for our needs (not in production yet)

Note that for Gitlab, there’s a huge pain point around how to install node modules efficiently. The built-in mechanism is slow as hell. They know about it but it ain’t fixed yet

I’ve blogged about it a while ago and described my current solution, which works rather well: https://itnext.io/speeding-up-your-ci-cd-build-times-with-a-custom-docker-image-3bfaac4e0479

Interesting, I will check this out today in details and maybe we can improve on this together, there is not a lot of NX docs on CI/CD unfortunately, which is an integral part of a good maintained monorepo

So I tried it today, and my workflow was: after a merge request was accepted during the ci on taget branch (master) compare the master to the source branch of the MR and build the difference, but I can’t get the information about the MR source branch after the MR was accepted