Andrushika commented on code in PR #73836:
URL: https://github.com/apache/airflow/pull/73836#discussion_r4125327138


##########
dev/breeze/doc/05_test_commands.rst:
##########
@@ -108,6 +108,20 @@ For example this will run API and WWW tests in parallel:
 
     breeze testing core-tests --parallel-test-types "API WWW" --run-in-parallel
 
+When testing separate worktrees concurrently, give each invocation a different
+``--project-name``. This isolates its containers, networks, and database 
volumes.
+The option also applies to ``breeze testing providers-tests``.
+
+.. code-block:: bash
+
+    breeze testing core-tests --project-name breeze-history --backend postgres
+    breeze testing core-tests --project-name breeze-clearing --backend postgres
+
+If you use this mode you will have to clean up old projects manually: 
+
+.. code-block:: bash
+    breeze down --project-name breeze-history

Review Comment:
   Yes I mean the project name literally. (Docker Compose project name)
   `breeze testing` is different from `breeze shell` here: shell passes 
`--project-name` to compose as-is, but testing builds 
`<value>-airflow-test-<test-type>` first:
   
   
https://github.com/apache/airflow/blob/87c0d38164060743f4d9b98a130868fbd21c37db/dev/breeze/src/airflow_breeze/commands/testing_commands.py#L323-L330
   
   
https://github.com/apache/airflow/blob/87c0d38164060743f4d9b98a130868fbd21c37db/dev/breeze/src/airflow_breeze/commands/testing_commands.py#L228-L238



-- 
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