[
https://issues.apache.org/jira/browse/JCR-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381911#comment-17381911
]
Andrei Dulceanu commented on JCR-4706:
--------------------------------------
[~kwin] if you have something which works, I'd say we should commit it in order
to avoid situations like the recent one for Oak 1.22.8 in which the community
couldn't validate the release. WDYT?
/cc [~mreutegg]
> Improve Jackrabbit Release Checker script to natively support Git clones
> ------------------------------------------------------------------------
>
> Key: JCR-4706
> URL: https://issues.apache.org/jira/browse/JCR-4706
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
> Attachments: JCR-4706-v1.patch, JCR-4706-v2.patch
>
>
> Currently the script at
> https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh still
> always relies on an SVN export to compare the zipped src with the origin.
> Instead a native Git clone should be performed (against a Gitbox URL)
> whenever the native repo is Git as it seems the SVN client support by GitHub
> (https://github.blog/2011-10-20-improved-subversion-client-support/)
> sometimes has issues.
> I experienced timeouts like this:
> {code}
> svn: E175002: Unexpected HTTP status 504 'Gateway Timeout' on
> '/apache/jackrabbit-oak/!svn/bc/125165/tags/jackrabbit-oak-1.22.8'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)