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-9175) Updating maven.apache.org site download.cgi with an executable flag does not work
Date Mon, 16 Mar 2015 06:46:38 GMT

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

Hervé Boutemy edited comment on INFRA-9175 at 3/16/15 6:46 AM:
---------------------------------------------------------------

"The real question for you Herve is why you are taking a personal interest in fixing this
entire mess"

exactly the same interest than a few years ago when I was forced to switch to CMS, with explanations
that were completely ignoring Maven needs (ie not only a site but components documentation),
then I had to dig into it, understand that under CMS there was svnpubsub then had to write
maven-scm-publish-plugin and work with you on extpaths.txt, understand staging, write documentation
(that nobody understands)

Was I happy? Was it what I wanted to work on? no: what I knew is that fighting against INFRA
was even more pain than working with. And blaming anybody didn't help either.
But I changed it into an opportunity to know new people, work with them, try to understand
how Ops at ASF work: it's all about why I'm working here.

Of course, there are differences between current issue and the CMS change a few years ago,
and you're not completely wrong on the communication issue this time.

But my interest is to continue making things work: and since I'm one of the few understanding
CMS from a user point of view (and it cost me a lot of time...), it was easier to fix the
situation than ranting


was (Author: hboutemy):
"The real question for you Herve is why you are taking a personal interest in fixing this
entire mess"

exactly the same interest than a few years ago when I was forced to switch to CMS, with explanations
that were completely ignoring Maven needs (ie not only a site but components documentation),
then I had to dig into it, understand that under CMS there was svnpubsub then had to write
maven-scm-publish-plugin plugin and work with you on extpaths.txt

Was I happy? Was it what I wanted to work on? no: what I knew is that fighting against INFRA
was even more pain than working with. And blaming anybody didn't help either.

Of course, there are differences between current issue and the CMS change a few years ago,
and you're not completely wrong on the communication issue this time.

But my interest is to continue making things work: and since I'm one of the few understanding
CMS from a user point of view (and it cost me a lot of time...), it was easier to fix the
situation than ranting

> Updating maven.apache.org site download.cgi with an executable flag does not work
> ---------------------------------------------------------------------------------
>
>                 Key: INFRA-9175
>                 URL: https://issues.apache.org/jira/browse/INFRA-9175
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot, SvnPubSub, Website
>            Reporter: Karl Heinz Marbaise
>            Priority: Blocker
>
> I have changed the svn:executable flag in the https://svn.apache.org/repos/asf/maven/site/trunk
but unfortunately the flag is not transfered to the production site.
> In the stdio output of the triggered build http://ci.apache.org/builders/maven-site-staging/builds/231/steps/shell/logs/stdio
you can't see that the download.cgi file has been updated, cause it contains only a change
in the above property.
> The result is that on production site / staging site the download.cgi does not have executable
permission which results in server error.
> Currently the work-a-round is to manually fix the property on production svn https://svn.apache.org/repos/infra/websites/production/maven/content...
> But the permission goes lost through the process of creation.
> After checking some things i found that the separate downloads in the areas of the plugins
like this http://maven.apache.org/plugins/maven-war-plugin/download.cgi, http://maven.apache.org/plugins/maven-ear-plugin/download.cgi,
http://maven.apache.org/plugins/maven-javadoc-plugin/download.cgi don't work either...cause
every plugin has to have a separate download of the appropriate source release which makes
this issue more important.
> I have manually fixed it in svn area https://svn.apache.org/repos/infra/websites/production/maven/content/plugins
for the following list of files:
> {code}
> Karl-Heinzs-MacBook-Pro:plugins kama$ svn st
>  M      maven-acr-plugin/download.cgi
>  M      maven-ant-plugin/download.cgi
>  M      maven-antrun-plugin/download.cgi
>  M      maven-assembly-plugin/download.cgi
>  M      maven-changelog-plugin/download.cgi
>  M      maven-changes-plugin/download.cgi
>  M      maven-checkstyle-plugin/download.cgi
>  M      maven-clean-plugin/download.cgi
>  M      maven-dependency-plugin/download.cgi
>  M      maven-deploy-plugin/download.cgi
>  M      maven-ear-plugin/download.cgi
>  M      maven-ejb-plugin/download.cgi
>  M      maven-gpg-plugin/download.cgi
>  M      maven-install-plugin/download.cgi
>  M      maven-invoker-plugin/download.cgi
>  M      maven-jar-plugin/download.cgi
>  M      maven-jarsigner-plugin/download.cgi
>  M      maven-javadoc-plugin/download.cgi
>  M      maven-linkcheck-plugin/download.cgi
>  M      maven-pdf-plugin/download.cgi
>  M      maven-pmd-plugin/download.cgi
>  M      maven-project-info-reports-plugin/download.cgi
>  M      maven-rar-plugin/download.cgi
>  M      maven-resources-plugin/download.cgi
>  M      maven-scm-publish-plugin/download.cgi
>  M      maven-site-plugin/download.cgi
>  M      maven-source-plugin/download.cgi
>  M      maven-toolchains-plugin/download.cgi
>  M      maven-war-plugin/download.cgi
> {code}
> in Revision 940654.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message