Edgewall group on GitHub

[RjOllos]

I'm looking at some services that we might be able to use to provide CI for the Trac project; currently evaluating drone.io which can run builds off the mirror on GitHub. I was wondering if someone could add me to the Edgewall group on GitHub so that I can point drone.io directly at the mirror. So far I've just pointed it to my fork of Trac on GitHub, which I don't normally use and so it's out of date unless I make the effort to push the latest changes. My GitHub username is rjollos.

I'm not done much that is too interesting yet regarding drone.io, but I'll post more later after spending some more time on it:
https://drone.io/github.com/rjollos/trac/6

Thanks!

[Jonas Borgström]

Cool, I just added you to the Edgewall account, let me know if it works.

Btw, any plans to evaluate Travis CI?

/ Jonas

[Ryan Ollos]

Thanks. I see the edgewall repositories in my list of accounts now, but I get an error when I try to select the repository to setup a build configuration:

It looks like I would need to be an administrator of the repository to setup a build:
http://docs.drone.io/newproject.html

Yeah, I plan to look at Travis CI as well. It appears drone.io has a Python 2.7 interpreter, but no other 2.x series interpretters (as well as 3.2 and 3.3); whereas we need to run the tests for 0.12-stable and 1.0-stable on Python 2.5-2.7, and 2.6-2.7 for the trunk.

For code coverage, I came across this one in a blog article today: https://coveralls.io/

[RjOllos]

On Monday, June 9, 2014 2:27:00 PM UTC-7, RjOllos wrote:

... whereas we need to run the tests for 0.12-stable and 1.0-stable on Python 2.5-2.7, and 2.6-2.7 for the trunk.

I keep forgetting that Trac 0.12 supports Python 2.4, so I should have said Python 2.4-2.7 for 0.12-stable.

[Jonas Borgström]

On 2014-06-09 23:26, Ryan Ollos wrote:
> On Mon, Jun 9, 2014 at 1:31 PM, Jonas Borgström <jo...@borgstrom.se
> <mailto:jo...@borgstrom.se>> wrote:
>
> On 2014-06-07 10:38, RjOllos wrote:
> > I'm looking at some services that we might be able to use to
> provide CI
> > for the Trac project; currently evaluating drone.io

> <http://drone.io> which can run builds

> > off the mirror on GitHub. I was wondering if someone could add me
> to the
> > Edgewall group on GitHub so that I can point drone.io

> <http://drone.io> directly at the

> > mirror. So far I've just pointed it to my fork of Trac on GitHub,
> which
> > I don't normally use and so it's out of date unless I make the
> effort to
> > push the latest changes. My GitHub username is rjollos.
> >
> > I'm not done much that is too interesting yet regarding drone.io

> <http://drone.io>, but

> > I'll post more later after spending some more time on it:
> > https://drone.io/github.com/rjollos/trac/6
>
> Cool, I just added you to the Edgewall account, let me know if it works.
>
> Btw, any plans to evaluate Travis CI?
>
> / Jonas
>
>
> Thanks. I see the edgewall repositories in my list of accounts now, but
> I get an error when I try to select the repository to setup a build
> configuration:
>

> Inline image 1
>
> It looks like I would need to be an administrator of the repository to
> setup a build:
> http://docs.drone.io/newproject.html

Ah right, that's a separate step. I've now added you as an administrator
to the Trac and Genshi repositories.

> Yeah, I plan to look at Travis CI as well. It appears drone.io

> <http://drone.io> has a Python 2.7 interpreter, but no other 2.x series

> interpretters (as well as 3.2 and 3.3); whereas we need to run the tests
> for 0.12-stable and 1.0-stable on Python 2.5-2.7, and 2.6-2.7 for the trunk.
>
> For code coverage, I came across this one in a blog article today:
> https://coveralls.io/

Cool, that looks interesting.

/ Jonas

[Ryan Ollos]

Thanks, it seems to be working great now.

I pushed a little change: http://trac.edgewall.org/changeset/12853

Immediately the build kicked off: https://drone.io/github.com/edgewall/trac/3

I'll try to sort out why the Twill tests aren't running, and then follow-up with a more thorough review of drone.io and whether it meets our needs.

[Jun Omae]

Hi,

On Wed, Jun 11, 2014 at 7:36 AM, Ryan Ollos <rjo...@gmail.com> wrote:
> Immediately the build kicked off:
> https://drone.io/github.com/edgewall/trac/3
>
> I'll try to sort out why the Twill tests aren't running, and then follow-up
> with a more thorough review of drone.io and whether it meets our needs.

I've got the same issue. Recently, twill 1.8.0 is released. The tests
don't work with the version of twill. Instead, works well with twill
0.9.1.

https://pypi.python.org/pypi/twill
https://drone.io/github.com/jun66j5/trac/admin


--
Jun Omae <jun...@gmail.com> (大前 潤)

[Ryan Ollos]

Thanks. Nice that there is some movement on maintaining that package, at least in theory.

It appears that current development is happening in the author's GitHub repository.
https://github.com/ctb

I don't see much in terms of a changelog, so we might be left reviewing changes from the repository:
https://github.com/ctb/twill/blob/master/doc/ChangeLog

[RjOllos]

Jun, I added you as an admin on my drone.io project so that we can work together on evaluating the build script if you want. I already grabbed your latest build script, which was much more complete than mine, and added it to the project.

[Jun Omae]

Thanks, Ryan.

I've tried to add postgres and mysql to the build, but I got "Maximum
build time exceeded" error.
https://drone.io/github.com/jun66j5/trac/13.

A build cannot exceed 15 minutes on free tier, according to "Limits"
section in http://docs.drone.io/buildscript.html.

[RjOllos]

I suppose we could contact them and ask if they are willing to loosen the restrictions for an open source project. Given the limited Python versions though, I'm hoping we can find a better solution. I might write-up our findings as a blog post since it would be a useful way to give them feedback and maybe get some input from other open source projects. I recall first reading about drone.io in a blog post by Anatoly. Let's also see what TravisCI can do.

Another solution would be to just setup buildbot, jenkins or similar on the edgewall server. We could run the slaves on the server if there is enough resources, and also allow users that want to contribute slaves to run the build on various platforms.

Even with the limited amount of testing that is being run at the moment, it is really nice and provides confidence to get the "Build Succeeded" notices by email. It should at least catch the worst errors, such as forgetting to commit a newly added file.

[Jun Omae]

Hi,

On Thu, Jul 3, 2014 at 3:18 AM, RjOllos <rjo...@gmail.com> wrote:
> I suppose we could contact them and ask if they are willing to loosen the
> restrictions for an open source project. Given the limited Python versions
> though, I'm hoping we can find a better solution. I might write-up our
> findings as a blog post since it would be a useful way to give them feedback
> and maybe get some input from other open source projects. I recall first
> reading about drone.io in a blog post by Anatoly. Let's also see what
> TravisCI can do.

I just tried travis-ci. Matrix build works well under the following.

Python:
- 2.6 (without subversion binding)
- 2.7
Database:
- SQLite on-memory
- SQLite file
- PostgreSQL
- MySQL

https://travis-ci.org/jun66j5/trac/builds/29040035
https://github.com/jun66j5/trac/blob/travis_0.12/.travis.yml

[Jun Omae]

On Thu, Jul 3, 2014 at 6:49 PM, Jun Omae <jun...@gmail.com> wrote:
> I just tried travis-ci. Matrix build works well under the following.

> ...
> https://travis-ci.org/jun66j5/trac/builds/29040035
> https://github.com/jun66j5/trac/blob/travis_0.12/.travis.yml

I just noticed that the mirror repository on github has enabled
travis-ci testing by someone. See
https://travis-ci.org/edgewall/trac/builds

We could start testing on travis-ci once we add .travis.yml to each
branch in subversion repository.

[Ryan Ollos]

 That sounds great. I vote for adding the .travis.yml since there is no harm and we can always delete it later.

[Peter Suter]

Sounds cool.

Would it make sense to document / link to this service somewhere on the
wiki? Is this similar to the previous Automatic builds [1] and/or Python
Community Buildbot [2]? (Neither seems to be available anymore. Perhaps
their description should be removed instead.)


Cheers,
Peter

[1] http://trac.edgewall.org/wiki/TracDev/UnitTests#Buildbots
[2] http://trac.edgewall.org/wiki/TracDev/AutomaticBuilds

[Ryan Ollos]

Those look like the right places to document the Travis CI service. It might be good to just remove the section in [1] and add a link from there to [2], updating [2] with new information about Travis CI. I'll plan to update those eventually if you don't beat me to it.

It could be nice to have a dedicated mailing list for build notifications. Looking at the current mailing lists [3], the Trac Tickets list is probably too verbose for many people that would be interested in knowing about failing builds. Maybe we could have a trac-...@edgewall.org?

[3] http://trac.edgewall.org/wiki/MailingList

[Peter Suter]

On 29.07.2014 06:17, Ryan Ollos wrote:

[1] http://trac.edgewall.org/wiki/TracDev/UnitTests#Buildbots
[2] http://trac.edgewall.org/wiki/TracDev/AutomaticBuilds

Those look like the right places to document the Travis CI service. It might be good to just remove the section in [1] and add a link from there to [2], updating [2] with new information about Travis CI. I'll plan to update those eventually if you don't beat me to it.

OK, I replaced the seemingly obsolete information by a link from [1] to [2] and some links to Travis CI and .travis.yml. Please amend or restore as you see fit.

It could be nice to have a dedicated mailing list for build notifications. Looking at the current mailing lists [3], the Trac Tickets list is probably too verbose for many people that would be interested in knowing about failing builds. Maybe we could have a trac-...@edgewall.org?

[3] http://trac.edgewall.org/wiki/MailingList

Alternatively it seems there's an Atom feed [4] but it also includes all successful builds.

[4] https://api.travis-ci.org/repos/edgewall/trac/builds.atom

[RjOllos]

Jun, do you think there is any value in keeping drone.io build notifications now that we have Travis CI? Do you want to continue receiving the build notifications?

[Jun Omae]

Nothing. I just disabled the build on https://drone.io/github.com/edgewall/trac.

[Jun Omae]

On Tue, Jul 29, 2014 at 1:17 PM, Ryan Ollos <rjo...@gmail.com> wrote:
> It could be nice to have a dedicated mailing list for build notifications.
> Looking at the current mailing lists [3], the Trac Tickets list is probably
> too verbose for many people that would be interested in knowing about
> failing builds. Maybe we could have a trac-...@edgewall.org?
>
> [3] http://trac.edgewall.org/wiki/MailingList

+1. However, edgewall.org server doesn't seem to provide mailing
lists. Instead, we could create trac-...@googlegroups.com?

[RjOllos]

Yeah, that sounds like a good idea.