Ensure that a single command failure logs the error (file or stderr) without stopping the execution of subsequent CLI commands.

[Genaker]

magento2/app/code/Magento/Deploy/Console/CommandList.php

Lines 48 to 54 in 597e991

	foreach ($this->getCommandsClasses() as $class) {
	if (class_exists($class)) {
	$commands[] = $this->objectManager->get($class);
	} else {
	throw new \Exception('Class ' . $class . ' does not exist');
	}
	}

[m2-assistant]

Hi @Genaker. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @Genaker ,

Thank you for your report and collaboration.

To help us investigate and reproduce the issue effectively, could you please provide the following details:

• Description of the issue
• Steps to reproduce
• Expected result
• Actual result
• Screen recording or screenshots (if possible)

This information will greatly assist us in identifying and resolving the problem more efficiently.

Hence marking this issue as "Issue: Needs Update"

Thank you again for your support!