[
https://issues.apache.org/jira/browse/JCR-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396496#comment-17396496
]
Julian Reschke edited comment on JCR-4706 at 8/10/21, 7:19 AM:
---------------------------------------------------------------
The changes for this ticket broke SVN support (what happens is that svn export
exports to a child directory of where it's supposed to go, and thus the diff
fails to work).
I'm reverting the changes now so that I can release Jackrabbit 2.16.8.
was (Author: reschke):
The changes for this ticket broke SVN support (what happens is that svn export
export to a child directory of where it's supposed to go).
I'm reverting the changes now so that I can release Jackrabbit 2.16.8.
> 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
> Assignee: 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)
