Deployments broken with 2.5.11

[Josh Perfetto]

Hi,

Just upgraded to 2.5.11 and it seems a few things broke with
deployments. deploy:migrate now attempts to execute the migration in
the oldest release directory (rather than the newest), and
deploy:cleanup deletes all but the oldest 5 directories, basically the
opposite of what you want. It all works fine in 2.5.10. This is on
Ubuntu 9.10.

-Josh

[Lee Hambley]

Josh,

Thanks for the report, we have a number of problems in this area in the latest release. Are you using customised release names, or the default timestamped ones?

-- Lee Hambley

Twitter: @leehambley | @capistranorb
Blog: http://lee.hambley.name/
Working with Rails: http://is.gd/1s5W1

2010/1/3 Josh Perfetto <jo...@snowrise.com>

--
* You received this message because you are subscribed to the Google Groups "Capistrano" group.
* To post to this group, send email to capis...@googlegroups.com
* To unsubscribe from this group, send email to capistrano+...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en

[Ryan Waldron]

I've got the same problem here (deploying from MacOSX 10.5 to a Fedora Core 5 (yes, that old) box).  I'm using the default timestamped release directory names.  'ls -xt' works properly on FC5, and 'ls -x' reverses the order (giving oldest first instead of newest first).

Just FYI.

--

[Kyle Bragger]

Not sure if this is related or not:
http://timothynjones.wordpress.com/2010/01/04/fatal-bug-in-capistrano-2-5-11/

> > capistrano+...@googlegroups.com<capistrano%2Bunsubscribe@googlegrou ps.com>For more options, visit this group at
> >http://groups.google.com/group/capistrano?hl=en

[Josh Perfetto]

Hi Lee,

I am using the default timestamped ones,

-Josh

On Jan 4, 3:39 am, Lee Hambley <lee.hamb...@gmail.com> wrote:
> Josh,
>
> Thanks for the report, we have a number of problems in this area in the
> latest release. Are you using customised release names, or the default
> timestamped ones?
>
> -- Lee Hambley
>
> Twitter: @leehambley | @capistranorb
> Blog:http://lee.hambley.name/
> Working with Rails:http://is.gd/1s5W1
>

> 2010/1/3 Josh Perfetto <j...@snowrise.com>

>
> > Hi,
>
> > Just upgraded to 2.5.11 and it seems a few things broke with
> > deployments. deploy:migrate now attempts to execute the migration in
> > the oldest release directory (rather than the newest), and
> > deploy:cleanup deletes all but the oldest 5 directories, basically the
> > opposite of what you want. It all works fine in 2.5.10. This is on
> > Ubuntu 9.10.
>
> > -Josh
>
> > --
> > * You received this message because you are subscribed to the Google Groups
> > "Capistrano" group.
> > * To post to this group, send email to capis...@googlegroups.com
> > * To unsubscribe from this group, send email to

> > capistrano+...@googlegroups.com<capistrano%2Bunsu...@googlegroups.com>For more options, visit this group at
> >http://groups.google.com/group/capistrano?hl=en
>
>

[Florian Munz]

Hi,

I'm having the same issues.

- deploy:migrate executes migrations not in the release_directory
- deploy:cleanup deletes the newest release, not the oldest one

Cheers,
Florian

[Rafael G.]

I had the same problem. We will fix it shortly, I'll try to coordinate
with Lee.

Sorry for the inconvenience, regards

--
Rafa

[Rafael G.]

Hi again,

I arrived late. There's a fix about it and will be in next release.
While you can try a provisional fix proposed by Christopher Rigor:

"
Until this gets fixed, you can add this to deploy.rb
set :releases, lambda { capture("ls -x
#{releases_path}").split.sort }
"

Read:
https://capistrano.lighthouseapp.com/projects/8716/tickets/88-getting-the-newest-directory

--
Rafa

[Lee Hambley]

Is it indeed related, new version on the way to gemcutter now.

[Timothy Jones]

This is an extremely serious bug -- a patch release needs to be issued
*immediately*.

Tim Jones
Barbary Codes and Data
www.barbarycodes.com

[Lee Hambley]

This hit gemcutter about 20 minutes ago.

[Lee Hambley]

For the record, there's no (yes, really NO) tests for this part of the code, because it's environmentally dependent – I'd love some help with this if anyone has any thoughts / can contribute.