Which Orchard source code branch?

Topics: General
Apr 1, 2011 at 12:57 PM

I remember seeing somewhere, but can't seem to find it now, that the naming conventions for the branches in the source code repository changed at one point.

Would someone be willing to post a link to the naming conventions for the various branches?

Also which branch represents the latest branch that has passed all the automated unit and integration tests?

Coordinator
Apr 1, 2011 at 7:06 PM

http://orchardproject.net/docs/Setting-up-a-source-enlistment.ashx?HL=branches#Branches_9

Coordinator
Apr 1, 2011 at 7:07 PM

For test status, you could check on the CI server: http://orchardproject.net:8080

Apr 1, 2011 at 10:43 PM
bertrandleroy wrote:

For test status, you could check on the CI server: http://orchardproject.net:8080

Thanks Bertrand, that is helpful. Obviously no point in entering something into the issue tracker that is already statused as breaking the build ;-)

Is the a writeup somewhere or could you tell me a little more about how the Orchard team is using TeamCity? Also have you integrated the Codeplex issue tracker with TeamCity?

Thanks.

Coordinator
Apr 1, 2011 at 10:45 PM

No issue tracker integration, no. I explained the setup here: http://weblogs.asp.net/bleroy/archive/2010/02/26/setting-up-a-continuous-integration-server-for-a-codeplex-project-using-teamcity-and-mercurial.aspx

Apr 2, 2011 at 12:48 AM
bertrandleroy wrote:

No issue tracker integration, no. I explained the setup here: http://weblogs.asp.net/bleroy/archive/2010/02/26/setting-up-a-continuous-integration-server-for-a-codeplex-project-using-teamcity-and-mercurial.aspx

 

Thank you, great blog post!

"For example, we’re working on getting it to generate release packages automatically so that each and every build is ready to be released."

How did that work out?

Coordinator
Apr 2, 2011 at 4:20 AM

Very well, that's how we generate the CodePlex releases, and you can actually go into the artefact drop-down for any release on TeamCity and get the packages. I think only the Azure packages still have to be done manually. Nothing impossible, just never got to it.