- Explore the NxCloud Run-Detail pages
- Configure the NxCloud bot to get easy to read reports on the Nx checks performed during CI
-
Enable the NxCloud GitHub bot on your GitHub repository: https://github.com/apps/nx-cloud
-
Switch to a new branch:
git checkout -b nxcloud-bot
-
Make a change (add a
console.log
) in the store:apps/store/src/app/app.component.ts
(so that it will trigger our affected commands in CI):export class AppComponent { constructor(private http: HttpClient) { console.log("component constructed") <-- add console log }
-
Commit everything and push your branch
-
Make a PR on GitHub
-
Once the checks finish you should see something similar to this:
If your install is failing with
@storybook/angular
add following to the rootpackage.json
:"overrides": { "@storybook/angular": { "zone.js": "0.12.0" } }
-
Click on one of the "failed" commands (if any). On the "Run Details" page, click on one of the projects and inspect the terminal output:
🔥 Rather than reading through CI logs, you can use this view to filter to the failed projects and inspect the failure reason scoped to that project.
-
Have a look at the "Cache Hit" and "Cache Miss" filters. What do you think they do?
-
Finally, you should see a "Claim workspace" button at the top - it's a good idea to do that at this stage. We'll explain more about that in a bit!
-
Merge your PR into
main
and pull latest locally:git checkout main git pull
-
BONUS: Have a look at some of the docs for setting up NxCloud on CI to see how the set-up might apply to your CI provider.
-
BONUS: Read this blog post on "Distributed Task Execution". We'll briefly talk about this after the lab.