|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hello,
I'm having a weird issue, I wonder if it's related to this open bug.
I have a build done in several steps. There are 3 maven calls, the first package the artifacts, a second to call run a "JUnit-script" that will populate the integration database, and a final third call that will run all tests.
The 2nd call must be run with a particular profile, that I activate via -P. The other two calls should not have this profile active.
But, for a reason that I ignore, the profile remains active during the third maven call.
I tried using a shell script for the second call, in the hope that it would spawn a second JVM and thus not preserve previous configs, but it did not work.
Any suggestions, work-around etc?
Thank you in advance!