Skip to content

Check in

Jump to bottom
Jesse Houwing edited this page Jun 3, 2016 · 10 revisions

The check-in tasks performs a TFVC checkin operation and will automatically detect all edits and deletes you've made to your $(Build.SourcesDirectory), optionally scoped to a specific path. It's able to by-pass your checkin policies and can optionally suppress a CI build by adding a specific comment.

Consent

  • I understand - if your build system dived into an endless loop, uses up all your build minutes or destroys your source tree by accident. You've signaled you understand this risk, the task won't work without this consent.

Configuration

  • Files to check in - specify one or more paths, separated by ; or newline. While wildcards (?, *) are supported, they're not the same as the minimatch patterns used by other build tasks and do not support the recursive wildcard **.

    Example: $/MyTeamproject/Main/*.cs

  • Recursion - controls whether you'll be checking in just the current folder/file (None), one level below the selected path (One Level) or all levels below the selected path (Full).
  • Check-in comment - The comment which will show up in the source control history for this changeset.
  • Skip shelveset build - Will skip the checkin when the build is a shelveset build.
  • Skip gated build - Will skip the checkin when the build is a gated build.

Auto-detect changes

  • Edits - Are always detected and this cannot be turned off.
  • Adds - Scans for added files in the workspace and adds that change to the list of pending changes.
  • Deletes - Scans for deleted files in the workspace and adds that change to the list of pending changes.

Note These options always take the .tfignore file into account.

Notes

  • Notes - specify one or more checkin notes using the following format Name=Value or Name:Value separated by ; or newline.

Policy Override

  • Bypass CI on check in - adds a special string to the check-in comment to ensure that no other build is triggered.
  • Override policies - to override any check-in policies or changeset-notes that may be required by your administrator.
  • Override reason - when enabling Override Policies, you're required to specify a reason. This reason is stored with the changeset.

Icon

Clone this wiki locally