OK, I think we have two options:
- When building on CI we disable the maven-invoker-plugin invocation through the skipInvocation param - no integrations tests at all
- When building on CI we only run the embedded jetty test (by having a different invokerPropertiesFile)
The first option is easier and cleaner. However, the second option adds a basic level of verification on the CI (which is the purpose of CI).
Today I would suggest the second option. However, if we make the invoker-plugin configuration grow it could possibly cause issues/confusion. But that's a future problem i think.
What we do is that when create a profile (id: bamboo-id or similar), which reconfigures the invoker-plugin (either the skipInvocation or the invokerPropertiesFile param). This profile is only triggered on CI, so when building locally (snapshot build, release build, or whatever) the invoker-plugin is doing a full execution.
The question is how we trigger this extra profile on the Bamboo instance. One way is to specifically specify the profile (for example "mvn clean install -Pbamboo-ci"). One other way is if there's a property (already set) on the CI instance that we can use to trigger the profile. Ali, what do you think?