Just want to add to this
- freestyle does not have "deploy artifacts" post build step
- freestyle does not have way to use a local maven repository per executor
- freestyle does not have an easy way to use the maven release plugin
So yeah maybe it's evil and has issues, but the maven job type is
FWIW i also tested with an empty maven repository, no difference. So it
must be something that is happening when it parses the POM for dependencies
?
On Wednesday, June 1, 2016 at 10:45:28 AM UTC+2, Jorg Heymans wrote:
>
> The maven repository used is one local to the ex
ory
> operations (up to date check?) take long…
>
> I think for Maven jobs, you should be able to see internal state (current
> threads' stacks?) in the Jenkins UI.
>
> > On 30.05.2016, at 10:14, Jorg Heymans <jorg.h...@gmail.com >
> wrote:
> >
> > Inter
Interestingly, executing offline with -o makes the problem disappear. But
this is obviously not a solution for me..
Jorg
On Monday, May 30, 2016 at 9:52:04 AM UTC+2, Jorg Heymans wrote:
>
> Sadly there is no additional debug output being emitted during the
> 'scanning for projec
:36 PM UTC+2, Jorg Heymans wrote:
>
> Good point! Trying this and will report back ...
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsc
Good point! Trying this and will report back ...
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this
f the artifacts...fingerprints are only needed
> if you try to make dependencies between jobs with SNAPSHOT's otherwise
> is useless.
>
> Furthermore are you using a local maven cache (ake local repository) for
> each job?
>
> Kind regards
> Karl Heinz Marbaise
> On 5/2
No, we keep only two builds. And we do not even archive any artifacts, just
a simple clean install.
Jorg
On Wednesday, May 25, 2016 at 3:39:32 PM UTC+2, David Karlsen wrote:
>
> Are you keeping a lot of build history?
> 25. mai 2016 11:21 skrev "Jorg Heymans" &
Hi,
Since recently in LTS we can configure a local maven repository per
executor. This works beautifully and has saved us about 20G of space on our
CI server making infra happy :)
However we noticed that the m2 repo cleaner plugin (
Hi,
In the latest LTS, using FTP deploy plugin 1.6 we get this exception when
we define 2 transfer sets for the post-build deploy action:
FATAL:
org.apache.commons.lang.StringUtils.join(Ljava/util/Collection;Ljava/lang/String;)Ljava/lang/String;
java.lang.NoSuchMethodError:
Hi,
For a large (100+ m2 jobs) Jenkins instance, what are my options to control
the diskspace taken up by the jobs' private m2 repos ? Since maven does not
handle access to its own local repo transactionally (vote here
http://jira.codehaus.org/browse/MNG-2802) we need to set a private local
, 2012 11:38:08 AM UTC+2, ol...@apache.org wrote:
Recently a repo per executor option has been added.
That could help you
2012/5/16 Jorg Heymans jorg.heym...@gmail.com:
Hi,
For a large (100+ m2 jobs) Jenkins instance, what are my options to
control
the diskspace taken up
For our use case the purging is not really necessary, i was just looking to
reduce the duplication of common dependencies and maven plugins. Also there
is a repo cleaner plugin, that allows you purge by wildcard. I'm wondering
if this is compatible with the per-executor-repo.
Jorg
On
13 matches
Mail list logo