Releasing by tag breaks the 'All tasks' dropdown

19 views
Skip to first unread message

Peter Farsinsen

unread,
Apr 1, 2011, 5:07:58 AM4/1/11
to webis...@googlegroups.com
Hi,

I'm trying to do releases by tag (inspired by this post https://groups.google.com/d/msg/webistrano/Ep-DkPuWP1I/u4YHWkZ-rQ4J), but when I add the 'tag' configuration option and set it to prompt, it breaks the 'All tasks' dropdown in the 'Deployment' box in the top right corner of the stage overview page. Rather than showing the list of all tasks the dropdown contains a single entry named 'Error'. Clicking 'Info' below the tasks dropdown throws this error: "Could not load tasks - syntax error in recipe definition?".

I've tried renaming 'tag' to 'svn_tag', 'release_tag' etc. which does not solve the problem, but unchecking the 'prompt' option seems to do the trick. I've been able to reproduce this on two different Webistrano installations (running 1.5).

Shouldn't it work? Any other way to achieve the same thing? I would greatly appreciate any advice on this matter.

Cheers,

Afam Agbodike

unread,
Apr 5, 2011, 2:35:31 PM4/5/11
to webis...@googlegroups.com
I don't remember exactly, but I believe I had a similar problem, try taking a look at this thread:

https://groups.google.com/d/topic/webistrano/_LqSXogujZo/discussion

I believe the solution was to change the line:
value = value.dup

to:
value = value.dup.to_s

in "lib/webistrano/deployer.rb"

This was almost a year ago, so my memory is pretty vague, and the code may have changed since then, so be careful.

Afam

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



--
Afam

Peter Farsinsen

unread,
Apr 9, 2011, 4:03:33 AM4/9/11
to webis...@googlegroups.com
Hi Afam,

Thanks for helping out.

Your solution didn't fix the problem, but after reading the post you linked to I ended up comparing the source of the latest release (1.5) and what's in the master branch. They are not identical (the issue has been patched in master), so I ended up doing a checkout of master rather than using the zipped package which seems to be working.

Thanks for pointing me in the right direction.

- Peter
Reply all
Reply to author
Forward
0 new messages