Downloads:

2,569

Downloads of v 0.5.0:

270

Last Update:

20 Sep 2017

Package Maintainer(s):

Software Author(s):

  • fwinkelbauer

Tags:

Versioning Build AssemblyInfo NuSpec

Bumpy

This is not the latest version of Bumpy available.

0.5.0 | Updated: 20 Sep 2017

Downloads:

2,569

Downloads of v 0.5.0:

270

Maintainer(s):

Software Author(s):

  • fwinkelbauer

Bumpy 0.5.0

This is not the latest version of Bumpy available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall Bumpy, 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 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 bumpy.portable -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 bumpy.portable -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 bumpy.portable installed
  win_chocolatey:
    name: bumpy.portable
    state: present
    version: 0.5.0
    source: STEP 3 URL

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

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


chocolatey_package 'bumpy.portable' do
  action    :install
  version  '0.5.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: bumpy.portable,
    Version: 0.5.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller bumpy.portable
{
   Name     = 'bumpy.portable'
   Ensure   = 'Present'
   Version  = '0.5.0'
   Source   = 'STEP 3 URL'
}

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


package { 'bumpy.portable':
  provider => 'chocolatey',
  ensure   => '0.5.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install bumpy.portable version="0.5.0" 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 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 approved as a trusted package on 20 Sep 2017.

Description

Bumpy is a tool to manipulate version information across multiple files found in the current working directory using a configuration file which consists of glob patterns and regular expressions.


tools\Bumpy.exe
md5: 88923F2B23852BA3EB8CE168717D3150 | sha1: 2BE0B9AED730EBFB8723276BF417C32893E79911 | sha256: 5843E098771D275B5E4341560220336888B373C47CFDF42219246D816AE444D0 | sha512: 09350F48627D60A6E7333B43512CA1025C3B11AABDCB1F67AEF5ABEF8C65DFB8FCB025360957BA0A3DD3F8383BD20910713C120ED2B5595472C4537A1B8D8D80
tools\Bumpy.pdb
 
tools\LICENSE.txt
MIT License

Copyright (c) 2017 Florian Winkelbauer

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
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 Florian Winkelbauer (fwinkelbauer).
The bumpy.exe binary contained in the Chocolatey package is identical to the
binary found in the NuGet package published at nuget.org [1].
Both packages are also published on GitHub [2].

[1] https://www.nuget.org/packages/Bumpy/
[2] https://github.com/fwinkelbauer/Bumpy/releases

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
Bumpy 0.10.0 213 Monday, February 26, 2018 Approved
Bumpy 0.9.0 242 Friday, February 9, 2018 Approved
Bumpy 0.8.0 232 Tuesday, February 6, 2018 Approved
Bumpy 0.6.0 275 Wednesday, October 18, 2017 Approved
Bumpy 0.5.0 270 Wednesday, September 20, 2017 Approved
Bumpy 0.4.1 245 Thursday, August 24, 2017 Approved
Bumpy 0.2.1 266 Friday, July 7, 2017 Approved
Bumpy 0.1.0 271 Saturday, June 24, 2017 Approved

This package has no dependencies.

Discussion for the Bumpy Package

Ground Rules:

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