|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
From our point of view in continous process it's can be life, since there can be exists some issues due which tests are failed (bug or bugs about which we are know) and QA should get build with some limitation.(Since another features are working and QA should test it)
To fix these issues need some time e.g. 2-4 days. As I said before QA should get build during this 2-4 days.
We are using tagging to have stable(or unstable) build (but not failed). Continous build marks in source control tag e.g. "stable" and nighly build use this tag to have "good" build.