Yes, it's a few days that it's broken due to Crank, we need a way to handle the insertion of new dependencies inside the project during the development process. Not having it makes a bit useless Jenkins itself as you are not able to know if things are broken for real as they always result being broken due to missing/wrong dependencies.
On Fri, Feb 10, 2012 at 11:37 AM, Christoph Zwerschke <c...@online.de> wrote: > The TG 2.1 tests on the Jenkins server are currently failing and Chuck > Norris really does not like it. It looks like this is caused by the fact > that we now use Crank which is missing in the current index. This also > reveals an issue with the test setup in general. The Jenkins script is > installing the dependencies from http://tg.tgy/current/index/. To do it > properly we should add another directory /next/ parallel to /current/ on the > TG server. In the beginning, /next/ should be a copy of /current/. When we > update or add to our requirements, the packages in /next/ should be adapted, > e.g. put Crank in here or a newer version of WebOb. The tests setup should > then install from /next/ and at the time we create a new release we already > have our packages ready and just need to rename /next/ to /current/. > > -- Christoph > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
