Our project had a nice hack (although I\'m guessing there are better ways to do it) to embed revision information into the artifacts (jar etc.) when we used svn.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accep开发者_高级运维ting answers.
Our system comprises many .NET websites, class libraries, and a MSSQL database. We use SVN for source control and TeamCity to automatically build to a Test server.
I want to throw this scenario out there and see what the most objective, vanilla-Mercurial way to fix this would be.
Closed. This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing
Tipically a deploy in production does not involve just a mere source code update (build) but requires a lot of other important tasks like, for example:
When using the maven-release-plugin with Git, mvn release:prepare happily tags the release in the local repository.I\'d expect mvn release:perform to push the tags to the remote repository, but this d
I look after the merging, deployment and release of Products & Services in the Company I work for. I\'ve slowly moved to this position from development so a lot of this is new to me (I guess!)
Our group is currently analysing our procedures for managing formal software releases and integrating with a bug lifecycle.
The process of creating a new build and releasing it to production is a critical step in the SDLC but it is often left as an afterthought and varies greatly from one company to the next.
加载中,请稍侯......