-
Notifications
You must be signed in to change notification settings - Fork 100
Validate Against Org flag to rerun validation even if no changes are detected #680
Comments
@rrgripp Can you explain the scenario further? If a particular package in a collection of packages fail, and some of them got deployed, we will redo the remaining if you retrigger. Is there something where you went ahead discarding the output of validateAgainstOrg and went to publish? |
Since we already have some source code in the happy soup, sometimes the test fails because of these files. But when I rerun the test, as there was no changes on the package source code, the test is not executed |
In that case, it is better to remove --diffcheck option. Will that help? |
That would be in which command?
|
In the case of validate command, remove sfpowerscripts artifact installed in the org. We will be introducing an environment variable for this shortly |
Hi @azlam-abdulsalam, thanks for the reply! Yeah, I've been doing that to workaround the issue, but on the long run, it's not the ideal solution. Looking forward to this new release and what you guys have prepared for us 🙏 ! Still regarding the matter of Anyway, thanks for all the support! |
Closing this as there is an analysis triggered on #800 |
Sometimes our Gitlab pipeline fails to complete during the sandbox validation job for various reasons (timeouts for instance), and when we try to rerun the job, we get the message
validate will only execute if there is a change in atleast one of the packages
.It would be interesting to have a flag that allows us to rerun the
sfdx sfpowerscripts:orchestrator:validateAgainstOrg
command, even if no changes were detected in the packages.The text was updated successfully, but these errors were encountered: