.circleci/config.yml

@@ -114,8 +114,7 @@ jobs:
             pnpm nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte &
             pids+=($!)
 
-            (pnpm nx affected --targets=lint,test,build --base=$NX_BASE --head=$NX_HEAD --parallel=3 &&
-            pnpm nx affected --targets=e2e,e2e-ci --base=$NX_BASE --head=$NX_HEAD --parallel=1) &
+            pnpm nx affected --targets=lint,test,build,e2e,e2e-ci --base=$NX_BASE --head=$NX_HEAD --parallel=3 &
             pids+=($!)
 
             for pid in "${pids[@]}"; do

docs/blog/2024-03-21-reliable-ci.md

@@ -103,7 +103,7 @@ Nx Cloud introduces an entirely different model. Instead of the graph of VMs, th
 By adding the following line…
 
 ```shell
-npx nx-cloud start-ci-run --distribute-on="5 linux-medium-js"
+npx nx-cloud start-ci-run --distribute-on="3 linux-medium-js"
 ```
 
 ... you are telling Nx Cloud to create five Nx Agents to execute all the tasks from all the commands that will follow.

docs/generated/packages/cypress/documents/overview.md

@@ -56,9 +56,7 @@ The `@nx/cypress` plugin will create a task for any project that has a Cypress c
 - `cypress.config.js`
 - `cypress.config.ts`
 - `cypress.config.mjs`
-- `cypress.config.mts`
 - `cypress.config.cjs`
-- `cypress.config.cts`
 
 ### View Inferred Tasks
 

docs/generated/packages/nest/documents/overview.md

@@ -150,6 +150,26 @@ You can lint a library with the following command:
 nx lint my-nest-lib
 ```
 
+## Deployment
+
+Ensuring a smooth and reliable deployment of a Nest.js application in a production environment requires careful planning and the right strategy. Depending on your specific needs and infrastructure, you can choose from several deployment approaches. Below are four commonly used methods:
+
+1. **Using Docker:**
+   Create a Dockerfile that specifies the application's environment and dependencies. Build a Docker image and optionally push it to a container registry. Deploy and run the Docker container on the server. Utilize the `@nx/node:setup-docker` generator to streamline the Docker setup process.
+
+2. **Installing Dependencies on the Server:**
+   Transfer the build artifacts to the server, install all dependencies using the package manager of your choice, and start the application. Ensure that [NxWebpackPlugin](/recipes/webpack/webpack-plugins#nxwebpackplugin) is configured with `generatePackageJson: true` so that the build artifacts directory includes `package.json` and `package-lock.json` (or the equivalent files for other package managers).
+
+3. **Transferring Pre-installed Dependencies:**
+   Install dependencies during the build process, and transfer the build artifacts along with the `node_modules` directory to the server. Typically, the artifacts are archived for faster transfer and then unarchived on the server.
+
+4. **Bundling Dependencies:**
+   By default, Nx/Nest creates a setup that externalizes all dependencies, meaning they are not included in the bundle. This behavior can be adjusted using the `externalDependencies` parameter in the webpack configuration with [NxWebpackPlugin](/recipes/webpack/webpack-plugins#nxwebpackplugin). After bundling, transfer the package to the server and start the application.
+
+{% callout type="note" title="Bundling Dependencies" %}
+Bundling dependencies is typically not recommended for Node applications.
+{% /callout %}
+
 ### Unit Test
 
 You can run unit test for an application with the following command:

docs/nx-cloud/reference/nx-cloud-cli.md

@@ -21,7 +21,7 @@ Tells Nx Cloud how many agents to use (and what launch templates to use) to dist
 using the `linux-medium-js` launch template.
 
 You can use different types of launch templates as follows:
-`npx nx-cloud start-ci-run --distribute-on="5 linux-medium-js, 3 linux-large-js"`.
+`npx nx-cloud start-ci-run --distribute-on="3 linux-medium-js, 3 linux-large-js"`.
 
 You can also define the configuration in a file and reference it as follows:
 `npx nx-cloud start-ci-run --distribute-on=".nx/workflows/dynamic-changesets.yaml"`.

docs/nx-cloud/reference/release-notes.md

@@ -1,5 +1,35 @@
 # Enterprise Release Notes
 
+### 2406.29.1
+
+##### Full terminal outputs in the web app
+
+Due to storage constraints in Mongo, long terminal outputs were sometimes truncated when viewed in the UI. With this update we are now loading all terminal outputs directly
+from the storage bucket, removing the need to keep them in Mongo. You should now be able to view full, complete logs in the UI regardless of how large the output is.
+
+##### OpenShift fixes for Agents
+
+- the latest messagequeue image is now OpenShift ready
+  - to use, just update to the latest Helm version `0.15.6` and make sure you are not passing in an explicit tag for the messagequeue
+  - then use version `2406.29.1` for NxCloud. This should use the latest, OpenShift enabled messagequeue image
+- when running Agents on OpenShift, they run as a specific user with ID 1000
+  - to override this, make sure to set `NX_CLOUD_RUN_UNIX_PODS_AS_USER: <userId>` and `NX_CLOUD_RUN_UNIX_PODS_AS_GROUP: <groupId>` on the [workflow controller env vars](https://github.com/nrwl/nx-cloud-helm/blob/main/charts/nx-agents/values.yaml#L63)
+
+##### Full Bitbucket Data Center (on-prem)
+
+We now have full support for BitBucket Data Center (self-hosted):
+
+- VCS integration for posting comments with live updates about your CI runs
+- full agents integration
+- more info about each one of your commits on the NxCloud web app
+- you can even [set-up auth with BitBucket Data Center](/ci/recipes/enterprise/on-premise/auth-bitbucket-data-center#bitbucket-data-center-auth)
+
+##### Misc
+
+- easier workspace setup experience for new customers
+- the CIPE visualisation has been updated (elapsed task time)
+- general web app performance improvements
+
 ### 2405.02.15
 
 ##### Easy membership management via GitHub