-
Notifications
You must be signed in to change notification settings - Fork 238
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
Trouble deploying trigger #7
Comments
Sorry for not getting back to you sooner, the notification for this issue slipped through the net! I'll have a look and see if I can reproduce this, my initial thought is this is one of those special 'Standard' objects that don't quite work as we expect.... |
I've managed to reproduce this, sorry for the long wait...looking at it now... |
Ok, the root issue was that it was not reporting test failures. Because the generated test has a try/catch in it, it will not cause failures, and will serve its purpose to obtain code coverage (since validation rules are invoked after the before phase of a trigger). So the remaining cause for deploy failure will be if other tests (excluded those from packages) are presently failing (which will likely explain why it failed in some orgs and not others for you). It will now display these messages correctly, you can upgrade to v1.5 (see the link on the readme). Thanks for your patience, the trust is I'd been thinking this was a harder fix than it turned out to be! :) |
I'm getting a funny message when I try to deploy the trigger for CampaignMember (see yellow messages section of screenshot). Messages indicate that the deployment has completed, but instead of confirmation that the trigger and class were created, I get another message telling me to click Deploy. The class and trigger are not created. I've deployed other triggers successfully in this org and have also successfully deployed the CampaignMember trigger in other orgs. Any thoughts?
The text was updated successfully, but these errors were encountered: