You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2021/08/10 07:17:00 UTC
[jira] [Reopened] (JCR-4706) Improve Jackrabbit Release Checker
script to natively support Git clones
[ https://issues.apache.org/jira/browse/JCR-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke reopened JCR-4706:
---------------------------------
> 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)