Downloads of v 5.1.2:


Last Update:

26 Apr 2012

Package Maintainer(s):

Software Author(s):

  • Arto
  • frando
  • Moshe Weitzman
  • Owen Barton
  • jonhattan
  • greg.1.anderson


drupal drush cmd

Drush (Command Line)

5.1.2 | Updated: 26 Apr 2012



Downloads of v 5.1.2:



Software Author(s):

  • Arto
  • frando
  • Moshe Weitzman
  • Owen Barton
  • jonhattan
  • greg.1.anderson


drupal drush cmd

Drush (Command Line) 5.1.2

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test

Validation Testing Unknown

Verification Testing Passed


To install Drush (Command Line), run the following command from the command line or from PowerShell:


To upgrade Drush (Command Line), run the following command from the command line or from PowerShell:


To uninstall Drush (Command Line), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade drush.commandline -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade drush.commandline -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure drush.commandline installed
    name: drush.commandline
    state: present
    version: 5.1.2
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'drush.commandline' do
  action    :install
  version  '5.1.2'
  source   'STEP 3 URL'

See docs at

    Name: drush.commandline,
    Version: 5.1.2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller drush.commandline
   Name     = 'drush.commandline'
   Ensure   = 'Present'
   Version  = '5.1.2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'drush.commandline':
  provider => 'chocolatey',
  ensure   => '5.1.2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install drush.commandline version="5.1.2" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.


The Drush Project Manager allows you to download, enable, disable, uninstall, update modules/themes/profiles/translations from the command line in a very simple way (apt-get style) - just type e.g. drush dl views and drush pm-enable views in a Drupal directory to install the Views project! Additionally, the Drush Package Manager also allows you to update all your modules and even Drupal core with just one command - drush pm-update.

Drush Core: several useful utilities for site administrators and developers (e.g. drush cron or drush cache-clear). Also includes a customized bash shell for drush. Start it with the drush cli command.
Drupal SQL Commands help you issue queries to any of your databases (i.e. is multi-site aware) and even helps you migrate databases between your environments.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Drush (Command Line) 5.1.1 333 Thursday, April 26, 2012 Unknown
Drush (Command Line) 5.1 325 Thursday, April 26, 2012 Unknown
Discussion for the Drush (Command Line) Package

Ground Rules:

  • This discussion is only about Drush (Command Line) and the Drush (Command Line) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Drush (Command Line), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus