Build: Gulp

Last Update: 3/6/2017

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

Node.js streaming task based build system

Demands

gulp

Arguments

Argument Description
Gulp file path Relative path from the repo root to the gulp script that you want to run. The default value is gulpfile.js
Gulp 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 gulp.

Tip: --gulpfile is not needed. This argument is handled by the Gulp 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.
gulp.js location gulp.js to run. The default value is node_modules/gulp/bin/gulp.js
Control options

Example

Run gulp.js

On the Build tab:

Package: npm
Package: npm

Install npm.

  • Command: install
Build: Gulp
Build: Gulp

Run your script.

  • Gulp file path: gulpfile.js
  • Advanced, gulp.js location: node_modules/gulp/bin/gulp.js

Build a Node.js app

Build your Node.js app with Gulp

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.