Databases
StackOverflow2013
Postsdbo
POCreating zipped artefacts and versioning with TeamCity
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating zipped artefacts and versioning with TeamCity
    primarykey
    data
    text
    <p>I am using TFS 2010 with TeamCity 8. Its a dot net solution.</p> <p>I need three things. </p> <p>1- Assemblies should be verisoned like this: <code>4.3.[tfs revision number].[counter]</code>.</p> <p>(i.e. Assembly File Version and Assembly Product Version.)</p> <p>2- The solution structure looks like this:</p> <pre><code> Root folder -&gt; solution.sln Root folder -&gt; proj1 -&gt; proj1.proj Root folder -&gt; proj2 -&gt; proj2.prj Root folder -&gt; several other projects </code></pre> <p>Please note that proj1 is an asp.net web application and proj2 is a wcf service.</p> <p>I want to create two zip files on the server <code>\\myserver\teamcityartefact\proj1.zip</code> and <code>\\myserver\teamcityartefact\proj2.zip</code>.</p> <p>3- I also want to make sure that the release configuration is used to build the artefacts.</p> <p><strong>Is there any thorough walk-through you can recommend?</strong></p> <p>Settings: The build step settings are: Runner type: Visual Studio (sln). Solution file path: solution.sln. Visual Studio: Microsoft Visual Studio 2013. Targets: Clean;Rebuild;Publish; Configuration: Release.</p> <hr> <p>What have I tried so far:</p> <p>a. Artifact Paths: <code>*.* =&gt; \\myserver\teamcityartefact\proj1.zip</code></p> <p>But that creates four files in the zip file. solution.sln, solution.sln.metaproj, solution.sln.metaproj.tmp and solution.vssscc.</p> <p>b. Artifact Paths: <code>proj1\**\*.* =&gt; projA</code> and <code>proj2\**\*.* =&gt; projB</code> returns me all the files in the projects. These are not pre-compiled published files. The build step settings are: Runner type: Visual Studio (sln). Solution file path: solution.sln. Visual Studio: Microsoft Visual Studio 2013. Targets: Clean;Rebuild;Publish; Configuration: Release.</p> <p>c. proj1**\bin***.* => projA.zip returns me the contents of the bin folder. Its an asp.net application.</p> <p>d. I am sure the release configuration is not being used as the webconfig is not transformed.</p> <p>e.The build number format of assemblies in the bin folder at the moment is 1.0.0.0.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOxon
    1. USOxon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COcan you be more specific why alternative b. is not satifactory? How come you are uncertain that the Release configuration is used?
      singulars
      1. POCreating zipped artefacts and versioning with TeamCity
      1. USSnorre
    2. COThanks for the comment @Snorre. Although I get all the files but they are not pre-compiled. For example, all the .cs files (source files) are in the artefacts. I want the published version (i.e. only the dlls and .aspx files for pages).
      singulars
      1. POCreating zipped artefacts and versioning with TeamCity
      1. USOxon
    3. COAnd... The release configuration is not used because the webconfigs are not transformed.
      singulars
      1. POCreating zipped artefacts and versioning with TeamCity
      1. USOxon
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload