Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It depends what you are trying to do.</p> <p>1) Do you want the build + staging to run as one operation? So that you end up with one consolidated build report, one log file, one job in the server's build queue, every step executed sequentially by the same Build Agent that executed the previous step?</p> <p>If so, then you are on basically the right path. I wouldn't <code>&lt;Exec</code>> out to tfsbuild.exe though -- running an entire new build has a lot of overhead, and I'm not sure what the potential side effects are. Instead, I would use the <code>&lt;Call</code>> task to execute msbuild tasks defined in your staging script(s).</p> <p>2) Do you want the "build build" to actually queue a separate "staging build"? Separate reports, log files, &amp; spots in the queue? Opportunity to be executed in parallel if you have multiple Build Agents?</p> <p>If so, then:</p> <ul> <li>create a new build definition(s) for staging</li> <li>add some code to your original build definition that queues [one/several] of the new build definitions using the Team Build API. <a href="http://notsosmartbuilder.blogspot.com/2007/09/team-build-2008-api.html" rel="noreferrer">Sample code</a>.</li> <li>remove anything not related to the core build from the original build definition</li> <li>make sure the new "staging" definitions don't have any automatic triggers (time intervals, checkin events, etc)</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to chain TFS builds?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRichard Berg
    1. USRichard Berg
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPreferably step 1, but <call> task cannot be used as you suggest. The staging build needs to be driver of the build in this case. It calls the core build and then does its custom staging. The problem with using a Minimal tfsbuild proj file is that, TFSBuild definition file created via the UI sets all path properties based on the solution picked to be built.(as we agree, staging build definition should not rebuild the solution) So is a pain to get the paths configured to call the right core TFSBuild.proj file without hardcoding them.
      singulars
      1. PO
      1. USuser22242
    2. COI don't understand the problem. Why not store your staging scripts in the same directory as your build scripts? Actually, even that is not necessary -- just ensure the relative paths stay the same. ///// If that doesn't help, please give more detail on what you're trying to do. What are the exact things you expect to happen in the "first build" and "second build?" What tasks do they have in common, and what needs to be customized?
      singulars
      1. PO
      1. USRichard Berg
    3. COBTW, depending on what you're trying to do, Team Build might not be the right approach at all. For instance, my test environments are setup on a "pull" model instead of "push". Each machine subscribes to the TFS notification system. When a BuildCompletion event is raised, a service on the machine checks against various criteria configured for that box and redeploys a test environment as appropriate.
      singulars
      1. PO
      1. USRichard Berg
 

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