[
https://issues.apache.org/jira/browse/MBUILDCACHE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Herscu updated MBUILDCACHE-72:
-------------------------------------
Description:
For system test automation we use the Failsafe Plugin.
In a very small automation project it takes about 20 seconds from launching
Maven until the tests actually begin.
If the cache is configured, such as that Failsafe always runs, then after
cleaning, it fails because no classes are in target directory.
If Failsafe is not configured to always run, then no testing is done unless
something is changed in the sources.
It appears that in both cases, it makes no sense for using the build cache,
although it could speed execution by preventing what it was meant to prevent
It would be great to have more details if the build cache can be used for such
scenario, and cut down the start time.
was:
For system test automation we use the Failsafe Plugin.
If the cache is configured, such as that Failsafe always runs, then after
cleaning, it fails because no classes are in target directory.
If Failsafe is not configured to always run, then no testing is done unless
something is changed in the sources.
It appears that in both cases, it makes no sense for using the build cache,
although it could speed execution by preventing what it was meant to prevent
It would be great to have more details if the build cache can be used for such
scenario.
> instructions for running failsafe plugin
> ----------------------------------------
>
> Key: MBUILDCACHE-72
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-72
> Project: Maven Build Cache Extension
> Issue Type: Wish
> Reporter: Adrian Herscu
> Priority: Trivial
> Labels: documentation
>
> For system test automation we use the Failsafe Plugin.
> In a very small automation project it takes about 20 seconds from launching
> Maven until the tests actually begin.
> If the cache is configured, such as that Failsafe always runs, then after
> cleaning, it fails because no classes are in target directory.
> If Failsafe is not configured to always run, then no testing is done unless
> something is changed in the sources.
> It appears that in both cases, it makes no sense for using the build cache,
> although it could speed execution by preventing what it was meant to prevent
>
> It would be great to have more details if the build cache can be used for
> such scenario, and cut down the start time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
