Le 14/11/2014 04:47, Dalai Felinto a écrit :
How to make a build now? After I click on 'Force Build' I land in a
page saying: Authorization Failed. You are not allowed to perform
this action.
Then you did not use the right page to start a build, you need to go on
each builder’s page (as
Don’t think so - and testbuild (now experimental-build) is not the only
one, this can happen (and already have happened) in any branch if you
mess a merge or whatever (even happens when backporting fixes into
release branches…).
Le 14/11/2014 08:00, Thomas Dinges a écrit :
That's not the first
For me it seems this happens because Dalai didn't follow the updates in the
ML and pushed testbuild branch again/ Which for sure created new branch and
pushed all the commits. So in this particular case proper solution would be
if the developers follow the ML, imo.
I can also forbid creating new
Also, maybe we should add in git tips
(http://wiki.blender.org/index.php/Dev:Doc/Tools/Git) a line about `git
fetch -p`, which allows to remove locally branches that where deleted on
the server?
Le 14/11/2014 10:04, Sergey Sharybin a écrit :
For me it seems this happens because Dalai didn't
I wouldn't really advertise this and let developers to manage their local
branches.
On Fri, Nov 14, 2014 at 10:12 AM, Bastien Montagne montagn...@wanadoo.fr
wrote:
Also, maybe we should add in git tips
(http://wiki.blender.org/index.php/Dev:Doc/Tools/Git) a line about `git
fetch -p`, which
How to make a build now? After I click on 'Force Build' I land in a
page saying: Authorization Failed. You are not allowed to perform
this action.
And for the records, in the future it would help to have the outcome
of such an important discussion re-sent to the list as an email on its
own
That's not the first time I have these 100+ e-mails from the testbuild
branch in my inbox. Can't we do something about this? ...
Am 14.11.2014 um 04:47 schrieb Dalai Felinto:
How to make a build now? After I click on 'Force Build' I land in a
page saying: Authorization Failed. You are not
Hi devs,
So, we resurrected testbuild as 'experimental-build', getting rid of the
issues that caused last week's shutdown of this tool (i.e. builds
publicly available from builder.b.o., and confusing name with testbuilds
done during release process).
Note this tool implies commit access to
Did you try using public_html/testbuilds instead? There's also a code in
the template which lusts the dirs, could comment that out.
On Oct 11, 2014 11:27 PM, Bastien Montagne montagn...@wanadoo.fr wrote:
Following Sergey's suggestion (put testbuilds in a separate dir) I
fought a bit with my
Think we should agree on some better name then and deploy?
On Sun, Oct 12, 2014 at 9:19 AM, Bastien Montagne montagn...@wanadoo.fr
wrote:
Good catch, this seems to work fine! :)
Le 12/10/2014 08:26, Sergey Sharybin a écrit :
Did you try using public_html/testbuilds instead? There's also a
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
+1 for enabling branch build option, but probably this needs some kind
of limitation on who may build how often or which branches can be built
how often or so... just a suggestion.
Could need this for my fracture_modifier branch indeed :)
scorpion81
Am Samstag, den 11.10.2014, 15:59 +0200
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
Hi Bastien,
Sorry, I've asked around and had the impression Sergey added the feature on
builder.blender.org.
The fact that building branches on buildbot is useful is not disputed. It's
just not acceptable to offer an official build for download on a popular page
on blender.org, with unknown
It _had been_ discussed several times at least. Starting from discussion in
#lbendercoders between me, Dan, Bastien and even Ton. Then once it was all
set up (and i believe some discussion happened in the ML as well). Once all
the changes to the infrastructure were done it was announced in the ML:
Following Sergey's suggestion (put testbuilds in a separate dir) I
fought a bit with my local version of buildbot to get it running again.
In the end, looks like a very simple change is enough, in
master_unpack.py, something like:
diff --git a/build_files/buildbot/master_unpack.py
16 matches
Mail list logo
