[Buildbot-devel] First impressions with 0.9.0b1

Sun Jul 19 23:56:37 UTC 2015

I know it's been a half-month, but FYI I reflected the issues as I
understand these emails into bugs:

   - http://trac.buildbot.net/ticket/3311 - Add a metapackage to make
   installing Buildbot easier

   - Force doesn't work - need more info (http://bit.ly/1HJJMOW)

   - http://trac.buildbot.net/ticket/2639 - Rebuild

   - http://trac.buildbot.net/ticket/3312 - Change hook changes

   - http://trac.buildbot.net/ticket/3313 - Migration notes

   - http://trac.buildbot.net/ticket/3314 - IS_NINE constant

   - http://trac.buildbot.net/ticket/3315 - pinned sidebar state

Dustin

On Sun, Jun 28, 2015 at 4:20 PM, Vitali Lovich <vlovich at gmail.com> wrote:

>
> On Jun 28, 2015, at 1:09 PM, Pierre Tardy <tardyp at gmail.com> wrote:
>
> Hi Vitali,
>
> Thanks again for this detailed review.
>
> Indeed, there are a lot of details that changed that may not be in the
> release note.
> We made our possible to detect and document the breaking changes for
> things that were documented, but indeed there are a lot of installs
> (including mine) that are relying on undocumented implementation details.
> We hope that for all those details we reworked it to be more easy to work
> with, like addStepsAfterCurrentStep.
>
> Also, it is difficult for us to sort out the perfect migration guide, as
> it is difficult to know what might be pain point as we ourselves know too
> much the details.
>
> Of course.  That’s why I’m hoping to document it & perhaps get other
> people to contribute their experience.  One thing that tripped me up
> with addStepsAfterCurrentStep is that instead of taking the steps I give it
> it wraps them first in a factory & then creates the step which broke me
> setting the workdir on the step.  Not sure why that’s done but the
> workaround has been to modify the step manually
> after addStepsAfterCurrentStep.
>
> We would be glad if you could contribute a migration guide as you think
> would have helped you better.
>
>
> Now some answers on the details that mayhelp you.
>
> - buildbot-www is the main UI, and supposed to be usable. Indeed it is
> very configurable, you can create your own pages like the waterfall view.
> Please let us now what are the missing features. Indeed, rebuild feature is
> not yet supported. It is not a very hard task. nobody happen to work on it
> yet.
>
> Sure.  I understand that.  Just reporting my findings.
>
> - If the UI locks this is most likely because of a misconfiguration of the
> reverse proxy. Please see here how to configure it correctly
>
> http://docs.buildbot.net/latest/manual/cfg-www.html#reverse-proxy-configuration
> I don't know where to place this information so that it is easy to find.
> This has been a common issue in my experience for my colleagues
>
> I am not using a proxy of any kind.  Connecting directly from my browser
> to the buildbot port on the same machine.
>
> - The forceschedulers are supposed to work. I am using them a lot in my
> prod, so this would most likely be a configuration problem of some sort. We
> can help you to debug
>
> I know they are.  Haven’t quite gotten to the point where I need to debug
> this quite yet.  Still trying to get things to build.  I solved the workdir
> problem (addStepsAfterCurrentStep was behaving strangely).  Now the next
> thing that looks to be broken is slave scheduling.  The set of connected
> slaves moved out of the botmaster so I have to re-write that part of the
> code to work in 0.9 & 0.8.  It looks to be a little complicated at the
> moment.
>
> > The sidebar scrolling in/out & resetting to this behavior is really
> annoying
> Not sure exactly what do you mean.
>
> When you load a page, the pinned state of the sidebar is reset.  Also,
> having the sidebar scroll in & out when I mouse over has been annoying.
> I’d rather it just be expanded by default & if you unpin, then it just
> shows the “shortcut” view instead of sliding out on mouse-over.
>
> Regards
> Pierre
>
>
> Le dim. 28 juin 2015 à 11:22, Vitali Lovich <vlovich at gmail.com> a écrit :
>
>> Yeah.  I know how hard such a major release can be from both the
>> development & adoption.  0.9 is looking awesome & I think it is made better
>> if as many people adopt it as possible; the new live web-view is
>> phenomenally pretty & there’s lot’s of things done right (only a couple
>> that aren’t).
>>
>> Some points about my setup that might be informative (e.g. many people
>> probably won’t encounter the issues I did aside from the obvious ones):
>>
>>    - ~10 builders defined at startup with about maybe half of it being
>>    semi “complex”
>>    - Actual “complex” logic lives externally inside individual projects
>>    (like travis except buildbot-flavor).  Am at the point where I’m trying to
>>    get those to work although I’m fighting with workdir at the moment.
>>    - The issues I had were mostly centered around me introspecting
>>    probably internal state & modifying objects that way
>>       - To create dynamic steps I used to muck around with build & build
>>       status.  Now I can just call `self.build.addStepsAfterCurrentStep`
>>       - To find if the previous step failed I had to introspect the
>>       build status (for do_step_if).  Now: step.build.executedSteps[-2].results
>>    - I was pleasantly surprised that it looks like 0.8.12 buildslave
>>    connects to a 0.9 master without issue.
>>
>> Cheers,
>> Vitali
>>
>> On Jun 28, 2015, at 10:54 AM, Mikhail Sobolev <mss at mawhrin.net> wrote:
>>
>> On Sat, Jun 27, 2015 at 09:00:19PM -0700, Vitali Lovich wrote:
>>
>>   Here are my notes of the changes I encountered migrating to 0.9.0 from
>>   0.8.12.
>>   TLDR: It can be a non-trivial amount of work to get the server to
>> actually
>>   start.  It can be even more non-trivial work to get builds to actually
>> run
>>   properly.
>>
>> Thank you very much for these notes.  Especially about the missing
>> documentation: now we have quite specific things to address.
>>
>> --
>> Misha
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor 25 network devices or servers for free with OpManager!
>> OpManager is web-based network management software that monitors
>> network devices and physical & virtual servers, alerts via email & sms
>> for fault. Monitor 25 devices for free with no restriction. Download now
>> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor 25 network devices or servers for free with OpManager!
>> OpManager is web-based network management software that monitors
>> network devices and physical & virtual servers, alerts via email & sms
>> for fault. Monitor 25 devices for free with no restriction. Download now
>> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20150719/24efc4c5/attachment.html>