You need to sign in to do that
Don't have an account?
Puzzled
Ant deploy trying to test trigger that doesn't exist
Here's the output I'm getting from an ant deploy statement...
C:\1Salesforce Clients\Apex\eProsper>ant deploy
Buildfile: build.xml
Buildfile: build.xml
deploy:
[sf:compileAndTest] compileAndTest on https://www.salesforce.com/services/Soap/u
/11.0, compiling 1 classes and 1 triggers, deleting 0 classes and 0 triggers
[sf:compileAndTest] compileAndTest on https://www.salesforce.com/services/Soap/u
/11.0, compiling 1 classes and 1 triggers, deleting 0 classes and 0 triggers
BUILD FAILED
C:\1Salesforce Clients\Apex\Client\build.xml:9: Failed:
Code coverage error on SetAStage: Test coverage of selected Apex Trigger is 0%
, at least 1% test coverage is required
Code coverage error: Test coverage of selected Apex Class and Trigger is 36%, at
least 75% test coverage is required
C:\1Salesforce Clients\Apex\Client\build.xml:9: Failed:
Code coverage error on SetAStage: Test coverage of selected Apex Trigger is 0%
, at least 1% test coverage is required
Code coverage error: Test coverage of selected Apex Class and Trigger is 36%, at
least 75% test coverage is required
The issue is that "SetAStage" is the name of a previous trigger I deployed and removed from the classes and triggers directories. I have the correct trigger name in the build.xml and compileAndTest.apex files.
All I have in the directory I'm building from is build.xml and build.properties. Under that are the classes (with only compileAndTest.apex in it) and triggers (with NewTriggerName.tgr) directories.
I've seen this happen when I left a previously deployed trigger in the triggers directory, even though I renamed its extension, so I don't leave previously deployed ones in there anymore. I move them to a totally different directory outside of the current build directory. I even moved the build directory somewhere else, but it still found the name of the old trigger. I looked for the old trigger name in each file and did a Windows search for that string and found nothing.
When I have errors in the trigger or test routine it does give me only the name of the current trigger I'm working on.
I've even rebooted in case it was stuck in memory or something but that didn't fix it. Anyone have any ideas?
Message Edited by jgrenfell on 02-11-2008 10:23 AM
Message Edited by jgrenfell on 02-11-2008 10:23 AM
Thank you so much!
I had the same class name (compileAndTest), didn't know it got stored somewhere in Salesforce. I'd like to know where. I don't recall having to change it in previous multiple trigger deployments that I've done this way.
So I just changed the class name and it deployed.
I have a lot to learn.
Thanks again!