[devel at bb.net] Review of "Expert Twisted" chapter

[Dustin J. Mitchell]

On http://buildbot.net, we have "Buildbot is an open-source framework for
automating software build, test, and release processes."

So, removing "open source" since that's not especially relevant in the book:

  Buildbot is an framework for automating software build, test, and release
processes.

Short, avoids "CI" entirely, matches our marketing copy, .. any objections?

Dustin

2017-12-18 21:50 GMT-05:00 Dustin J. Mitchell <dustin at v.igoro.us>:

> Thanks for the feedback, I'm now convinced that I'm mis-using "CI" :)
>
> However, the suggested sentence doesn't really "snap".  It sounds like
> "Buildbot's useful for doing some of the things relating to this thing".
> Thoughts on a tighter phrase?
>
> Dustin
>
> 2017-12-18 10:45 GMT-05:00 Neil Gilmore <ngilmore at grammatech.com>:
>
>> Hi everyone,
>>
>> On 12/16/2017 3:45 PM, Dustin J. Mitchell wrote:
>>
>> 2017-12-12 7:06 GMT-05:00 Vit Ry <frodox at zoho.com>:
>>
>>> Hi! According to PR12 build (https://31-103838017-gh.circl
>>> e-artifacts.com/0/root/repo/out/10-Buildbot.pdf)
>>>
>>> > Buildbot is a framework for building continuous integration
>>> applications.
>>>
>>> I'm confusing with this every time. What is "CI application" ? CI - is a
>>> process, a culture...
>>> I don't hear often 'CI application' term, and what is the meaning then?
>>>
>>
>> A CI application is an application that implements a continuous
>> integration process.  I'm trying to make the point here that if you're
>> going to use Buildbot, you're going to have to implement what you want
>> (your application) *on top* of Buildbot (a framework).  Do you have a
>> better term?
>>
>>
>> That first sentence is a bit tautological, isn't it? I understand what
>> you're trying to get at -- buildbot is a framework, not an application
>> itself. But someone unfamiliar with the term may head off to Wikipedia,
>> which seems to have a very different definition that you seem to from that
>> definition:
>>
>> https://en.wikipedia.org/wiki/Continuous_integration
>>
>> In software engineering
>> <https://en.wikipedia.org/wiki/Software_engineering>, *continuous
>> integration* (*CI*) is the practice of merging all developer working
>> copies to a shared mainline
>> <https://en.wikipedia.org/wiki/Trunk_%28software%29> several times a day.
>>
>> That, combined with your explanation of buildbot, would seem to say that
>> buildbot does merges, which really isn't the case. It does its work after
>> the merges are done.
>>
>> Maybe a better way to say it might be:
>>
>> "Buildbot is a framework that that aids developers in maintaining some of
>> the best practices of Continuous Integration, such as automating builds,
>> tests and deployments."
>>
>> Neil Gilmore
>> raito at raito.com
>>
>> _______________________________________________
>> devel mailing list
>> devel at buildbot.net
>> https://lists.buildbot.net/mailman/listinfo/devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20171222/6a0e541d/attachment.html>