[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Integration Builds and Tags

From: Stephen McConnell <mcconnell_stephen_at_yahoo.com>
Date: 2005-01-13 19:13:56 CET

Brad, thanks for the article.

The problem is even more complex than I stated.

We have started with a base codeline. As developers "fix" bugs in the
trouble tickets or add functionality to the codeline... those fixes
need to be promoted to a "Test" environment. So, I need some way to
differentiate between the code that will move to the "Test"
environment. Only those classes that are involved in the change need
to be moved to the "Test" environment.

BUT, here's the catcher.... We have multiple clients. Once our
testers test the "fix", it needs to be moved to a Client QA test. And
they ONLY want those fixes applicable to them (unless one fix affects
all the clients).

I need to move certain code bunches to a Client Test Integration Build.

Now, If I use the "properties" idea, then each revision of a file can
have only one "state" as defined by the "INTEGRATION-LEVEL" property.

AND A FURTHER KICKER... For the Production Level, the client only
wants those classes to be included that they have tested to be moved
the "THEIR" production level.

We are using "subclipse" inside of Eclipse to develop on the "trunk".

I receive an email with a description of the code the developer wants
to "Promote" to Test. I need to promote it, do a build and move an
"EAR" file out to the test server for our test team to test. Once it's
tested by our testers, I need to move that code the the client test

Then, once the client has tested it, I need to move that code to the
client production..... for each individual client.

I believe this is getting too complex; and I need to have a talk with
this company....


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 13 19:16:50 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.