You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Stevo Slavic (JIRA)" <ji...@apache.org> on 2013/10/28 14:43:30 UTC
[jira] [Resolved] (MAHOUT-1294) Cleanup previously installed
artifacts from CI server local repository
[ https://issues.apache.org/jira/browse/MAHOUT-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stevo Slavic resolved MAHOUT-1294.
----------------------------------
Resolution: Fixed
This is fixed with r1507425 and r1507473 through using {{build-helper-maven-plugin}} and it's {{remove-project-artifact}} goal to remove old mahout artifacts from local Maven repository on Jenkins nodes, in {{prepare-package}} build phase, so before creating and installing new artifacts.
Marking issue as resolved.
> Cleanup previously installed artifacts from CI server local repository
> ----------------------------------------------------------------------
>
> Key: MAHOUT-1294
> URL: https://issues.apache.org/jira/browse/MAHOUT-1294
> Project: Mahout
> Issue Type: Improvement
> Components: build
> Environment: Apache Jenkins CI servers
> Reporter: Stevo Slavic
> Assignee: Stevo Slavic
> Priority: Minor
> Fix For: 0.9
>
>
> Mahout builds produce multiple and relatively large artifacts.
> Before being uploaded to Apache snapshots repository they get installed into Jenkins node local repository.
> [Mahout-Examples-Cluster-Reuters-II|https://builds.apache.org/job/Mahout-Examples-Cluster-Reuters-II/] job often runs on Apache Jenkins nodes with little free disk space, and fails in package phase when trying to create new artifacts.
> We can be little bit better users of Apache infrastructure, and in build jobs on Apache Jenkins nodes, before producing new artifacts, cleanup previously built and installed Apache Mahout artifacts from CI server node local repository.
--
This message was sent by Atlassian JIRA
(v6.1#6144)