I'm testing out Bamboo, putting together a rails project similar to this blog article: http://blogs.atlassian.com/2012/06/building-ruby-projects-with-bundler-and-the-bamboo-ruby-plugin/
The issue I think is that our git project does not have the rails project at the root. Our git repo is laid out so that the rails app is in a subfolder, because we have other non-rails files at the root also. I think this is causing issues like, bundler not finding the gemfile, etc. (which makes sense because you couldn't run these commands from a folder above the rails folder in command line.
How can I do this without changing my repo? I was thinking that maybe I could issue a cd command as a task, but no dice I'm afraid. And I don't see how I can set a working folder for bundle or rake?
As the author of the Ruby Plugin for bamboo I had never considered this problem, that said I can most certainly assist in resolving it.
As each of the "tasks" spawns independent processes I will just need to configure this for all tasks within the build.
I have added an issue on my project to solve it https://github.com/wolfeidau/rake-bamboo-plugin/issues/29
Thanks for taking the time to post this question!
Update:
This morning I shipped an updated version with this feature added.
https://marketplace.atlassian.com/plugins/au.id.wolfe.bamboo.rake-bamboo-plugin/version/48
Screen shots illustrate the case where a project in bitbucket has a rails project directory nested within it which needs to be tested (see example project below).
https://bitbucket.org/wolfeidau/zooper/src
If you have any issues I am happy to help.
Shoot! I thought I picked the right one. No its about the downloaded version. My bad.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dave, is this really an OnDemand question?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.