[
https://issues.apache.org/jira/browse/OAK-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406432#comment-13406432
]
Michael Dürig commented on OAK-163:
-----------------------------------
bq. There's a risk that people won't run the TCK before checking in, causing
loss of cycles for somebody else later on.
In my experience this is not only a risk but common practice. And the CI server
doesn't seem to help either. http://ci.apache.org/builders/oak-trunk fails
since quite a while now and no one bothers to have a look.
Having long build times is inconvenient agreed. But failing the build for all
others is a very bad trade off. Optimally:
* everyone runs the integration tests before checkin unless there is very good
reasons to believe nothing will break
* the CI infrastructure would be reliable
* everyone watches the CI server and fixes broken builds caused by self.
Until we have that, I suggest we'd turn the process around and add an option to
smoke test like we had it in OAK-53 before it was reverted.
> 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
> 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
