infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-16088) configure credentials on Jenkins nodes to commit to svnpubsub
Date Sat, 31 Mar 2018 19:13:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421428#comment-16421428
] 

Hervé Boutemy edited comment on INFRA-16088 at 3/31/18 7:12 PM:
----------------------------------------------------------------

Git is for site source (Markdown, apt, xdoc, + maven pom.xml), svn/svnpubsub/svnwcsub is for
generated html

if you want to get rid of https://svn.apache.org/repos/infra/ and prefer storing generated
html to http://svn.apache.org/repos/asf/, we can: from a personal perspective, I don't like
it because it means storing generated content to /repos/asf/, but you better know than me
the ASF strategy on svn repos

if you want to get rid of /repos/infra/, we'll need to create the same content + components
subdirectories as we have in https://svn.apache.org/repos/infra/websites/production/maven/
The switch for components will be harder to manage at Maven level, but if you really want
it, we'll do it.

We'll need also to reproduce the svnwcsub configuration for these content and components subdirectories
And this will have to be done at Maven and Doxia level (yes, we have 2 site, with 2 svnwcsub
per site, see https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnwcsub/files/svnwcsub.conf#L152
)


was (Author: hboutemy):
Git is for site source (Markdown, apt, xdoc, + maven pom.xml), svn/svnpubsub/svnwcsub is for
generated html

if you want to get rid of https://svn.apache.org/repos/infra/ and prefer storing generated
html to http://svn.apache.org/repos/asf/, we can: from a personal perspective, I don't like
it because it means storing generated content to /repos/asf/, but you better know than me
the ASF strategy on svn repos

if you want to get rid of /repos/infra/, we'll need to create the same content + components
subdirectories as we have in https://svn.apache.org/repos/infra/websites/production/maven/
The switch for components will be harder to manage at Maven level, but if you really want
it, we'll do it.

We'll need also to reproduce the svnwcsub configuration for these content and components subdirectories

> configure credentials on Jenkins nodes to commit to svnpubsub
> -------------------------------------------------------------
>
>                 Key: INFRA-16088
>                 URL: https://issues.apache.org/jira/browse/INFRA-16088
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Hervé Boutemy
>            Assignee: Chris Lambertus
>            Priority: Major
>
> Currently, there are 2 Jenkins nodes with credentials to commit to gitpubsub
> Maven uses svnpubsub (and need to continue to use it, see https://lists.apache.org/thread.html/72ede3758155d156e171fd5b4eda2716bb2fdc50c3759888f968eb46@%3Cbuilds.apache.org%3E)
> Please configure credentials on some Jenkins nodes to be able to publish to svnpubsub:
this will be a step for Maven to stop using CMS and replace with following Jenkins job https://builds.apache.org/view/M-R/view/Maven/job/maven-site/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message