I thought you had to install a Jenkins plugin to get a green build ;-)
Regards
Mirko
--
Sent from my mobile
On Mar 28, 2014 2:38 PM, "Stephen Connolly"
wrote:
> I've merged it... though who knows!
>
>
> On 28 March 2014 12:37, Baptiste Mathus wrote:
>
> > Hi,
> >
> > To stay on the track of Mi
On 28 March 2014 12:09, Anders Hammar wrote:
>> The requirements also says:
>>
>> "Disk No minimum requirement. Approximately 100MB will be used for
>> your local repository, however this will vary depending on usage ..."
>>
>> AFAICT there _is_ a minimum requirement which is needed to store a
>>
Github user asfgit closed the pull request at:
https://github.com/apache/maven-scm/pull/11
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Hello Stephen,
I am a big fan of pipelines here:
1. clean test-compile
2. clean verify of modules with changes or excluding failsafe/invoker
3. clean verify of all modules with inclusion of invoker tests.
Regards
Mirko
--
Sent from my mobile
On Mar 28, 2014 1:02 PM, "Stephen Connolly"
wrote:
I've merged it... though who knows!
On 28 March 2014 12:37, Baptiste Mathus wrote:
> Hi,
>
> To stay on the track of Mirko's last email, my original PR for SCM-741 [1]
> seems to make the IT fail in maven-scm CI [2].
>
> After analyzing the failure logs, I've created another PR that should
> ho
+1, my repo is about 1.3GB so saying "500+ MB or more depending on your
usage" seems sensible.
2014-03-28 13:09 GMT+01:00 Anders Hammar :
> > The requirements also says:
> >
> > "Disk No minimum requirement. Approximately 100MB will be used for
> > your local repository, however this will vary
Make sure to use the existing URL of
http://maven.apache.org/release-notes.html to get to the starting point of
this. This URL is found in our distros as well as on the site.
/Anders
On Tue, Mar 25, 2014 at 5:13 AM, Jason van Zyl wrote:
> If no one else minds I'll convert it all to single mark
Hi,
To stay on the track of Mirko's last email, my original PR for SCM-741 [1]
seems to make the IT fail in maven-scm CI [2].
After analyzing the failure logs, I've created another PR that should
hopefully fix the issue (first PR worked locally, but the issue seems
specific to CI env) :
https://g
> The requirements also says:
>
> "Disk No minimum requirement. Approximately 100MB will be used for
> your local repository, however this will vary depending on usage ..."
>
> AFAICT there _is_ a minimum requirement which is needed to store a
> basic set of plugins.
> And of course there is the Ma
I would rather get some good pipelining going so that we have a better
quality of jobs in the first place, e.g. see the job pipeline I have set up
https://builds.apache.org/job/maven-3.2-release-status/
I want to add other tests into this pipeline and once we have a strong
template for a good pipe
Cool! The pipeline is working!
On 26 March 2014 15:02, Apache Jenkins Server wrote:
> This is an automated email to notify the Maven developer list that there
> are unreleased changes in the Maven 3.2.x GIT branch that have passed all
> the integration tests and are therefore potentially releasa
Well, the Windows IT build [1] has failed constantly for over a month. :-(
/Anders
[1] https://builds.apache.org/view/M-R/view/Maven/job/core-it-maven-3-win/
On Fri, Mar 28, 2014 at 12:32 PM, Mirko Friedenhagen <
mfriedenha...@gmail.com> wrote:
> Hello,
>
> as a fresh subscriber to notificatio
Hello,
as a fresh subscriber to notifications I really wonder how often the jobs
have failed in the last two weeks.
- One reason seems to be, that during staging of plugins and especially
shared components the jobs are failing because of staged dependencies are
not available in central. I propose
I have updated quite a few places to asm 4.x compliance (and hence 5.x). Do
let me know if I missed something, I can do the rest.
(The api changes are fairly significant so I'm assuming I can do further
upgrades about twice as fast as someone who hasn't done it...)
K
2014-03-28 8:11 GMT+01:00
why didn't we detect the failure when building the plugin and running ITs with
JDK 8 = somthing we did a long time ago and that I was conviced would give us
more accurate results than what we finally have?
I had a quick look at ITs, and it seems that the compiler plugin is configured
to generat
15 matches
Mail list logo
