Downloads:

8,463

Downloads of v 2.2.6:

205

Last Update:

4/26/2019

Package Maintainer(s):

Software Author(s):

  • Inedo

Tags:

upack command line client

2.2.6 | Updated: 4/26/2019

Downloads:

8,463

Downloads of v 2.2.6:

205

Maintainer(s):

Software Author(s):

  • Inedo

Tags:

upack command line client 2.2.6

All Checks are Passing

2 Passing Test


Verification Testing Passed

Details

Validation Testing Passed

To install upack command line client, run the following command from the command line or from PowerShell:

>

To upgrade upack command line client, run the following command from the command line or from PowerShell:

>

To uninstall upack command line client, run the following command from the command line or from PowerShell:

>

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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade upack -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 upack -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure upack installed
  win_chocolatey:
    name: upack
    state: present
    version: 2.2.6
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020!


chocolatey_package 'upack' do
  action    :install
  version  '2.2.6'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: upack,
    Version: 2.2.6,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller upack
{
   Name     = 'upack'
   Ensure   = 'Present'
   Version  = '2.2.6'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'upack':
  provider => 'chocolatey',
  ensure   => '2.2.6',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install upack version="2.2.6" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 8/5/2019.

Description

upack is a simple CLI tool for building, installing, and publishing universal packages to universal feeds.


tools\LICENSE
 
tools\upack.exe
md5: 43A779A3670A3DB53F9A8F3C66812EE4 | sha1: 5F768B50C4622FA739B2D023558662E2AFAEADE1 | sha256: D2D39BF69F9E9703BAEC449EC41E9D9EFC7C7CCF56D35BAA615691CDDED40773 | sha512: BD153766DE08670AE24C4498BD43EECCEF8E9A1E4B4C2DAF23857CE174BCAA6AF45244A74A46F8EF12B33E3B68109849DFBA87A5968BC6FF3C0086734963D61B
tools\VERIFICATION.md
*This file is intended to assist the Chocolatey moderators and community in verifying that this package's contents are trustworthy.*

The Chocolatey package should contain one executable file `upack.exe`, which is digitally signed by Inedo's code signing certificate.

`upack.exe` should be exactly the same file as the file named `upack.exe` on the corresponding GitHub release.

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
upack command line client 2.2.5 148 Tuesday, January 15, 2019 approved
upack command line client 2.2.4 49 Friday, January 11, 2019 approved
upack command line client 2.2.3 64 Saturday, December 15, 2018 approved
upack command line client 2.2.2 414 Friday, August 10, 2018 approved
upack command line client 2.2.1 301 Wednesday, May 2, 2018 approved
Show More

This package has no dependencies.

Discussion for the upack command line client Package

Ground Rules:

  • This discussion is only about upack command line client and the upack command line client 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 upack command line client, 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