[
https://issues.apache.org/jira/browse/OAK-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved OAK-163.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.4
Assignee: Jukka Zitting
Noting the above objections, I still decided to implement this change in
revision 1359014. It's possible to switch back to the previous build behavior
by setting the OAK_INTEGRATION_TESTING environment variable in your
environment, and we can always move the TCK back to the default build if we
start having trouble with broken builds because of this.
> 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
> Assignee: Jukka Zitting
> Priority: Minor
> Labels: tck
> Fix For: 0.4
>
> Attachments:
> 0001-OAK-163-Move-the-JCR-TCK-back-to-the-integrationTest.patch
>
>
> 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
