www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7536) Subversion polling fails : Failed to install ... apache-maven-3.0.4-bin.zip
Date Sun, 06 Apr 2014 11:11:17 GMT

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

Gavin commented on INFRA-7536:

[~hboutemy] We know your opinion of not trusting 'Maven 3 (Latest)' and other symlinks but
please don't repeatedly demoralise our volunteers who have to manually update the symlinks
to latest products every time a new release comes out, it does not help.

In the meantime, it would be really fantastic if our jobs were made easier by stating which
Jenkins (or Buildbot) slave(s) had the out of date versions rather than our having to search
them out. This will get better in the future with some increase in automation of the slaves
in terms of software installs/upgrades.

> Subversion polling fails : Failed to install ... apache-maven-3.0.4-bin.zip
> ---------------------------------------------------------------------------
>                 Key: INFRA-7536
>                 URL: https://issues.apache.org/jira/browse/INFRA-7536
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Robert Munteanu
>            Priority: Critical
>         Attachments: sling-trunk-1.7-job-config.png, svn-polling-log-sling-trunk-1.7.txt
> The Sling 1.7 job no longer runs. The error is logged at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/scmPollLog/
 . The root cause is
> Caused by: java.io.IOException: Failed to mkdirs: /home/hudson/tools/maven/apache-maven-3.0.4
> 	at hudson.FilePath.mkdirs(FilePath.java:1069)
> 	at hudson.FilePath.installIfNecessaryFrom(FilePath.java:732)
> 	... 19 more
> I tried to work around this problem by configuring the job to use Maven 3 (latest), but
it did not help.

This message was sent by Atlassian JIRA

View raw message