Downloads:

676,525

Downloads of v 4.39.3:

3,142

Last Update:

17 Aug 2018

Package Maintainer(s):

Software Author(s):

  • Octopus Deploy

Tags:

automation deployment

Octo.exe

This is not the latest version of Octo.exe available.

  • 1
  • 2
  • 3

4.39.3 | Updated: 17 Aug 2018

Downloads:

676,525

Downloads of v 4.39.3:

3,142

Software Author(s):

  • Octopus Deploy

  • 1
  • 2
  • 3
Octo.exe 4.39.3

This is not the latest version of Octo.exe available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

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.

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Octo.exe, run the following command from the command line or from PowerShell:

>

To upgrade Octo.exe, run the following command from the command line or from PowerShell:

>

To uninstall Octo.exe, 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 https://community.chocolatey.org/api/v2/)


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 https://community.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. Copy Your Script

choco upgrade octopustools -y --source="'INTERNAL REPO URL'" --version="'4.39.3'" [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 octopustools -y --source="'INTERNAL REPO URL'" --version="'4.39.3'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install octopustools
  win_chocolatey:
    name: octopustools
    version: '4.39.3'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'octopustools' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.39.3'
end

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


cChocoPackageInstaller octopustools
{
    Name     = "octopustools"
    Version  = "4.39.3"
    Source   = "INTERNAL REPO URL"
}

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


package { 'octopustools':
  ensure   => '4.39.3',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved as a trusted package on 17 Aug 2018.

Description

Octopus Deploy is an automated release management tool for modern developers and DevOps teams.

This package contains Octo.exe, a command line tool for creating and deploying releases with Octopus Deploy.


tools\init.ps1
param($installPath, $toolsPath, $package, $project)

$path = $env:PATH
if (!$path.Contains($toolsPath)) {
    $env:PATH += ";$toolsPath"
}
tools\LICENSE.txt
From: https://github.com/OctopusDeploy/OctopusClients/blob/master/LICENSE.txt

LICENSE

Copyright (c) Octopus Deploy and contributors. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use
these files except in compliance with the License. You may obtain a copy of the
License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for the
specific language governing permissions and limitations under the License.
tools\Octo.exe
md5: BDD3A3CC4BB58F738D97B7A971A2D923 | sha1: A3DEC2B45B721CF7264A0026BC3BCC246C3E94E8 | sha256: F8F41025FFBE62F8DECD3A26D0ED1D447BFA393CE64C71392D238C0CF4C5E099 | sha512: 4B8F1F0A24AB068B3A4C2ADCB47764F5141999DA4965DD783AF915A2AB75C2606741AB447A1F559054F86988DE996A68AC4041598626B60B9A5263B2EC6BB6DB
tools\Octo.exe.config
<?xml version="1.0" standalone="yes"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.6.9.0" newVersion="2.6.9.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
</configuration>
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

This package is published by the Octopus Deploy team itself.

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
Octopus CLI 7.4.3528 80 Thursday, December 2, 2021 Approved
Octopus CLI 7.4.3527 171 Wednesday, December 1, 2021 Approved
Octopus CLI 7.4.3526 3 Tuesday, November 30, 2021 Pending Automated Review
Octopus CLI 7.4.3525 139 Monday, November 29, 2021 Approved
Octopus CLI 7.4.3524 248 Sunday, November 28, 2021 Approved
Octopus CLI 7.4.3522 423 Friday, November 26, 2021 Approved
Octopus CLI 7.4.3521 183 Thursday, November 25, 2021 Approved
Octopus CLI 7.4.3520 307 Wednesday, November 24, 2021 Approved

This package has no dependencies.

Discussion for the Octo.exe Package

Ground Rules:

  • This discussion is only about Octo.exe and the Octo.exe 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 Octo.exe, 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