[Buildbot-devel] Looking for suggestions (TrySchedulers - Buildbot 0.9)

Francesco Di Mizio francescodimizio at gmail.com
Sat Feb 7 15:46:39 UTC 2015 

Mickhael adjusted the autobuilds. Using the wheel worked out very well.

On Fri, Feb 6, 2015 at 12:22 AM, Dustin J. Mitchell <dustin at v.igoro.us>
wrote:

> So yeah, you need npm and node.  It looks like there's some PATH
> funniness there on Windows.  On Ubuntu, that gulp error is odd -- do
> you not have access to that directory?
>
> Dustin
>
> On Sun, Feb 1, 2015 at 6:46 PM, Francesco Di Mizio
> <francescodimizio at gmail.com> wrote:
> > Did further investigations:
> >
> > Make forntend fails with:
> >
> > bash.exe"-3.1$ make frontend
> > pip install -e pkg
> > Obtaining file:///e:/bbsrc/buildbot/pkg
> >   Running setup.py (path:e:/bbsrc/buildbot/pkg\setup.py) egg_info for
> > package fr
> > om file:///e:/bbsrc/buildbot/pkg
> >
> > Installing collected packages: buildbot-pkg
> >   Running setup.py develop for buildbot-pkg
> >
> >     Creating c:\python27\lib\site-packages\buildbot-pkg.egg-link (link
> to .)
> >     buildbot-pkg 0.9.0 is already the active version in easy-install.pth
> >
> >     Installed e:\bbsrc\buildbot\pkg
> > Successfully installed buildbot-pkg
> > Cleaning up...
> > pip install mock
> > Requirement already satisfied (use --upgrade to upgrade): mock in
> > c:\python27\li
> > b\site-packages
> > Cleaning up...
> > for i in www/*/; do pip install -e $i ; done
> > Obtaining file:///e:/bbsrc/buildbot/www/base
> >   Running setup.py (path:e:/bbsrc/buildbot/www/base\setup.py) egg_info
> for
> > packa
> > ge from file:///e:/bbsrc/buildbot/www/base
> >     npm install
> >     error: command 'npm' failed: No such file or directory
> >     Complete output from command python setup.py egg_info:
> >     running egg_info
> >
> > npm install
> >
> > error: command 'npm' failed: No such file or directory
> >
> > ----------------------------------------
> > Cleaning up...
> > Command python setup.py egg_info failed with error code 1 in
> > e:/bbsrc/buildbot/w
> > ww/waterfall_view
> > Storing debug log for failure in C:\Users\Riziero\pip\pip.log
> > make: *** [frontend] Error 1
> > bash.exe"-3.1$
> >
> >
> > Above I stripped out the 3 parts as it fails the same way with all 4 www
> > subfolder.
> >
> > I can run ok npm, by issuing "npm" I get the help.
> >
> > Cheers,
> >  Francesco
> >
> > On Sun, Feb 1, 2015 at 9:43 PM, Francesco Di Mizio
> > <francescodimizio at gmail.com> wrote:
> >>
> >> I failed to install Nine following that tutorial.
> >>
> >> I was on Win and did everything on a Linux like shell (GitBash). Better
> do
> >> it on Linux?
> >>
> >> First off: do i necesserally need to create a virtualenv? I tried
> without
> >> (had to install pywin32) and upon buildbot master startup I got:
> >>
> >> File "e:\bbsrc\buildbot\master\buildbot\www\service.py", line 121, in
> >> setupSite
> >>    raise RuntimeError("could not find buildbot-www; is it installed?")
> >> exceptions.RuntimeError: could not find buildbot-www; is it installed?
> >>
> >> Wanted then to give virualenv a try and repeat - didnt go that far as I
> >> have got no idea how get the virtualenv to see pywin32.
> >>
> >>
> >> On Wed, Jan 28, 2015 at 12:52 PM, Pierre Tardy <tardyp at gmail.com>
> wrote:
> >>>
> >>> We used to have daily builds of aster branch, but this has been
> >>> temporarily stopped until we sort out some of our new infra work
> >>> So the package here are slightly outdated, and some are actually
> broken.
> >>> ftp://ftp.buildbot.net/pub/latest/
> >>>
> >>> So right now the best is to follow this quick start guide:
> >>>
> >>>
> https://github.com/buildbot/buildbot/blob/master/master/docs/developer/www.rst#hacking-quick-start
> >>>
> >>>
> >>> Le Wed Jan 28 2015 at 12:37:41 PM, Francesco Di Mizio
> >>> <francescodimizio at gmail.com> a écrit :
> >>>
> >>>> It works like a charm.
> >>>>
> >>>> Very last question: suggested ways to get nine up and running? Should
> I
> >>>> just get the code and install form there?
> >>>> I remeber reading a discussion about this, cant seem to find it.
> >>>>
> >>>> Francesco
> >>>>
> >>>> On Wed, Jan 28, 2015 at 12:19 PM, Pierre Tardy <tardyp at gmail.com>
> wrote:
> >>>>>
> >>>>> You can have a look at chrome developer tools (network tab) to see
> the
> >>>>> use of REST api.
> >>>>> The url you should use is:
> >>>>> http://nine.buildbot.net/api/v2/builders/1
> >>>>>
> >>>>> in
> >>>>> http://nine.buildbot.net/#/about
> >>>>> You have a formal description of all REST apis
> >>>>>
> >>>>> There are all straighforward mapping the internal 'data' api, which
> is
> >>>>> described here:
> >>>>> http://docs.buildbot.net/latest/developer/data.html
> >>>>>
> >>>>> HTH
> >>>>> Pierre
> >>>>>
> >>>>>
> >>>>> Le Wed Jan 28 2015 at 12:11:16 PM, Francesco Di Mizio
> >>>>> <francescodimizio at gmail.com> a écrit :
> >>>>>
> >>>>>> Hey Pierre,
> >>>>>>
> >>>>>> Thanks a lot for the kind reply.
> >>>>>>
> >>>>>> That's good news. I can probably do without those missing features.
> >>>>>>
> >>>>>> The part I am mostly interested in as I said above is
> >>>>>> http://docs.buildbot.net/latest/developer/www.html , in particual
> the rest
> >>>>>> api. I've given it a try with something simple against
> nine.buildbot.net.
> >>>>>> According to that page http://nine.buildbot.net/#/api/v2/builder/1
> >>>>>> should return me something meaningdul while I only get redirected
> to Home.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Jan 28, 2015 at 11:33 AM, Pierre Tardy <tardyp at gmail.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi Francesco,
> >>>>>>>
> >>>>>>> For me, master branch is really useable for small and medium use
> >>>>>>> cases.
> >>>>>>>
> >>>>>>> There are a few feature missing (rebuild, stop builds,
> authorization
> >>>>>>> framework, log compression),  that are preventing us to release a
> first
> >>>>>>> version. I would estimate something like 3-4 mm of work to finish
> this make
> >>>>>>> sure it is stable. The thing is that this project has no full time
> developer
> >>>>>>> working on it, so its hard to get an ETA.
> >>>>>>>
> >>>>>>> I would advise you to start your work on master branch, and if
> there
> >>>>>>> are bottlenecks, we can help you fix them or you can decide to
> switch back
> >>>>>>> to eight later.
> >>>>>>> There are very few change in configuration API between eight and
> >>>>>>> nine, so the work you do on nine can be reused on eight platform
> with very
> >>>>>>> few adjustments.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Le Wed Jan 28 2015 at 11:09:36 AM, Francesco Di Mizio
> >>>>>>> <francescodimizio at gmail.com> a écrit :
> >>>>>>>>
> >>>>>>>> I wouldn't mind using it and file issues. In this case I'd have to
> >>>>>>>> know an (even very imprecise) ETA  for 0.9 to be stable/released.
> >>>>>>>> What I am really looking forward to is the API that's coming with
> >>>>>>>> 0.9, it seems to be entirely missing on 0.8. Would this be a 0.9
> feature
> >>>>>>>> already functioning ok?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Sun, Jan 25, 2015 at 4:39 AM, Dustin J. Mitchell
> >>>>>>>> <dustin at v.igoro.us> wrote:
> >>>>>>>>>
> >>>>>>>>> There are a few folks out there using 'master' right now, but
> it's
> >>>>>>>>> still early days.  It's very helpful for us to get early
> feedback,
> >>>>>>>>> but
> >>>>>>>>> if you were to use it you'd definitely find yourself doing so :)
> >>>>>>>>>
> >>>>>>>>> Dustin
> >>>>>>>>>
> >>>>>>>>> On Wed, Jan 21, 2015 at 10:31 AM, Francesco Di Mizio
> >>>>>>>>> <francescodimizio at gmail.com> wrote:
> >>>>>>>>> > Thanks Dustin,
> >>>>>>>>> >
> >>>>>>>>> > that's what I thought too. I'll go the custom/scripting way.
> >>>>>>>>> >
> >>>>>>>>> > What about (copy and paste from above)
> >>>>>>>>> >
> >>>>>>>>> > Also I've been following http://nine.buildbot.net/#/ with
> >>>>>>>>> > interest. Since
> >>>>>>>>> > it's going to take a while to set all up, can it make sense for
> >>>>>>>>> > me to start
> >>>>>>>>> > off with 0.9 directly? Any idea as to when 0.9 might be out?
> >>>>>>>>> >
> >>>>>>>>> > Cheers,
> >>>>>>>>> >  Francesco
> >>>>>>>>> >
> >>>>>>>>> >
> >>>>>>>>> >
> >>>>>>>>> > On Mon, Jan 19, 2015 at 5:25 PM, Dustin J. Mitchell
> >>>>>>>>> > <dustin at v.igoro.us>
> >>>>>>>>> > wrote:
> >>>>>>>>> >>
> >>>>>>>>> >> Yes, at the moment the try schedulers have a fairly intricate
> >>>>>>>>> >> interface with Buildbot via Perspective Broker.  If you didn't
> >>>>>>>>> >> want to
> >>>>>>>>> >> install Buildbot, but were comfortable installing Twisted and
> >>>>>>>>> >> some
> >>>>>>>>> >> custom Python code, you could emulate `buildbot try` without
> too
> >>>>>>>>> >> much
> >>>>>>>>> >> difficulty.
> >>>>>>>>> >>
> >>>>>>>>> >> Dustin
> >>>>>>>>> >>
> >>>>>>>>> >> On Fri, Jan 16, 2015 at 9:20 AM, Francesco Di Mizio
> >>>>>>>>> >> <francescodimizio at gmail.com> wrote:
> >>>>>>>>> >> > Hello there,
> >>>>>>>>> >> >
> >>>>>>>>> >> > in the past at the company I was working for we used to
> have a
> >>>>>>>>> >> > buildbot
> >>>>>>>>> >> > based system mainly used for CL validation (making sure it
> >>>>>>>>> >> > compiles
> >>>>>>>>> >> > before
> >>>>>>>>> >> > checking it in).
> >>>>>>>>> >> >
> >>>>>>>>> >> > This was based on a minimalistic webpage that would in turn
> >>>>>>>>> >> > call some
> >>>>>>>>> >> > buildbot python api to a add a change to BB (it might have
> >>>>>>>>> >> > been
> >>>>>>>>> >> > addSourceStamp) so that it would show up on the left side of
> >>>>>>>>> >> > the
> >>>>>>>>> >> > waterfall.
> >>>>>>>>> >> > The schedulers being used were AnyBranchSchedulers. Without
> a
> >>>>>>>>> >> > successful
> >>>>>>>>> >> > 'test' a p4 trigger would prevent you from checking in.
> >>>>>>>>> >> >
> >>>>>>>>> >> > That approach can somehow be compared to
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/master/try_job_base.py
> >>>>>>>>> >> >
> >>>>>>>>> >> > I've then noticed that Buildbot comes with TrySchedulers. I
> am
> >>>>>>>>> >> > now in
> >>>>>>>>> >> > the
> >>>>>>>>> >> > middle of setting up something very similar to what I
> >>>>>>>>> >> > described above
> >>>>>>>>> >> > and
> >>>>>>>>> >> > was wondering if I can get away with it by using
> TrySchdulers.
> >>>>>>>>> >> >
> >>>>>>>>> >> > As far as I understand by reading the docs, a developer
> needs
> >>>>>>>>> >> > to run
> >>>>>>>>> >> > 'buildbot try', which I'd assume requires buildbot to be set
> >>>>>>>>> >> > up on their
> >>>>>>>>> >> > machine, which is a requirement I would like to avoid.
> Please
> >>>>>>>>> >> > correct me
> >>>>>>>>> >> > if
> >>>>>>>>> >> > I am wrong.
> >>>>>>>>> >> >
> >>>>>>>>> >> > Also I've been following http://nine.buildbot.net/#/ with
> >>>>>>>>> >> > interest.
> >>>>>>>>> >> > Since
> >>>>>>>>> >> > it's going to take a while to set all up, can it make sense
> >>>>>>>>> >> > for me to
> >>>>>>>>> >> > start
> >>>>>>>>> >> > off with 0.9 directly?
> >>>>>>>>> >> >
> >>>>>>>>> >> > Cheers,
> >>>>>>>>> >> >  Francesco
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> >>>>>>>>> >> >
> ------------------------------------------------------------------------------
> >>>>>>>>> >> > New Year. New Location. New Benefits. New Data Center in
> >>>>>>>>> >> > Ashburn, VA.
> >>>>>>>>> >> > GigeNET is offering a free month of service with a new
> server
> >>>>>>>>> >> > in
> >>>>>>>>> >> > Ashburn.
> >>>>>>>>> >> > Choose from 2 high performing configs, both with 100TB of
> >>>>>>>>> >> > bandwidth.
> >>>>>>>>> >> > Higher redundancy.Lower latency.Increased
> capacity.Completely
> >>>>>>>>> >> > compliant.
> >>>>>>>>> >> > http://p.sf.net/sfu/gigenet
> >>>>>>>>> >> > _______________________________________________
> >>>>>>>>> >> > Buildbot-devel mailing list
> >>>>>>>>> >> > Buildbot-devel at lists.sourceforge.net
> >>>>>>>>> >> > https://lists.sourceforge.net/lists/listinfo/buildbot-devel
> >>>>>>>>> >> >
> >>>>>>>>> >
> >>>>>>>>> >
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> ------------------------------------------------------------------------------
> >>>>>>>> Dive into the World of Parallel Programming. The Go Parallel
> >>>>>>>> Website,
> >>>>>>>> sponsored by Intel and developed in partnership with Slashdot
> Media,
> >>>>>>>> is your
> >>>>>>>> hub for all things parallel software development, from weekly
> >>>>>>>> thought
> >>>>>>>> leadership blogs to news, videos, case studies, tutorials and
> more.
> >>>>>>>> Take a
> >>>>>>>> look and join the conversation now.
> >>>>>>>>
> http://goparallel.sourceforge.net/_______________________________________________
> >>>>>>>> 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/20150207/2422a0ef/attachment.html>

More information about the devel mailing list