Ok, I'll put one in a rack.
On Sep 5, 2013, at 2:17 PM, Dennis Lundberg wrote:
> Getting back to this, I have now confirmation that that the osx node is
> dead. It has also been removed from Jenkins to avoid confusion.
> Den 21 aug 2013 15:59 skrev "Dennis Lundberg" :
>
>> Yes, both OSX and Win
Getting back to this, I have now confirmation that that the osx node is
dead. It has also been removed from Jenkins to avoid confusion.
Den 21 aug 2013 15:59 skrev "Dennis Lundberg" :
> Yes, both OSX and Windows jobs are unreliable in their current state. When
> they are more mature we can move t
On 21 August 2013 14:59, Dennis Lundberg wrote:
> Yes, both OSX and Windows jobs are unreliable in their current state. When
> they are more mature we can move them from the "unstable" view to the
> "stable" view.
>
> Let me check with builds@a.o to see if they have the resources to breathe
> so
Yes, both OSX and Windows jobs are unreliable in their current state. When
they are more mature we can move them from the "unstable" view to the
"stable" view.
Let me check with builds@a.o to see if they have the resources to breathe
some life into that OSX box, before setting up something extern
The only thing I've ever knit is a scarf, in grade 5. So if you want a grade 5
quality scarf, no problem. It will only take me a year.
On Aug 21, 2013, at 6:23 AM, Kristian Rosenvold
wrote:
> Maybe you can knit something for my mac mini flowerpot stand, the one
> that runs windows ?
>
> Kris
Maybe you can knit something for my mac mini flowerpot stand, the one
that runs windows ?
Kristian
2013/8/21 Jason van Zyl :
> I agree that it would be nice to have Windows and OSX builds. But looking at
> our grid and that those builds are either disabled or haven't passed in
> months I don'
I agree that it would be nice to have Windows and OSX builds. But looking at
our grid and that those builds are either disabled or haven't passed in months
I don't think one can consider them reliable, or contribute to the notion of
being releasable.
I can put an OSX machine in a rack, and I ca
In order to get a working build of the Core ITs there are a number of steps
that needs to be taken. These include checking out the source for the ITs
and the version of Maven you want to test. Then there are an elaborate
setup of M2_HOME local.repo and some other stuff. There is a shell script
to h
The jobs you suggested are a minimum (and "OK"). I really think we
should have a functioning windows build too... (I suspect we even have
1 or 2 committers that actually use windows now!)
I have no idea of what is actually wrong with the windows build. I
have a Mac Mini running windows functioning
What do you mean exactly?
Also what about the releasability question?
On Aug 20, 2013, at 7:45 AM, Dennis Lundberg wrote:
> Thanks for looking into this Jason.
>
> As someone who has tried to fix these builds, I think what we need is a
> platform independent way to set up and run the core ITs.
Thanks for looking into this Jason.
As someone who has tried to fix these builds, I think what we need is a
platform independent way to set up and run the core ITs. The best choice is
probably to use Ant.
Den 20 aug 2013 16:18 skrev "Jason van Zyl" :
Thanks for looking into this Jason.
As someone who has tried to fix these builds, I think what we need is a
platform independent way to set up and run the core ITs. The best choice is
probably to use Ant.
Den 20 aug 2013 16:18 skrev "Jason van Zyl" :
> I have separated them like the following to
I have separated them like the following to delineate the stable builds that
are a reliable measure of the ITs working and things that have either been
failing for months, or things we can't reasonably maintain.
If these are working I consider Maven releasable:
https://builds.apache.org/view/M
13 matches
Mail list logo
