+1 for staying with Travis. The reason could maybe be the same as for moving the repositories to Github: Because everybody's there now, e.g. to stay at the pulse of the time. It (maybe) increases visibility of the TG project a little, it's better integrated with Github etc. pp. And as with rtfd, it increases the chance that some other folks put a hand on it, since they are more common services...
Am Freitag, 19. April 2013 10:22:52 UTC+2 schrieb [email protected]: > > Talking with Michael yesterday, he has been quite harsh about the fact we > have duplicated docs on rtfd.org and duplicated continuous integration on > travis.ci. The situation ended so because the existing solutions were > broken at the time (doc built wrong version and jenkins didn't work at all) > and I tried to provide a quick fix to them by moving them to cloud > services. That actually lead to having duplicate docs and duplicated > continuous integration. > > The travis based CI is currently working quite well, we have both stable > and development branches CI and it provided builds and issues reporting on > both Py2.x and Py3.x thanks to the fact that we now have a decent test > suite. > > So my point is that I would like to officially dismiss > jenkins.turbogears.org and make travis our official CI platform. Does > anybody see any issue in such a move? > > If we want to keep on jenkins we must fix it as all builds since months > are failing and provide at least testing on Py3.2 and Py3.3 too. > > References: > http://jenkins.turbogears.org/view/TurboGears%20Hosted/ > https://travis-ci.org/TurboGears/tg2 > -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
