ok, I don't know if this is intended behavior or not, but here's what
I ran this time and I got the correct output:
before("deploy:migrate") {
warn "Release Was: #{releases.inspect}"
reset! :releases
reset! :current_release
reset! :previous_release
warn "Release Now: #{releases.inspect}"
}
Release Was: ["20100215025835", "20100215211937", "20100215213658",
"20100215214424", "20100215232317"]
Release Now: ["20100215025835", "20100215211937", "20100215213658",
"20100215214424", "20100215232317", "20100216003359"]
latest => /path/to/my/app/releases/20100216003359
* executing "cd /path/to/my/app/releases/20100216003359; rake
RAILS_ENV=production db:migrate"
So it looks like current_release and previous_release were cached as
well and needed a reset! before they'd re-query too?
On Feb 15, 6:27 pm, jmadtech <[email protected]> wrote:
> Good idea!
>
> So... now it makes even less sense (to me anyway):
>
> Release Was: ["20100215025740", "20100215025835", "20100215211937",
> "20100215213658", "20100215214424"]
> Release Now: ["20100215025740", "20100215025835", "20100215211937",
> "20100215213658", "20100215214424", "20100215232317"]
> latest => /path/to/my/app/releases/20100215214424
> * executing "cd /path/to/my/app/releases/20100215214424; rake
> RAILS_ENV=production db:migrate"
>
> On Feb 15, 5:43 pm, Lee Hambley <[email protected]> wrote:
>
> > I'd try:
>
> > before("deploy:migrate") {
> > warn "Release Was: #{releases.inspect}"
> > reset! :releases
> > warn "Release Now:: #{releases.inspect}"
>
> > }
>
> > Just to make sure that it's having an effect.. ( I can't see anything
> > obvious going amis here :\ )
>
> > -- Lee Hambley
>
> > Twitter: @leehambley | @capistranorb
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
