Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Build Automation in PowerShell

License

NotificationsYou must be signed in to change notification settings

nightroman/Invoke-Build

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

PSGVPSGDNGVNGD

Build Automation in PowerShell

Invoke-Build is a build and test automation tool which invokes tasks defined inPowerShell v3.0+ scripts. It is similar to psake but arguably easier to use andmore powerful. It is complete, bug free, well covered by tests.

In addition to basic task processing the engine supports

  • Incremental tasks with effectively processed inputs and outputs.
  • Persistent builds which can be resumed after interruptions.
  • Parallel builds in separate workspaces with common stats.
  • Batch invocation of tests composed as tasks.
  • Ability to define new classes of tasks.

Invoke-Build v3.0.1+ is cross-platform with PowerShell Core.

Invoke-Build can be effectively used in VSCode and ISE.

SeveralPowerShell Team projects use Invoke-Build.

The package

The package includes the engine, helpers, and help:

Extra scripts, see PSGallery and the repository:

And some more tools, see the repository:

Install as module

Invoke-Build is published as PSGallery moduleInvokeBuild.You can install it by one of these commands:

Install-Module InvokeBuild

To install the module with Chocolatey, run the following command:

choco install invoke-build

NOTE: The Chocolatey package is maintained by its owner.

Install as scripts

Invoke-Build is also published asnuget.org/packages/Invoke-Build.

If you usescoop then invoke:

scoop install invoke-build

and you are done, scripts are downloaded and their directory is added to thepath. You may need to start a new PowerShell session with the updated path.

Otherwise, download the package manually, rename it to zip, extract itstoolsand rename toInvokeBuild. Consider including this directory to the path forinvoking scripts by names. Or copy to any PowerShell module directory in orderto use it as module.

Install as dotnet tool

nuget.org/packages/ib provides Invoke-Buildas the dotnet toolib which may be installed as global or local.

To install the global tool:

dotnet tool install --global ib

To install the local tool:

dotnet new tool-manifest # once on setting up a repo with toolsdotnet tool install --local ib

Seeib/README for more details aboutib commands.

Getting help

If you use the module (known issue#2899) or the script is not in the path,use the full pathhelp .../Invoke-Build.ps1 instead ofhelp Invoke-Build.

In order to get help for the engine, invoke:

help Invoke-Build -full

In order to get help for internal commands:

. Invoke-Buildhelp task -fullhelp exec -full...

See also onlineInvoke-Build Help

Online resources

Questions, suggestions, and reports are welcome atdiscussions andissues.

Credits

About

Build Automation in PowerShell

Topics

Resources

License

Stars

Watchers

Forks

Sponsor this project

 

Languages


[8]ページ先頭

©2009-2025 Movatter.jp