[Bf-committers] Revising the testbuild branch

[Sergey Sharybin]

Bastien, configuration is still there, it's all just commented out (in fact
it's just a one-liner). It might be used for a "refined" tesbuild process.

I'm not happy with the idea of being able to build any of the branches.
it'll get out of control real easily. IMO, better thing to do would be to
keep process the same and just tweak uploader so it puts testbuild to a
separate folder, not visible from the web UI, but available with some
direct location like "https://builder.blender.org/testbuilds", so
developers cn poke buildbot and re-upload builds to some more permanent
location or just let users to quickly test changes.

Can look into this, but not gonna to do it during my spare time.

On Sat, Oct 11, 2014 at 6:24 PM, Bastien Montagne <montagne29 at wanadoo.fr>
wrote:

> I’m not happy at all with both the decision and the way it was taken.
> Fyi, I was the one who spent a fair amount of time some months agon
> setting this up, and I think it has proven to be really really useful
> for all wip projects around.
>
> Further more, I do not see any reason to just cut this out out of the
> blue, there was no urgency at all here. And I do not even really
> understand the root of the issue, imho people who are not able to make a
> distinction between builds tagged as 'official' and builds tagged as
> 'testbuild' have nothing to do on builder.b.o.
>
> But even though, imho it would have been much nicer to ask to add some
> way to delete testbuilds from the server, again see no urgency at all
> here that could justify this discontinuation.
>
> Adding back build of all branches will just create much much more mess,
> we won’t gain anything. Oh, and people that cannot understand what
> 'testbuild' means won’t be able either to distinguish from master and
> branches builds - even less I’d say.
>
> Very disapointed here!
> Bastien
>
> Le 11/10/2014 15:59, Ton Roosendaal a écrit :
> > Hi,
> >
> > I've asked Sergey to disable the testbuild branch from automatic
> building.
> > This is currently leading to a confusing situation. People have no idea
> what's the code that is in it. It's even being used to apply patches from
> the tracker on it. This information is invisible for our website visitors.
> >
> > Worse is that visitors think it's the official release test build, and
> not a testing branch for coders only.
> >
> > We should do this better communicated. Can we just back to the old
> option that you can build branches?
> > This way that branch build gets properly named and timestamped.
> >
> > The only problem is that too many builds might flood the bot's list of
> builds. It shouldn't be too hard to make a delete button on that page for
> old ones (for admins)?
> >
> > Laters,
> >
> > -Ton-
> >
> > --------------------------------------------------------
> > Ton Roosendaal  -  ton at blender.org   -   www.blender.org
> > Chairman Blender Foundation - Producer Blender Institute
> > Entrepotdok 57A  -  1018AD Amsterdam  -  The Netherlands
> >
> >
> >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin