jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-163) Move the JCR TCK back to the integrationTesting profile
Date Wed, 04 Jul 2012 09:01:37 GMT

    [ https://issues.apache.org/jira/browse/OAK-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406377#comment-13406377
] 

Jukka Zitting commented on OAK-163:
-----------------------------------

I'd like to change that in Jackrabbit trunk as well, there the default build already takes
>10 minutes for me. That's enough time for a coffee break for each build of the codebase.

A long build time is a drain on productivity as to get a deployable build artifact (runnable
jar, OSGi bundle, etc.) you need to run the build. When working on some non-trivial issue,
I typically have to build the codebase at least a half a dozen times before the changes are
ready to be committed. There's little point having long-running tests included in such intermediate
builds, but it would still be useful to have a basic set of fast and simple sanity checks
run on the code to catch any obvious mistakes beyond just compile failures.

Currently I'm using {{mvn clean install -DskipTests}} for such intermediate builds, which
is hardly ideal as a) that disables all tests, and b) requires more typing than the default
build.

Instead I'd like the default build (that's executed most often) to be lean and fast (with
unit tests ideally not taking much more time than it took to compile the relevant code), and
have a separate integration test build ({{mvn clean install -PintegrationTesting}}) for more
complete verification of changes before committing them.

If people prefer to have all tests run on each build, we could still support that use case
on a per-user basis by having the {{integrationTesting}} profile be automatically activated
on something like the presence of an {{OAK_INTEGRATION_TESTING}} environment variable.
                
> Move the JCR TCK back to the integrationTesting profile
> -------------------------------------------------------
>
>                 Key: OAK-163
>                 URL: https://issues.apache.org/jira/browse/OAK-163
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Jukka Zitting
>            Priority: Minor
>              Labels: tck
>
> In revision 1325811 the JCR TCK tests were moved from the integrationTesting profile
to a normal build. However, since then the execution time of the TCK has grown to 3+ minutes,
which is more than the rest of the Oak build combined. To keep the build time down to at most
a couple of minutes, I'd like to move the TCK run back to the integrationTesting profile where
it will get executed only when explicitly requested (typically manually before a commit or
after one in a CI build).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message