Build Configuration Elements - Order of Execution
I have created a new pre-build configuration element to perform some verification tasks before a build is executed. My question is, is the order of pre-build task execution consistent? From my experimentation they always get executed in the order they are defined in my plugin.xml.
Can I safely assume this will always be the case?
Thanks,
-Dave
<buildDefinitionTemplate>
<buildConfigurationElement>
</buildConfigurationElement>
<buildConfigurationElement>
</buildConfigurationElement>
<buildConfigurationElement>
</buildConfigurationElement>
<buildConfigurationElement>
</buildConfigurationElement>
<availableBuildConfigurationElement>
</availableBuildConfigurationElement>
<availableBuildConfigurationElement>
</availableBuildConfigurationElement>
</buildDefinitionTemplate>
Can I safely assume this will always be the case?
Thanks,
-Dave
2 answers
The order of phases is: PRE_BUILD, BUILD, POST_BUILD. Within each phase, the participants corresponding to the configurations are executed in order. Note that users may customize the order (for a given phase), either in the build definition wizard when creating the definition, or afterwards by choosing Edit Configuration in the context menu in the header of the build definition editor.
The order of phases is: PRE_BUILD, BUILD, POST_BUILD. Within each phase, the participants corresponding to the configurations are executed in order. Note that users may customize the order (for a given phase), either in the build definition wizard when creating the definition, or afterwards by choosing Edit Configuration in the context menu in the header of the build definition editor.
Thanks,
That makes sense. I missed that you could set the order while creating the definition with the 'Move Up' and 'Move Down' buttons.
-Dave