Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No indication of failure until the end of deploy logs #3104

Open
andrewgoodmansabio opened this issue Nov 11, 2024 · 4 comments
Open

No indication of failure until the end of deploy logs #3104

andrewgoodmansabio opened this issue Nov 11, 2024 · 4 comments
Labels
bug Issue or pull request that identifies or fixes a bug

Comments

@andrewgoodmansabio
Copy link

Following on from Changes to deploy output? #3079, I see that the new console output is back in the latest build.

The logging is improved from the previous iteration but no longer shows any indication of an error until the build has finished.

Before example:
Screenshot 2024-11-11 at 16 36 58

After example:
Screenshot 2024-11-11 at 16 38 33

The previous logging wasn't great, it didn't say what the error was but we'd know the build had failed. The newer version doesn't even give us this information.

In earlier builds of SFDX, you'd get the whole component/test failure output as soon as it happened - it wasn't necessarily pretty but it was functional and gave us the information.

This is important. Salesforce builds can run for ages, with some clients hours - developers need to know about these failures as soon as they happen so that they can be working on fixes whilst the rest of the build completes.

Note, developers don't necessarily have access to the orgs where validations are running - the only thing they have to go on is the logs.

@andrewgoodmansabio andrewgoodmansabio added the investigating We're actively investigating this issue label Nov 11, 2024
Copy link

Hello @andrewgoodmansabio 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

  • Make sure you've provided detailed steps to reproduce your issue.
    • A repository that clearly demonstrates the bug is ideal.
  • Make sure you've installed the latest version of Salesforce CLI. (docs)
    • Better yet, try the rc or nightly versions. (docs)
  • Try running the doctor command to diagnose common issues.
  • Search GitHub for existing related issues.

Thank you!

@github-actions github-actions bot added more information required Issue requires more information or a response from the customer and removed investigating We're actively investigating this issue labels Nov 11, 2024
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@cristiand391 cristiand391 added bug Issue or pull request that identifies or fixes a bug and removed more information required Issue requires more information or a response from the customer labels Nov 11, 2024
Copy link

git2gus bot commented Nov 11, 2024

This issue has been linked to a new work item: W-17203886

@cristiand391
Copy link
Member

@andrewgoodmansabio thanks for the heads up, we got a PR to add a completed/failed counter here:
salesforcecli/plugin-deploy-retrieve#1215

In earlier builds of SFDX, you'd get the whole component/test failure output as soon as it happened - it wasn't necessarily pretty but it was functional and gave us the information.

agree, asked my team about ways we can render failures as soon as they appear while polling for the deploy status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug
Projects
None yet
Development

No branches or pull requests

2 participants