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 Thu, 12 Apr 2018 06:24:00 GMT

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

Hervé Boutemy edited comment on INFRA-16088 at 4/12/18 6:23 AM:
----------------------------------------------------------------

as discussed and configured in puppet, new svn location for site html output created in http://svn.apache.org/r1828949,
ie in http://svn.apache.org/viewvc/maven/ :
- website/content
- website/components
- doxia/website/content
- doxia/website/components

I also updated site pom.xml https://svn.apache.org/r1828950 and Jenkins job to publish to
this new location: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/15/console
it works!!!
of course, the initial html commit is quite long "Content consists of 81 directories and 447
files = 10 MB", but updates should be more efficient

Tonight, I'll create a new Jenkins job for Doxia site to do the same job

Then I'll discuss with the Maven team to see:
1. when we switch svnwcsub, which will mean we stop using CMS to build and deploy site but
use the new Jenkins job
2. if we want to do GitBox migration at the same time, to get faster source update detection
(given our https://builds.apache.org/job/maven-box/ job that uses ASF organization Jenkins
plugin)

and I'll contact you on HipChat to continue the job (until we finish our job on components,
which will be later...)


was (Author: hboutemy):
as discussed and configured in puppet, new svn location for site html output created in http://svn.apache.org/r1828949,
ie in http://svn.apache.org/viewvc/maven/ :
- website/content
- website/components
- doxia/website/content
- doxia/website/components

I also updated site pom.xml and Jenkins job to publish to this new location: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/15/console
it works!!!
of course, the initial html commit is quite long "Content consists of 81 directories and 447
files = 10 MB", but updates should be more efficient

Tonight, I'll create a new Jenkins job for Doxia site to do the same job

Then I'll discuss with the Maven team to see:
1. when we switch svnwcsub, which will mean we stop using CMS to build and deploy site but
use the new Jenkins job
2. if we want to do GitBox migration at the same time, to get faster source update detection
(given our https://builds.apache.org/job/maven-box/ job that uses ASF organization Jenkins
plugin)

and I'll contact you on HipChat to continue the job (until we finish our job on components,
which will be later...)

> 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
>              Labels: pull-request-available
>
> 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