Downloads of v 0.3.0:


Last Update:

30 Jun 2014

Package Maintainer(s):

Software Author(s):

  • Gordon Thiesfeld


pik ruby admin

Pik (Ruby)

  • 1
  • 2
  • 3

0.3.0 | Updated: 30 Jun 2014



Downloads of v 0.3.0:



Software Author(s):

  • Gordon Thiesfeld


pik ruby admin

  • 1
  • 2
  • 3
Pik (Ruby) 0.3.0

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Pik (Ruby), run the following command from the command line or from PowerShell:


To upgrade Pik (Ruby), run the following command from the command line or from PowerShell:


To uninstall Pik (Ruby), run the following command from the command line or from PowerShell:


Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade pik -y --source="'INTERNAL REPO 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 pik -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install pik
    name: pik
    version: '0.3.0'
    state: present

See docs at

chocolatey_package 'pik' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.3.0'

See docs at

cChocoPackageInstaller pik
    Name     = "pik"
    Version  = "0.3.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'pik':
  ensure   => '0.3.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator mwrock on 26 Oct 2014.


Pik is a tool to manage multiple versions of ruby on Windows. It can be used from the Windows command line (cmd.exe), Windows PowerShell, or Git Bash. I have yet to test on cygwin.
Pik Commands

  • add - Adds another ruby location to pik.
  • benchmark|bench - Runs bencmarks with all versions that pik is aware of.
  • checkup|cu - Checks your environment for current Ruby best practices.
  • config - Adds/modifies configuration options.
  • default - Switches back to the default settings.
  • gem - Runs the gem command with all versions that pik is aware of.
  • gemsync - Synchronizes gems from the version specified to the current version.
  • help - Displays help information.
  • implode - Removes your pik configuration.
  • info - Displays information about the current ruby version.
  • install|in - Downloads and installs different ruby versions.
  • list|ls - Lists ruby versions that pik is aware of.
  • rake - Runs the rake command with all versions that pik is aware of.
  • remove|rm - Removes a ruby location from pik.
  • ruby|rb - Runs ruby with all versions that pik is aware of.
  • run - Runs command with all versions of ruby that pik is aware of.
  • switch|sw|use - Switches ruby versions based on patterns.
  • tag - Adds the given tag to the current version.
  • tags - Runs the pik command against the given tags.
  • uninstall|unin - Deletes a ruby version from the filesystem and removes it from Pik.
  • update|up - updates pik.

For help on a particular command, use 'pik help COMMAND'.

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.

Add to Builder Version Downloads Last Updated Status
Pik (Ruby) 782 Saturday, November 16, 2013 Unknown
Pik (Ruby) 523 Monday, November 11, 2013 Unknown
Pik (Ruby) 724 Monday, April 22, 2013 Unknown
Pik (Ruby) 518 Monday, April 22, 2013 Unknown
Pik (Ruby) 0.2.8 776 Friday, February 17, 2012 Unknown

This package has no dependencies.

Discussion for the Pik (Ruby) Package

Ground Rules:

  • This discussion is only about Pik (Ruby) and the Pik (Ruby) 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 Pik (Ruby), 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