[#CIB-1487] Force attribute is ignored on nested command

Pulse

Force attribute is ignored on nested command

Created: 02/May/08 04:25 AM Updated: 02/May/08 09:11 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

2.0.6, 1.2.52

Description

« Hide

I'm having some trouble with force="true". I thought that specifying force="true" would cause the second command to be run even if the first command fails, but this doesn't seem to be the case. I'm looking at a couple of runs where the first command has failed and the second is not run.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Daniel Ostermeier - 02/May/08 04:26 AM

That is certainly the intention of the force parameter.

There are however a couple of cases it seems then the force is bypassed, in particular when an exception is generated by the preceding command. What does the build log say is the cause of the failure of the first command.

Errors included in this list of exceptions include:

"Could not create command output directory ..."

"Unexpected error: ..."

[ Permlink | « Hide ]

Daniel Ostermeier - 02/May/08 04:27 AM

Are there any exceptions in the server logs at around that time?

The other condition that would cause the second command to be skipped is if the build/recipe is terminated. This can happen if an agent is detected as going offline and then online again (there is a bug that Jason is looking into at the moment where this can occur if the agent configuration is changed), or if the build itself is terminated. I'm assuming that you did not terminate the build, so agent connectivity can be a cause.

[ Permlink | « Hide ]

jason - 02/May/08 08:54 PM

This happens when you set force on a nested command tag:

<command>
<nested force="true"/>
</command>

[ Permlink | « Hide ]

jason - 02/May/08 09:11 PM

Fixed in change 4407, merged to trunk in change 4408.