0
votes

I have a custom TFS Build template that includes a procedure that runs a process that involves getting some data from a server and checking it into TFS before moving onto the main build process.

The steps are as follows:

  1. Set build number
  2. Run our custom script - get data, check into TFS
  3. Initialize environment
  4. Get sources from Team Foundation Version Control
  5. Associate the changesets that occurred since the last good build
  6. Compile, Test and Publish

The issue I appear to be having is that all change sets since the last successful build are included, except, the change set associated with the script run at step 2.

Does anyone know what could be going on here? my guess is that the logic that is looking for the change sets since last build is using a cut off that is set at the moment the build is requested (hence why the last change set is ignored) but this is just an uneducated guess.

Thanks in advance for your help.

2
Why you want to use step2 to check in code before build starts, and what data you need to check in? The changeset created in steps seems can't be recognized using the default Associate changesets activity.Tingting0929
We have a server that contains default data that is inserted into the database at install time. The process in step two reads that data into an XML format and checks in the resulting files into TFS. This is normally kicked off manually but for our nightly builds we need this to be done as part of the build.jcnewman83
What's the build system you use? XAML or vNext?Eddie Chen - MSFT
I am using XAMLjcnewman83

2 Answers

0
votes

I would have two builds chained: the first build generates and check-in the files the second simply pulls them down.

0
votes

Trying the steps below:

  1. Edit your build definition and go to "Process" tab.
  2. Enter "T" under "Get version" option. enter image description here
  3. Queue the build and check the result.