[
https://issues.apache.org/jira/browse/COMDEV-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956259#comment-17956259
]
Herve Boutemy commented on COMDEV-561:
--------------------------------------
> There is no website publication step. The website is created when the code is
> checked out on the server.
there is no build step, but checking out to the web server is the publication:
does projects.a.o use a different web server (hosted on projects/reporter
machine) than every other ASF website?
IIRC, the machine is used for cronjobs that require direct access to ASF
internal service, but I can't really tell about the web server
> There are various cronjobs that update files on the server, and another job
> which commits changes.
> In the case of SVN, this means providing the password when committing the
> changes.
do you see any drawback going to Git auth instead of svn auth?
any complexity?
any other aspect we should take care of not breaking?
I'd love to get PRs workflows when updating projects.a.o as a diverse team as
we are, then require discussion on code
> migrate projects to Git
> -----------------------
>
> Key: COMDEV-561
> URL: https://issues.apache.org/jira/browse/COMDEV-561
> Project: Community Development
> Issue Type: Improvement
> Components: Projects Tool
> Reporter: Herve Boutemy
> Priority: Major
>
> in COMDEV-288, we let the source code in svn but created a svn2git Git mirror
> https://github.com/apache/comdev-projects
> next step is to make Git read-write
> full impact analysis to be done, but we can immediately list a few topics:
> - cronjobs update to commit to Git instead of svn
> - switch to ASF website publication from Git instead of svn (probably through
> .asf.yaml)
> anything else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
