You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2013/09/05 20:17:49 UTC
Re: Maven Core ITs and releasable state
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" <de...@apache.org>:
> 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 external.
>
> I'm happy to try out any tools for Windows. I have a local Jenkins running
> on Windows where I can test drive and tweak them, before they're ready to
> be deployed to builds.apache.org
>
> The set of 3 is probably what can be trusted at the moment, but I'd also
> like to get "core-integration-testing-maven-3" into the "stable" view. It
> is a Java 5 build of Maven 3 master. As long as we support Java 5 it should
> pass.
>
>
> On Wed, Aug 21, 2013 at 3:13 PM, Jason van Zyl <ja...@tesla.io> wrote:
>
>> 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 can help make a general way to
>> provision and setup a run for Maven with the ITs. I have tools for this and
>> they are just written in Java which I think is fine. Dennis, I'm happy to
>> help with some tools if you want to try them out on a Windows machine.
>>
>> I will consider that set of 3 as good of an indicator as we have now and
>> if it improves great. But currently as the RM for the core, if there are
>> improvements or bug fixes available and I want to do a release I will
>> consider that set of three jobs being good as the core being in a
>> releasable state. I would love an OSX build and I can look into that. I
>> will help someone else with the Windows build, but I honestly have as the
>> same level of proficiency with Windows as I do, say, knitting.
>>
>> On Aug 21, 2013, at 12:32 AM, Dennis Lundberg <de...@apache.org> wrote:
>>
>> > 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 help with this, but it is for Linux/Unix only. If you take a look at
>> the
>> > Jenkins jobs that runs the ITs there are several platform dependent
>> steps.
>> >
>> > To get more people to help run the ITs in different environments, we
>> need
>> > to make this simpler, especially for Windows. So I suggest that we put
>> > together an Ant script that can be used by all users, including CI
>> builds,
>> > to do the necessary setup.
>> >
>> > As for releaseability I think that we should have both the windows and
>> osx
>> > jobs pass.
>> >
>> > That being said, it seems that the osx installation is dead and won't be
>> > coming back any time soon, so until then we can't rely on it. We have
>> lots
>> > of devs running osx so it shouldn't be a problem getting confirmation
>> that
>> > the ITs pass on that platform.
>> >
>> > Since I'm on Windows myself I'm keen to get the Windows job into a
>> runnable
>> > state. I did some work on it before, but finally gave up because of the
>> > platform dependent steps that was needed, in combination with some
>> > limitations in the properties that are available to Jenkins on Windows.
>> I'm
>> > willing to work on it again though.
>> >
>> > Related to this, what's the status on Core ITs for Maven 2? Are the ITs
>> > that this thread talk about applicable to Maven 2, or does it use a
>> > different set of ITs?
>> >
>> > On Tue, Aug 20, 2013 at 5:17 PM, Jason van Zyl <ja...@tesla.io> wrote:
>> >
>> >> What do you mean exactly?
>> >>
>> >> Also what about the releasability question?
>> >>
>> >> On Aug 20, 2013, at 7:45 AM, Dennis Lundberg <de...@apache.org>
>> 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. The best
>> choice
>> >> is
>> >>> probably to use Ant.
>> >>> Den 20 aug 2013 16:18 skrev "Jason van Zyl" <ja...@tesla.io>:
>> >>>
>> >>>> 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-R/view/Maven%20Core%20ITs/
>> >>>>
>> >>>> I put the rest of them here:
>> >>>>
>> >>>>
>> >>
>> https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs%20(unstable)/
>> >>>>
>> >>>> If the jobs in the first group are passing can we consider that being
>> >> in a
>> >>>> reasonable state for a release?
>> >>>>
>> >>>> Thanks,
>> >>>>
>> >>>> Jason
>> >>>>
>> >>>> ----------------------------------------------------------
>> >>>> Jason van Zyl
>> >>>> Founder, Apache Maven
>> >>>> http://twitter.com/jvanzyl
>> >>>> ---------------------------------------------------------
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>
>> >> Thanks,
>> >>
>> >> Jason
>> >>
>> >> ----------------------------------------------------------
>> >> Jason van Zyl
>> >> Founder, Apache Maven
>> >> http://twitter.com/jvanzyl
>> >> ---------------------------------------------------------
>> >>
>> >> We know what we are, but know not what we may be.
>> >>
>> >> -- Shakespeare
>> >>
>> >> --
>> >> Dennis Lundberg
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> Our achievements speak for themselves. What we have to keep track
>> of are our failures, discouragements and doubts. We tend to forget
>> the past difficulties, the many false starts, and the painful
>> groping. We see our past achievements as the end result of a
>> clean forward thrust, and our present difficulties as
>> signs of decline and decay.
>>
>> -- Eric Hoffer, Reflections on the Human Condition
>>
>> --
>> Dennis Lundberg
>
>
Re: Maven Core ITs and releasable state
Posted by Jason van Zyl <ja...@tesla.io>.
Ok, I'll put one in a rack.
On Sep 5, 2013, at 2:17 PM, Dennis Lundberg <de...@apache.org> 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" <de...@apache.org>:
>
>> 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 external.
>>
>> I'm happy to try out any tools for Windows. I have a local Jenkins running
>> on Windows where I can test drive and tweak them, before they're ready to
>> be deployed to builds.apache.org
>>
>> The set of 3 is probably what can be trusted at the moment, but I'd also
>> like to get "core-integration-testing-maven-3" into the "stable" view. It
>> is a Java 5 build of Maven 3 master. As long as we support Java 5 it should
>> pass.
>>
>>
>> On Wed, Aug 21, 2013 at 3:13 PM, Jason van Zyl <ja...@tesla.io> wrote:
>>
>>> 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 can help make a general way to
>>> provision and setup a run for Maven with the ITs. I have tools for this and
>>> they are just written in Java which I think is fine. Dennis, I'm happy to
>>> help with some tools if you want to try them out on a Windows machine.
>>>
>>> I will consider that set of 3 as good of an indicator as we have now and
>>> if it improves great. But currently as the RM for the core, if there are
>>> improvements or bug fixes available and I want to do a release I will
>>> consider that set of three jobs being good as the core being in a
>>> releasable state. I would love an OSX build and I can look into that. I
>>> will help someone else with the Windows build, but I honestly have as the
>>> same level of proficiency with Windows as I do, say, knitting.
>>>
>>> On Aug 21, 2013, at 12:32 AM, Dennis Lundberg <de...@apache.org> wrote:
>>>
>>>> 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 help with this, but it is for Linux/Unix only. If you take a look at
>>> the
>>>> Jenkins jobs that runs the ITs there are several platform dependent
>>> steps.
>>>>
>>>> To get more people to help run the ITs in different environments, we
>>> need
>>>> to make this simpler, especially for Windows. So I suggest that we put
>>>> together an Ant script that can be used by all users, including CI
>>> builds,
>>>> to do the necessary setup.
>>>>
>>>> As for releaseability I think that we should have both the windows and
>>> osx
>>>> jobs pass.
>>>>
>>>> That being said, it seems that the osx installation is dead and won't be
>>>> coming back any time soon, so until then we can't rely on it. We have
>>> lots
>>>> of devs running osx so it shouldn't be a problem getting confirmation
>>> that
>>>> the ITs pass on that platform.
>>>>
>>>> Since I'm on Windows myself I'm keen to get the Windows job into a
>>> runnable
>>>> state. I did some work on it before, but finally gave up because of the
>>>> platform dependent steps that was needed, in combination with some
>>>> limitations in the properties that are available to Jenkins on Windows.
>>> I'm
>>>> willing to work on it again though.
>>>>
>>>> Related to this, what's the status on Core ITs for Maven 2? Are the ITs
>>>> that this thread talk about applicable to Maven 2, or does it use a
>>>> different set of ITs?
>>>>
>>>> On Tue, Aug 20, 2013 at 5:17 PM, Jason van Zyl <ja...@tesla.io> wrote:
>>>>
>>>>> What do you mean exactly?
>>>>>
>>>>> Also what about the releasability question?
>>>>>
>>>>> On Aug 20, 2013, at 7:45 AM, Dennis Lundberg <de...@apache.org>
>>> 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. The best
>>> choice
>>>>> is
>>>>>> probably to use Ant.
>>>>>> Den 20 aug 2013 16:18 skrev "Jason van Zyl" <ja...@tesla.io>:
>>>>>>
>>>>>>> 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-R/view/Maven%20Core%20ITs/
>>>>>>>
>>>>>>> I put the rest of them here:
>>>>>>>
>>>>>>>
>>>>>
>>> https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs%20(unstable)/
>>>>>>>
>>>>>>> If the jobs in the first group are passing can we consider that being
>>>>> in a
>>>>>>> reasonable state for a release?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder, Apache Maven
>>>>>>> http://twitter.com/jvanzyl
>>>>>>> ---------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>> We know what we are, but know not what we may be.
>>>>>
>>>>> -- Shakespeare
>>>>>
>>>>> --
>>>>> Dennis Lundberg
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> Our achievements speak for themselves. What we have to keep track
>>> of are our failures, discouragements and doubts. We tend to forget
>>> the past difficulties, the many false starts, and the painful
>>> groping. We see our past achievements as the end result of a
>>> clean forward thrust, and our present difficulties as
>>> signs of decline and decay.
>>>
>>> -- Eric Hoffer, Reflections on the Human Condition
>>>
>>> --
>>> Dennis Lundberg
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------