Build: Grunt

Last Update: 9/26/2016

Team Services | TFS 2017 | TFS 2015 Update 3 | Previous versions: XAML Build, Release

The JavaScript Task Runner

Demands

The build agent must have the following capability:

  • Grunt

Arguments

Argument Description
Grunt File Path Relative path from the repo root to the grunt script that you want to run. The default value is gruntfile.js
Grunt task(s) (Optional) Space delimited list of tasks to run. If you leave it blank, the default task will run.
Advanced
Arguments

Additional arguments passed to grunt. See Using the CLI.

Tip: --gruntfile is not needed. This argument is handled by the Grunt file path argument shown above.

Working directory Current working directory when the script is run. If you leave it blank, the working directory is the folder where the script is located.
Control options

Example

See Sample Gruntfile.

Q&A

Do I need an agent?

You need at least one agent to run your build or release. Get an agent.

I can't select a default agent queue and I can't queue my build or release. How do I fix this?

See queues.

I use Team Foundation Server on-premises and I don't see some of these features. Why not?

Some of these features are available only on Visual Studio Team Services and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.