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

subprojects/stages/jobs #40

Closed
wiktorschmidt opened this issue Feb 1, 2011 · 4 comments
Closed

subprojects/stages/jobs #40

wiktorschmidt opened this issue Feb 1, 2011 · 4 comments

Comments

@wiktorschmidt
Copy link

Did you think about creating some kind of "subprojects/stages/jobs", however you call it. To support different stages/branches of the same projects instead of creating separate projects?

@wuputah
Copy link
Contributor

wuputah commented Feb 4, 2011

A project can already have multiple different builds - how would this be different?

I'll admit I'd like to add branch support (for different VCS branches), but it's not at the highest list of my personal priorities.

@wiktorschmidt
Copy link
Author

What I have in mind is having different STAGES (ex: test, staging, beta, production) on CI with separate tests that run one after another not concurrently like current builds. Hundson has something like this.

@wuputah
Copy link
Contributor

wuputah commented Feb 12, 2011

Well, if you want later steps to not run if earlier steps fail, add them as subsequent lines in a single build...

@antekpiechnik
Copy link
Member

I don't really understand this issue.

Branches can contain completely different code. You wouldn't want the whole project marked as failed if only one, insignificant, experimental branch has failed.

I also don't really understand the concurrency thing. Create separate build configs for those environments and fire them away ?

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

3 participants