Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split project and build configurations #11

Closed
koraktor opened this issue Dec 4, 2010 · 5 comments
Closed

Split project and build configurations #11

koraktor opened this issue Dec 4, 2010 · 5 comments

Comments

@koraktor
Copy link

koraktor commented Dec 4, 2010

Right now, each project can only have one build configuration. If you want to run several projects and/or branches with several configurations (e.g. using RVM), you have to create a project for each configuration.
This is tedious and you'll pretty soon loose track of your projects' status if you have lots of projects or configurations.

This is the current version: http://yfrog.com/3ubigtuna1p

And this is how I imagine configuration support: http://yfrog.com/5fbigtuna2p

@michalbugno
Copy link
Member

How do such configuration differ from each other? Are there some additional tasks which involve for example changing env by RVM?

Also, this is somehow similar to 'grouping' various projects together into one meta--project, isn't it?

We'd like to hear your answers so that we know what needs to be changed.

@koraktor
Copy link
Author

koraktor commented Dec 6, 2010

In fact – at least for my simple setup right now – I'm just calling rvm 1.9.2 rake test, rvm jruby-1.5.3 rake test etc. on one single project: Testing the same code on different interpreters. So basic project configuration (like VCS) is the same for all different setups.
This is something like TeamCity's build configurations.

My case is pretty basic, others may use more complex configurations, but I think it's a must-have for a CI server, to allow different configurations on a project.

@michalbugno
Copy link
Member

Multiple configurations are available on development branch. Database schema has changed and it should be recreated with rake db:schema:load (note that all your project data will be gone)

@koraktor
Copy link
Author

koraktor commented Dec 7, 2010

Looks like a good start. Thanks!

@michalbugno
Copy link
Member

I'm closing the ticket, we'll open new if anything pops up.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants