You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Konrad Windszus <kw...@apache.org> on 2023/12/12 11:33:16 UTC
Jackrabbit Site: Migrate to Git
Hi,
Currently the source for the Jackrabbit website is maintained at https://svn.apache.org/repos/asf/jackrabbit/site/trunk/.
The Maven site build generates the target site out of that and the maven-scm-publish-plugin pushes the generated site to https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr/ afterwards.
The last step is the tool svnpubsub (executed by ASF INFRA) publishing those files to https://jackrabbit.apache.org/
I propose to create a new git repository for the Jackrabbit (2) site source at https://gitbox.apache.org/repos/asf/jackrabbit-site.git / https://github.com/apache/jackrabbit-site and let INFRA migrate the SVN repository location https://svn.apache.org/repos/asf/jackrabbit/site/trunk/ into that new repo (keeping the history)
That is the last active piece of the puzzle in the Jackrabbit ecosystem which is still leveraging SVN.
Note: I don’t propose to change the SVN repository containing the "generated site” at https://svn.apache.org/repos/asf/jackrabbit/site/live/. That is currently the target of multiple sources, namely
- https://github.com/apache/jackrabbit-filevault/tree/master/src/site
- https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/master/src/site and
- https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc/src/site
I don’t think there is an urgent need for changing this to Git as well, as the active work uses the source repository locations only.
WDYT?
Konrad
Re: Jackrabbit Site: Migrate to Git
Posted by Konrad Windszus <kw...@apache.org>.
Migration is now complete. From now on please use https://github.com/apache/jackrabbit-site to commit changes to the JR2 part of the JR website.
The according SVN repository in https://svn.apache.org/repos/asf/jackrabbit/site/trunk was put to read-only mode.
Let me know in case you face any issues.
Konrad
P.S. The automated build and deployment of the website on Jenkins does not yet work due to missing credentials (https://issues.apache.org/jira/browse/INFRA-25453) but the manual process described in https://github.com/apache/jackrabbit-site/blob/main/README.md works fine.
> On 24. Jan 2024, at 20:45, Konrad Windszus <kw...@apache.org> wrote:
>
> Hi,
> Due to the size of the generated site (almost 2GB without history) I decided for now to leave the https://svn.apache.org/repos/asf/jackrabbit/site/live/ in place.
>
> The source for the JR2 part of the site was imported from https://svn.apache.org/repos/asf/jackrabbit/site/trunk to https://github.com/apache/jackrabbit-site
> Please check the latter if everything looks good there.
>
> The canonical repo of the site stays for now https://svn.apache.org/repos/asf/jackrabbit/site/trunk until I gathered some feedback on the migrated state and the according SVN repo is read only.
> I will send another mail, once that is done.
>
> Konrad
>
>> On 14. Jan 2024, at 15:25, Konrad Windszus <kw...@apache.org> wrote:
>>
>> I created https://issues.apache.org/jira/browse/JCRSITE-55 to track this.
>>
>> Konrad
>>
>>> On 14. Jan 2024, at 14:12, Julian Reschke <ju...@gmx.de> wrote:
>>>
>>> On 11.01.2024 16:56, Konrad Windszus wrote:
>>>> Ping, any feedback? Otherwise I would start an official VOTE soon.
>>>> ...
>>>
>>> +1 in general, and I don't think we need a vote.
>>>
>>> The one thing I'd suggest is to do this step-by-step where possible.
>>>
>>> Best regards, Julian
>>
>
Re: Jackrabbit Site: Migrate to Git
Posted by Konrad Windszus <kw...@apache.org>.
Hi,
Due to the size of the generated site (almost 2GB without history) I decided for now to leave the https://svn.apache.org/repos/asf/jackrabbit/site/live/ in place.
The source for the JR2 part of the site was imported from https://svn.apache.org/repos/asf/jackrabbit/site/trunk to https://github.com/apache/jackrabbit-site
Please check the latter if everything looks good there.
The canonical repo of the site stays for now https://svn.apache.org/repos/asf/jackrabbit/site/trunk until I gathered some feedback on the migrated state and the according SVN repo is read only.
I will send another mail, once that is done.
Konrad
> On 14. Jan 2024, at 15:25, Konrad Windszus <kw...@apache.org> wrote:
>
> I created https://issues.apache.org/jira/browse/JCRSITE-55 to track this.
>
> Konrad
>
>> On 14. Jan 2024, at 14:12, Julian Reschke <ju...@gmx.de> wrote:
>>
>> On 11.01.2024 16:56, Konrad Windszus wrote:
>>> Ping, any feedback? Otherwise I would start an official VOTE soon.
>>> ...
>>
>> +1 in general, and I don't think we need a vote.
>>
>> The one thing I'd suggest is to do this step-by-step where possible.
>>
>> Best regards, Julian
>
Re: Jackrabbit Site: Migrate to Git
Posted by Konrad Windszus <kw...@apache.org>.
I created https://issues.apache.org/jira/browse/JCRSITE-55 to track this.
Konrad
> On 14. Jan 2024, at 14:12, Julian Reschke <ju...@gmx.de> wrote:
>
> On 11.01.2024 16:56, Konrad Windszus wrote:
>> Ping, any feedback? Otherwise I would start an official VOTE soon.
>> ...
>
> +1 in general, and I don't think we need a vote.
>
> The one thing I'd suggest is to do this step-by-step where possible.
>
> Best regards, Julian
Re: Jackrabbit Site: Migrate to Git
Posted by Julian Reschke <ju...@gmx.de>.
On 11.01.2024 16:56, Konrad Windszus wrote:
> Ping, any feedback? Otherwise I would start an official VOTE soon.
> ...
+1 in general, and I don't think we need a vote.
The one thing I'd suggest is to do this step-by-step where possible.
Best regards, Julian
Re: Jackrabbit Site: Migrate to Git
Posted by Konrad Windszus <kw...@apache.org>.
Ping, any feedback? Otherwise I would start an official VOTE soon.
After having a second thought I would also propose to replace svnpubsub (being managed by INFRA manually) by the equivalent for Git which can be controlled through .asf.yaml: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories. This internally relies on https://infra.apache.org/pypubsub.html.
That means that we would generate the HTML for the site in the according subproject:
- https://github.com/apache/jackrabbit-filevault/tree/master/src/site
- https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/master/src/site and
- https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc/src/site
in a dedicated branch and just configure the sub directory feature accordingly: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-Specifyingasub-directorytopublishto
That way each module of the jackrabbit site (JR2, Oak, FileVault, …) is nicely encapsulated and there is no longer the need for cross-repository writes to publish the site.
Konrad
> On 12. Dec 2023, at 12:33, Konrad Windszus <kw...@apache.org> wrote:
>
> Hi,
> Currently the source for the Jackrabbit website is maintained at https://svn.apache.org/repos/asf/jackrabbit/site/trunk/.
> The Maven site build generates the target site out of that and the maven-scm-publish-plugin pushes the generated site to https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr/ afterwards.
> The last step is the tool svnpubsub (executed by ASF INFRA) publishing those files to https://jackrabbit.apache.org/
>
> I propose to create a new git repository for the Jackrabbit (2) site source at https://gitbox.apache.org/repos/asf/jackrabbit-site.git / https://github.com/apache/jackrabbit-site and let INFRA migrate the SVN repository location https://svn.apache.org/repos/asf/jackrabbit/site/trunk/ into that new repo (keeping the history)
> That is the last active piece of the puzzle in the Jackrabbit ecosystem which is still leveraging SVN.
>
> Note: I don’t propose to change the SVN repository containing the "generated site” at https://svn.apache.org/repos/asf/jackrabbit/site/live/. That is currently the target of multiple sources, namely
> - https://github.com/apache/jackrabbit-filevault/tree/master/src/site
> - https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/master/src/site and
> - https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc/src/site
>
> I don’t think there is an urgent need for changing this to Git as well, as the active work uses the source repository locations only.
>
> WDYT?
> Konrad