gopidesupavan commented on code in PR #45324:
URL: https://github.com/apache/airflow/pull/45324#discussion_r1900375928


##########
dev/breeze/doc/ci/07_running_ci_locally.md:
##########
@@ -79,83 +79,109 @@ To load the image from specific PR, you can use the 
following command:
 breeze ci-image load --from-pr 12345 --python 3.9 --github-token 
<your_github_token>
 ```
 
-To load the image from specific job run (for example 12538475388),
+To load the image from specific run (for example 12538475388),
 you can use the following command, find the run id from github action runs.
 
 ```bash
-breeze ci-image load --from-job 12538475388 --python 3.9 --github-token 
<your_github_token>
+breeze ci-image load --from-run 12538475388 --python 3.9 --github-token 
<your_github_token>
 ```
 
 After you load the image, you can reproduce the very exact environment that 
was used in the CI run by
 entering breeze container without mounting your local sources:
 
 ```bash
-breeze shell --mount-sources skip [OTHER OPTIONS]
+breeze shell --mount-sources skip [OPTIONS]
 ```
 
 And you should be able to run any tests and commands interactively in the very 
exact environment that
 was used in the failing CI run even without checking out sources of the 
failing PR.
 This is a powerful tool to debug and fix CI issues.
 
+You can also build the image locally by checking-out the branch of the PR that 
was used and running:
+
+```bash
+breeze ci-image build
+```
+
+You have to be aware that some of the PRs and canary builds use the 
`--upgrade-to-newer-dependencies` flag
+(`UPGRADE_TO_NEWER_DEPENDENCIES` environment variable set to `true`) and they 
are not using constraints
+to build the image so if you want to build it locally, you should pass the 
`--upgrade-to-newer-dependencies`
+flaag when you are building the image.

Review Comment:
   ```suggestion
   flag when you are building the image.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to