[Twisted-Python] (no subject)
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
As commented by @glyph Since we've added the buildbot link to trac pages, force-builds.py is basically obsolete. I think we should just scrub all mentions of it, and probably delete it. I have created a ticket to remove it and clean documentation: https://github.com/twisted/twisted-dev-tools/issues/5 Is there anyone else still using this tool? Should we keep it and rather than removing it, improve its documentation? Thanks! -- Adi Roiban
![](https://secure.gravatar.com/avatar/607cfd4a5b41fe6c886c978128b9c03e.jpg?s=120&d=mm&r=g)
On 18 Nov, 06:40 pm, adi@roiban.ro wrote:
Given that it already exists, I'm not sure it makes much sense to delete it. Perhaps some folks prefer a workflow that is command-line oriented rather than web-browser based. I don't really feel very strongly about it, though. Jean-Paul
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
I guess we should do two things, really: 1. remove it from the onboarding documentation so there are fewer choices / things to learn when getting started 2. *add it* to some documentation for itself, so that people know how to use it. While in its current state it isn't really useful to me, I would _love_ to be able to use this to spin off some tests ... if I could then view their output on the command line as well, and not just have to hit a browser immediately anyway :). -glyph
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
On 19 November 2014 at 20:20, Glyph <glyph@twistedmatrix.com> wrote:
Here are my improvements: https://github.com/twisted/twisted-dev-tools/pull/8 Please, please merge https://github.com/twisted/twisted-dev-tools/pull/4 or https://github.com/twisted/twisted-dev-tools/pull/7 ---------- I also wanted to update the tools to show status in command line and run a specific test/tests just like you would run trial on local system (without -b) ... but for next ticket. For my project I have a similar tool which just runs a background thread and pipes the output of last builbot web status log into the console. It is ok for test which take a few second, but for test that take 40minutes I found email notifications much useful. Cheers -- Adi Roiban
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
I've merged 4.
That would be amazing; thank you.
I've wanted this for years :-D.
It is ok for test which take a few second, but for test that take 40minutes I found email notifications much useful.
Can you have the command line tool request those as well? -g
![](https://secure.gravatar.com/avatar/607cfd4a5b41fe6c886c978128b9c03e.jpg?s=120&d=mm&r=g)
On 18 Nov, 06:40 pm, adi@roiban.ro wrote:
Given that it already exists, I'm not sure it makes much sense to delete it. Perhaps some folks prefer a workflow that is command-line oriented rather than web-browser based. I don't really feel very strongly about it, though. Jean-Paul
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
I guess we should do two things, really: 1. remove it from the onboarding documentation so there are fewer choices / things to learn when getting started 2. *add it* to some documentation for itself, so that people know how to use it. While in its current state it isn't really useful to me, I would _love_ to be able to use this to spin off some tests ... if I could then view their output on the command line as well, and not just have to hit a browser immediately anyway :). -glyph
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
On 19 November 2014 at 20:20, Glyph <glyph@twistedmatrix.com> wrote:
Here are my improvements: https://github.com/twisted/twisted-dev-tools/pull/8 Please, please merge https://github.com/twisted/twisted-dev-tools/pull/4 or https://github.com/twisted/twisted-dev-tools/pull/7 ---------- I also wanted to update the tools to show status in command line and run a specific test/tests just like you would run trial on local system (without -b) ... but for next ticket. For my project I have a similar tool which just runs a background thread and pipes the output of last builbot web status log into the console. It is ok for test which take a few second, but for test that take 40minutes I found email notifications much useful. Cheers -- Adi Roiban
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
I've merged 4.
That would be amazing; thank you.
I've wanted this for years :-D.
It is ok for test which take a few second, but for test that take 40minutes I found email notifications much useful.
Can you have the command line tool request those as well? -g
participants (3)
-
Adi Roiban
-
exarkun@twistedmatrix.com
-
Glyph