Where are stored artifacts on server?

Hello,

Artifacts are stored on the disk on the server, under TeamCity Data Directory/artifacts/<project name>/<build configuration name>/<internal_build_id> directory. Storage format is described in the TeamCity Data Directory section.

Kind regards,
Marina

Le 19/08/2010 16:59, Marina Grechko a ecrit :

Hello,

>

Artifacts are stored on the disk on the server, under http://confluence.jetbrains.net/display/TCD5/TeamCityDataDirectory/artifacts/<project name>/<build configuration name>/<internal_build_id>  directory. Storage format is described in the http://confluence.jetbrains.net/display/TCD5/TeamCityDataDirectory section.

Thank you, I found it !

Gérald

Hi again,

Does internal_build_id correspond to %env.BUILD_NUMBER% ?

Regards,

Gérald

No, this is internal unique identifier — build configuration ID. To determine the internal ID of a build configuration navigate to the build configuration home page and in page URL, find the buildTypeID=btXXX parameter (see http://confluence.jetbrains.net/download/attachments/15802095/buildConfigurationId.png).

Kind regards,
Marina

Le 20/08/2010 12:44, Marina Grechko a ecrit :

No, this is internal unique identifier — build configuration ID. To determine the internal ID of a build configuration navigate to the build configuration home page and in page URL, find the buildTypeID=btXXX parameter (see http://confluence.jetbrains.net/download/attachments/15802095/buildConfigurationId.png).

Mmmm... well, that gives me the id of the build, but not the internal
build_id I see on the server :

On filesystem :

TeamCity/.BuildServer/system/artifacts/weekly/trunk_weekly_windll/7127/Test_Output/


In TeamCity
http://../repository/download/bt48/7127:id/Test_Output

The bt48 is the build configuration id, ok, but the 7127 is another id,
is there a way to get it with environment variable maybe ?

Gérald

Gerald,

Sorry for misleading. In path to build artifacts by <internal build id> should be meant id of certain build. For example, in your case to access artifacts on filesystem  you should navigate to TeamCity/.BuildServer/system/artifacts/weekly/trunk_weekly_windll/7127 where
7127 is internal build id. bt48 in the URL — it is build configuration id i mentioned in previous post.

Could you please explain why do you need this information?
If you need URL patterns that you may use to download build artifacts from outside of TeamCity please refer to http://confluence.jetbrains.net/display/TCD5/Patterns+For+Accessing+Build+Artifacts.

Kind regards,
Marina

Le 20/08/2010 14:44, Marina Grechko a ecrit :

Gerald,

>

Sorry for misleading. In path to build artifacts by<internal build id>  should be meant id of certain build. For example, in your case to access artifacts on filesystem  you should navigate to TeamCity/.BuildServer/system/artifacts/weekly/trunk_weekly_windll/7127 where
7127 is internal build id. bt48 in the URL — it is build configuration id i mentioned in previous post.

Ok, so that's not the id I wanted.

>

Could you please explain why do you need this information?
If you need URL patterns that you may use to download build artifacts from outside of TeamCity please refer to http://confluence.jetbrains.net/display/TCD5/PatternsForAccessingBuildArtifacts.

Actually, on the server where TeamCity is running, I have also a script
that let me compare results of some tests, and I need to access to file
in their folder on the server, as they are stored there.

So when a user look at build results, he can click on a test results
that will open some PHP script that compare results to some previous
version, by reading file on server in artifacts.

For the moment, I found a workaround by extracting id from referer url.

If there is a better way for that, I'll be glad to try it.

Thanks,

Gérald

Hello Gerald,

You can try to use URL patterns for obtaining artifacts.

Kind regards,
Marina