First build questions -- Why delete the build workspace? Why build as the builder?
CLM 4.0.5
For some reason....our previous person deleted the build workspace after each build? I don't remember reading about it anywhere. This group, unlike our others, also had the release guy log in to the build machine and accept all changes as the builder and do a build... Is there any value to recreating the workspace? Or even deleting it? Is there any value to logging in the build machine as the builder and accepting changes and doing the build manually? |
Accepted answer
How much do you trust that your "clean" targets actually restore a pristine state? If you don't trust them then it makes sense to blow away the sandbox & reload each time. I've worked in groups where we also rebooted the build engine before every build. It just depends on how paranoid you are. For example, I'd be much less inclined to trust that an Ant-based build's "clean" target actually restores a pristine state, compared to a Maven build.
If you want to cherry-pick changes, instead of just accepting all, I don't know of a built in way in RTC to do that (other than the manual approach you describe).
Mahari Hill selected this answer as the correct answer
Comments This wiki entry: https://jazz.net/wiki/bin/view/Deployment/RTCSlowBuilds discusses incremental v. clean builds and discusses the pros and cons of both approaches.
A true incremental build is the holy grail...IMO though for Java-based products it's just not worth the effort unless your project is trivially small (in which case the time benefit probably is minimal). Thanks for the answers, I have found that they were A) doing a personal build B) using ant script to copy "out of the build" directory somewhere else, and then doing a build...which seems pointless.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.