Artifact storage

I realize what I'm about to ask is subjective, but I want to get
feedback from anyone who cares to pile-on.

Is the intent of TeamCity to be the Authoritative Source (DRY) for build
artifacts? If so, are the artifacts stored then on the server (vs. the
agents) - and this location would presumably need to be backed up.

Is this how some of you use TeamCity - or when you have a public release
of a build, do you move it off for safe-keeping elsewhere?


--
Chris

3 comments

Chris Morris wrote:

Is the intent of TeamCity to be the Authoritative Source (DRY) for build
artifacts? If so, are the artifacts stored then on the server (vs. the
agents) - and this location would presumably need to be backed up.


And a follow-up question -- can TeamCity be configured to allow me to
choose another server/path for artifact storage? Before going to
TeamCity, our home-rolled build process moved the artifacts to a
production network file server which has backups on it.


--
Chris

0

Chris,

Speaking of our internal JetBrains TeamCity installation:
We trust TeamCity to store all important (pinned) builds on the server, while we do also backup the most important ones (such as release build) elsewhere. Internally, TeamCity is the most common place to get latest or released EAP builds of our products, e.g. IDEA. With the new search functionality finding necessary build artifacts become even easier.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Chris,

Right now you can only configure the path to the whole .BuildServer directory. Artifacts are stored in .BuildServer/system/artifacts directory.

You can file a feature request for separate artifacts storage directory configuration.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.