You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the jobs in github actions build workflow is split into parallel jobs by using a mechanism based on the "Nx" library. Unfortunately, changes in the "Nx" library broke this mechanism at now it is not possible to update the dependency without breaking the pipeline.
The method used to split the workflows is very similar to the one described here. Basically, it executes a Nx bash command under the hood and gets the output to be able to determine the affected packages and the corresponding tasks to generate a matrix of Github actions jobs dynamically. The problem seems to be related to latest versions of Nx are stopping the process somehow before ending to print all outputs to the stdout.
In order to avoid having to investigate too much about this problem, or fix it with another "hack" that may be broken again in the future, it would be desirable to simply create different jobs for each Node version to test, and, inside each one, run in series the needed tasks by using "Nx" affected commands, for example:
nx affected -t link
nx affected -t test
Or even to define a "build:ci" task on each package which should have a dependency with all tasks to be executed in that package to be considered a valid build, and simply run:
nx affected -t build:ci
The text was updated successfully, but these errors were encountered:
Currently, the jobs in github actions build workflow is split into parallel jobs by using a mechanism based on the "Nx" library. Unfortunately, changes in the "Nx" library broke this mechanism at now it is not possible to update the dependency without breaking the pipeline.
The method used to split the workflows is very similar to the one described here. Basically, it executes a Nx bash command under the hood and gets the output to be able to determine the affected packages and the corresponding tasks to generate a matrix of Github actions jobs dynamically. The problem seems to be related to latest versions of Nx are stopping the process somehow before ending to print all outputs to the stdout.
In order to avoid having to investigate too much about this problem, or fix it with another "hack" that may be broken again in the future, it would be desirable to simply create different jobs for each Node version to test, and, inside each one, run in series the needed tasks by using "Nx" affected commands, for example:
nx affected -t link nx affected -t test
Or even to define a "build:ci" task on each package which should have a dependency with all tasks to be executed in that package to be considered a valid build, and simply run:
The text was updated successfully, but these errors were encountered: