Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: pass (nike.apache.org: domain of muralihere@gmail.com designates
 209.85.215.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALyHw0GmMC7Oy8uBUs7pGgfmB+4J-3wFAeruxuD+3GKXzrNFRg@mail.gmail.com>
References: 
 <CAL4rnW05_dXCHPQdHh-_B1MSWp_sfY+mHLTAKoe=nxA9x8=JSQ@mail.gmail.com>
	<CALyHw0GmMC7Oy8uBUs7pGgfmB+4J-3wFAeruxuD+3GKXzrNFRg@mail.gmail.com>
Date: Fri, 1 Mar 2013 10:52:28 +0000
Message-ID: 
 <CAL4rnW3hAB20qvQOzufLmWVctCrAiDBGBgGOox7J4t17gztBSw@mail.gmail.com>
Subject: Re: Problems with Continuum making it useless
From: murali mohan <muralihere@gmail.com>
To: users@continuum.apache.org
Content-Type: multipart/alternative; boundary=047d7b3438aeb1516804d6dacd87

--047d7b3438aeb1516804d6dacd87
Content-Type: text/plain; charset=ISO-8859-1

As an immediate solution, I will have to look at other options, I guess.

To solve these, I will try to help. But are people interested in this
project?

-Murali

On Thu, Feb 28, 2013 at 5:53 PM, Brent Atkinson <batkinson@apache.org>wrote:

> Hi Murali,
>
> I'm sorry that you're frustrated.
>
> I doubt I can address everything you're raising as I'm still a relative
> newbie in the code base, but I do know that there are a number of cases
> Continuum doesn't handle, at least without workarounds, in its current
> state. One of them is dependencies between builds and I wonder if this
> limitation is responsible for why the parallel builds work this way.
>
> To be perfectly honest, if you are looking for an immediate solution,
> Continuum may not be the best choice for you. However, if you're interested
> in helping to address the issues, I will do what I can to help.
>
> Brent
>
> On Thu, Feb 28, 2013 at 4:21 AM, murali mohan <muralihere@gmail.com>
> wrote:
>
> > Warning. This is a rant.
> >
> > -> Parallel builds in Continuum is an embarrassment. Reasons:
> >
> >    1. Different builds from the same project cannot be queued if one of
> >    them is already running. Why is this? It is not even the same build,
> it
> > is
> >    a separate buildsbut belonging to the same project. This is a block
> > since
> >    we are forced to time the scheduling perfectly so that the second
> build
> >    starts only after first build is done. Why?! Or we need to have
> separate
> >    project groups. Then why do we need projects?!
> >    2. Shell builds are not running in parallel in version 1.3.6 (Don't
> know
> >    about other versions). Even after enabling parallel builds and queues
> > and
> >    when maven builds run in parallel without any problem.
> >
> > It has become a very clever and unknown science now to run all the builds
> > in parallel in continuum and to ensure that everything completes.
> >
> > -> There are thousand of builds and their history in our continuum
> setup. I
> > have set up purge configurations, but still the UI lists thousands and
> > takes a long time to load.
> >
> > -> For both the above, I have sent emails to support. One is recent, so
> > lets leave that, The deletion of builds - no help to complete it. Some
> > vague suggestions which never worked when I tried. There is some XML RPC
> > tool to delete these old builds. I did spend a couple of days to run it,
> it
> > doesn't!
> >
> > -> Yes, this is open source and we all should contribute. But I am
> someone
> > who has submitted patches before and willing to spend some time. But
> there
> > seems to be no people who are running this or being responsible.
> >
> > -> All in all, I have spent a lot of time on this software from the time
> > when it had very minimal features. Sadly, I think it is a waste of time
> now
> > adjusting schedules and making it "somehow" run.
> >
> > -Murali.
> >
>

--047d7b3438aeb1516804d6dacd87--