omnibus 5.5.0 → 5.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: df89be1587ea0dd7f53b9d049fd0b98e59303696
-  data.tar.gz: 3dbf3e7857bfd275f4d35e04d1b2522259a82f01
+  metadata.gz: c1743d10eeba568049429e83ffe6c49ee3d03af8
+  data.tar.gz: d3ddb3b93766faa83e19cf591c4324c9a6392797
 SHA512:
-  metadata.gz: 73d9cf647ab0734f4e13797ae98f7baff5d1f03011bcd826c291cab03f8fd4c7448fc8328d903211a675b1b023034b84d84a2bd85f304c901e9cc47b6f88fcba
-  data.tar.gz: 895ab544f10c0cd284965c21c586c30b439ba679f1898b14d1f72671d91c21de43eca176141cdb681f9e8c18de8b93ea9b4e7d62eeb316fa4175fb0f50bbefbf
+  metadata.gz: 834462aa9e01a2086d7058c51a595a2ece8ff28d64a7d4166952e950558e5657e9e5e191df2bdbe667c0edb6fbefa72dd5f216668e6d3502dbc64a1aa677b446
+  data.tar.gz: 106d58b1f31a951a25412caa752506fd39979e65f5a584190820ae72781e9c7a350a2f9b5a9acd5fb73c68ef62ac9b13eeef1a7566a609fcb8a4e4173f151294

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -4,3 +4,14 @@ Briefly describe the new feature or fix here
 
 --------------------------------------------------
 /cc @chef/omnibus-maintainers <- This ensures the Omnibus Maintainers team are notified to review this PR.
+
+#### Maintainers
+
+Please ensure that you check for:
+
+- [] If this change impacts git cache validity, it bumps the git cache
+  serial number
+- [] If this change impacts compatibility with omnibus-software, the
+  corresponding change is reviewed and there is a release plan
+- [] If this change impacts compatibility with the omnibus cookbook, the
+  corresponding change is reviewed and there is a release plan

data/.travis.yml

@@ -1,7 +1,8 @@
 sudo: false
 rvm:
-  - 2.1.9
   - 2.2.5
+  - 2.3.1
+  - 2.4.1
 bundler_args: "--jobs 7 --without docs local"
 branches:
   only:

data/CHANGELOG.md

@@ -1,6 +1,43 @@
 Omnibus CHANGELOG
 =================
 
+v5.6.0 (June 20, 2017)
+----------------------
+### New Features
+- Add AWS Shared Credentials support.(#781)
+- Add option to build command to populate S3 cache. (#781)
+- Add strip BuildCommand. (#775)
+- Add support for building against omnibus-toolchain on Windows. (#759)
+- Don't require build user to have a configured Git identity (#758)
+- Added endpoint and S3 transfer acceleration as config options (#736)
+- Only checkout from git_cache once (#747)
+- IPS: Add version-lock facet at end of manifest (#745)
+- Alpine Linux Support (#744)
+- Add fips_mode flags (#742)
+- SmartOS pkgsrc support (#733)
+- Make DEB and RPM compression configurable (#738)
+- Check for the transitive dependency licensing errors during post_build. (#729)
+- Enable gcc 4.8 on suse/sles if available (#720)
+- Allow manually specify transitive dependency license information (#712)
+
+### Bug Fixes
+- Various bugfixes for APPX support. (#752, #759)
+- Expose overrides. (#780)
+- Fixed documentation links and table in README (#769, #778)
+- Fixed Travis CI Label (#777)
+- git_cache fixes: Use `.join` on git commands lines to avoid mangle and set
+  `core.ingorecase=false` (#768)
+- Ignore paths with braces in the BFF packager. (#771)
+- Switch from single to double quotes in git config. (#767)
+- Fixed Windows globbing. (#766)
+- Update pedump to latest released. (#714)
+- Retry git network operations by default (#753)
+- Fix guard for non-caching projects (#751)
+- DMG bug fixes (#748)
+- IPS Package fixes (#718, #728, #740)
+- Artifactory publisher fixes/improvements (#725)
+- Do not autoload fetcher to avoid eace condition (#715)
+
 v5.5.0 (August 16, 2016)
 -----------------------
 ### New Features

data/Gemfile

@@ -1,11 +1,12 @@
 source "https://rubygems.org"
 gemspec
 
-# Fork to allow for a recent version of multipart-post.
-gem "pedump", git: "https://github.com/ksubrama/pedump", branch: "patch-1"
-
 # Always use license_scout from master
-gem "license_scout", github: "chef/license_scout"
+gem "license_scout", git: "https://github.com/chef/license_scout"
+
+# net-ssh 4.x does not work with Ruby 2.2 on Windows. Chef and ChefDK
+# are pinned to 3.2 so pinning that here. Only used by fauxhai in this project
+gem "net-ssh", "3.2.0"
 
 group :docs do
   gem "yard",          "~> 0.8"

data/MAINTAINERS.md

@@ -2,27 +2,22 @@
 
 This file lists how the `omnibus` project is maintained.
 
-When making changes to the system, you need two maintainers to provide a :+1: on
-your pull request. Additionally, you need to not receive a veto from a
-Lieutenant or the Project Lead.
+When making changes to the system, you need two maintainers to provide a :+1: on your pull request. Additionally, you need to not receive a veto from a Lieutenant or the Project Lead.
 
-Check out
-[How Chef is Maintained](https://github.com/chef/chef-rfc/blob/master/rfc030-maintenance-policy.md#how-the-project-is-maintained)
-for details on the process, how to become a maintainer, lieutenant, or the
-project lead.
+Check out [How Chef is Maintained](https://github.com/chef/chef-rfc/blob/master/rfc030-maintenance-policy.md#how-the-project-is-maintained) for details on the process, how to become a maintainer, lieutenant, or the project lead.
 
 ## Project Lead
 
-* [Seth Chisamore](https://github.com/schisamo)
+- [Seth Chisamore](https://github.com/schisamo)
 
 ## Maintainers
 
-* [Daniel DeLeo](https://github.com/danielsdeleo)
-* [Jay Mundrawala](https://github.com/jaym)
-* [Kartik Null Cating-Subramanian](https://github.com/ksubrama)
-* [Lamont Granquist](https://github.com/lamont-granquist)
-* [Scott Hain](https://github.com/scotthain)
-* [Seth Vargo](http://github.com/sethvargo)
-* [Steven Danna](https://github.com/stevendanna)
-* [Thom May](https://github.com/thommay)
-* [Yvonne Lam](http://github.com/yzl)
+- [Daniel DeLeo](https://github.com/danielsdeleo)
+- [Jay Mundrawala](https://github.com/jaym)
+- [Kartik Null Cating-Subramanian](https://github.com/ksubrama)
+- [Lamont Granquist](https://github.com/lamont-granquist)
+- [Scott Hain](https://github.com/scotthain)
+- [Seth Vargo](http://github.com/sethvargo)
+- [Steven Danna](https://github.com/stevendanna)
+- [Thom May](https://github.com/thommay)
+- [Yvonne Lam](http://github.com/yzl)

data/README.md

@@ -1,32 +1,27 @@
-![Omnibus Icon](lib/omnibus/assets/README-logo.png) Omnibus
-===========================================================
+# ![Omnibus Icon](lib/omnibus/assets/README-logo.png) Omnibus
+
 [![Gem Version](http://img.shields.io/gem/v/omnibus.svg)][gem]
-[![Travis Build Status](http://img.shields.io/travis/chef/omnibus.svg?label=Travis CI)][travis]
+[![Travis Build Status](http://img.shields.io/travis/chef/omnibus.svg?label=Travis%20CI)][travis]
 [![AppVeyor Build Status](http://img.shields.io/appveyor/ci/chef/omnibus.svg?label=AppVeyor)][appveyor]
 
-[gem]: https://rubygems.org/gems/omnibus
-[travis]: https://travis-ci.org/chef/omnibus
-[appveyor]: https://ci.appveyor.com/project/chef/omnibus
-
 Easily create full-stack installers for your project across a variety of platforms.
 
 Seth Chisamore and Christopher Maier of CHEF gave an introductory talk on Omnibus at ChefConf 2013, entitled **Eat the Whole Bowl: Building a Full-Stack Installer with Omnibus**:
-  - [Video](http://www.youtube.com/watch?v=q8iJAntXCNY)
-  - [Slides](https://speakerdeck.com/schisamo/eat-the-whole-bowl-building-a-full-stack-installer-with-omnibus)
+
+- [Video](http://www.youtube.com/watch?v=q8iJAntXCNY)
+- [Slides](https://speakerdeck.com/schisamo/eat-the-whole-bowl-building-a-full-stack-installer-with-omnibus)
 
 This project is managed by the CHEF Release Engineering team. For more information on the Release Engineering team's contribution, triage, and release process, please consult the [CHEF Release Engineering OSS Management Guide](https://docs.google.com/a/opscode.com/document/d/1oJB0vZb_3bl7_ZU2YMDBkMFdL-EWplW1BJv_FXTUOzg/edit).
 
+## Prerequisites
 
-Prerequisites
--------------
 Omnibus is designed to run with a minimal set of prerequisites. You will need the following:
 
-- Ruby 2.0.0+
+- Ruby 2.2+
 - Bundler
 
+## Get Started
 
-Get Started
------------
 Omnibus provides both a DSL for defining Omnibus projects for your software, as well as a command-line tool for generating installer artifacts from that definition.
 
 To get started, install Omnibus locally on your workstation.
@@ -53,21 +48,20 @@ More details can be found in the generated project's README file.
 
 Omnibus determines the platform for which to build an installer based on **the platform it is currently running on**. That is, you can only generate a `.deb` file on a Debian-based system. To alleviate this caveat, the generated project includes a [Test Kitchen](http://kitchen.ci) setup suitable for generating a series of Omnibus projects.
 
+## More documentation
 
-More documentation
-------------------
-- [Building on Debian](docs/Building on Debian.md)
-- [Building on OSX](docs/Building on OSX.md)
-- [Building on RHEL](docs/Building on RHEL.md)
-- [Building on Windows](docs/Building on Windows.md)
-- [Build Cache](docs/Build Cache.md)
+- [Building on Debian](docs/Building%20on%20Debian.md)
+- [Building on OSX](docs/Building%20on%20OSX.md)
+- [Building on RHEL](docs/Building%20on%20RHEL.md)
+- [Building on Windows](docs/Building%20on%20Windows.md)
+- [Build Cache](docs/Build%20Cache.md)
 
+## Configuration DSL
 
-Configuration DSL
------------------
 Though the template project will build, it will not do anything exciting. For that, you need to use the Omnibus DSL to define the specifics of your application.
 
 ### Config
+
 If present, Omnibus will use a top-level configuration file named `omnibus.rb` at the root of your repository. This file is loaded at runtime and includes a number of configuration tunables. Here is an example:
 
 ```ruby
@@ -84,6 +78,8 @@ use_git_caching false
 use_s3_caching true
 s3_access_key  ENV['S3_ACCESS_KEY']
 s3_secret_key  ENV['S3_SECRET_KEY']
+# You can use the Shared Credentials files in place of the s3_access_key and s3_secret_key.
+#s3_profile    ENV['S3_PROFILE']
 s3_bucket      ENV['S3_BUCKET']
 ```
 
@@ -102,6 +98,7 @@ $ bin/omnibus --override use_git_caching:false
 ```
 
 ### Projects
+
 A Project DSL file defines your actual application; this is the thing you are creating a full-stack installer for in the first place. It provides a means to define the dependencies of the project (again, as specified in Software DSL definition files), as well as ways to set installer package metadata.
 
 All project definitions must be in the `config/projects` directory of your Omnibus repository.
@@ -120,24 +117,22 @@ dependency "chef"
 
 Some DSL methods available include:
 
-| DSL Method        | Description                                 |
-| :---------------: | --------------------------------------------|
-| `name`            | The name of the project                     |
-| `install_dir`     | The desired install location of the package |
-| `build_version`   | The package version                         |
-| `build_iteration` | The package iteration number                |
-| `dependency`      | An Omnibus software-defined component to include in this package |
-| `package`         | Invoke a packager-specific DSL              |
-| `compress`        | Invoke a compressor-specific DSL            |
-
-By default a timestamp is appended to the build_version.  You can turn
-this behavior off by setting `append_timestamp` to `false` in your
-configuration file or using `--override append_timestamp:false` at the
-command line.
+DSL Method        | Description
+:---------------- | ----------------------------------------------------------------
+`name`            | The name of the project
+`install_dir`     | The desired install location of the package
+`build_version`   | The package version
+`build_iteration` | The package iteration number
+`dependency`      | An Omnibus software-defined component to include in this package
+`package`         | Invoke a packager-specific DSL
+`compress`        | Invoke a compressor-specific DSL
+
+By default a timestamp is appended to the build_version. You can turn this behavior off by setting `append_timestamp` to `false` in your configuration file or using `--override append_timestamp:false` at the command line.
 
 For more information, please see the [`Project` documentation](http://rubydoc.info/github/opscode/omnibus/Omnibus/Project).
 
 ### Software
+
 Omnibus "software" files define individual software components that go into making your overall package. They are the building blocks of your application. The Software DSL provides a way to define where to retrieve the software sources, how to build them, and what dependencies they have. These dependencies are also defined in their own Software DSL files, thus forming the basis for a dependency-aware build ordering.
 
 All Software definitions should go in the `config/software` directory of your Omnibus project repository.
@@ -165,41 +160,42 @@ end
 
 Some of the DSL methods available include:
 
-| DSL Method        | Description                                |
-| :---------------: | -------------------------------------------|
-| `name`            | The name of the software component (this should come first) |
-| `default_version` | The version of the software component      |
-| `source`          | Directions to the location of the source   |
-| `dependency`      | An Omnibus software-defined component that this software depends on |
-| `relative_path`   | The relative path of the extracted tarball |
-| `build`           | The build instructions                     |
-
-For more DSL methods, please consult the [`Software` documentation](http://rubydoc.info/github/opscode/omnibus/Omnibus/Software).
-
-Additionally, there are a number of DSL methods avaiable inside the `build` block:
-
-| DSL Method          | Description                                |
-| :-----------------: | -------------------------------------------|
-| `command`           | Execute a single shell command             |
-| `make`              | Run make (with or without args), using gmake when appropriate |
-| `patch`             | Apply a patch from disk                    |
-| `workers`           | The maximum number of builders             |
-| `windows_safe_path` | Format the path to be safe for shelling out on Windows |
-| `ruby`              | Execute the code as the embedded Ruby      |
-| `gem`               | Execute the code as the embedded Rubygems  |
-| `bundle`            | Execute the code as the embedded Bundler   |
-| `rake`              | Execute the code as the embedded Rake gem  |
-| `block`             | Execute Ruby block at build time           |
-| `erb`               | Render the given ERB template              |
-| `mkdir`             | Create the given directory                 |
-| `touch`             | Create the given empty file                |
-| `delete`            | Remove the given file or directory         |
-| `copy`              | Copy a to b                                |
-| `move`              | Move a to b                                |
-| `link`              | Link a to b                                |
-| `sync`              | Copy all files from a to b, removing any union files |
-
-For more DSL methods, please consult the [`Builder` documentation](http://rubydoc.info/github/opscode/omnibus/Omnibus/Builder).
+DSL Method        | Description
+:---------------- | -------------------------------------------------------------------
+`name`            | The name of the software component (this should come first)
+`default_version` | The version of the software component
+`source`          | Directions to the location of the source
+`dependency`      | An Omnibus software-defined component that this software depends on
+`relative_path`   | The relative path of the extracted tarball
+`build`           | The build instructions
+
+For more DSL methods, please consult the [`Software` documentation](http://rubydoc.info/github/chef/omnibus/Omnibus/Software).
+
+Additionally, there are a number of DSL methods available inside the `build` block:
+
+DSL Method          | Description
+:------------------ | -------------------------------------------------------------
+`command`           | Execute a single shell command
+`make`              | Run make (with or without args), using gmake when appropriate
+`patch`             | Apply a patch from disk
+`workers`           | The maximum number of builders
+`windows_safe_path` | Format the path to be safe for shelling out on Windows
+`ruby`              | Execute the code as the embedded Ruby
+`gem`               | Execute the code as the embedded Rubygems
+`bundle`            | Execute the code as the embedded Bundler
+`rake`              | Execute the code as the embedded Rake gem
+`block`             | Execute Ruby block at build time
+`erb`               | Render the given ERB template
+`mkdir`             | Create the given directory
+`touch`             | Create the given empty file
+`delete`            | Remove the given file or directory
+`strip`             | Strip symbols from binaries on a given file or directory
+`copy`              | Copy a to b
+`move`              | Move a to b
+`link`              | Link a to b
+`sync`              | Copy all files from a to b, removing any union files
+
+For more DSL methods, please consult the [`Builder` documentation](http://rubydoc.info/github/chef/omnibus/Omnibus/Builder).
 
 You can support building multiple versions of the same software in the same software definition file using the `version` method and giving a block:
 
@@ -221,6 +217,7 @@ end
 Since the software definitions are simply ruby code, you can conditionally execute anything by wrapping it with pure Ruby that tests for the version number.
 
 #### Sharing software definitions
+
 The easiest way to share organization-wide software is via bundler and Rubygems. For an example software repository, look at Chef's [omnibus-software](https://github.com/chef/omnibus-software). For more information, please see the [Rubygems documentation](http://guides.rubygems.org/publishing/).
 
 It is recommended you use bundler to pull down these gems (as bundler also permits pulling software directly from GitHub):
@@ -244,7 +241,6 @@ local_software_dirs %w(/path/to/software /other/path/to/software)
 
 For all of these paths, **order matters**, so it is possible to depend on local software version while still retaining a remote software repo. Given the above example, Omnibus will search for a software definition named `foo` in this order:
 
-
 ```text
 $PWD/config/software/foo.rb
 /path/to/software/config/software/foo.rb
@@ -255,62 +251,48 @@ $PWD/config/software/foo.rb
 
 The first instance of `foo.rb` that is encountered will be used. Please note that **local** (vendored) softare definitions take precedence!
 
-Version Manifest
-----------------
+## Version Manifest
 
-Git-based software definitions may specify branches as their
-default_version. In this case, the exact git revision to use will be
-determined at build-time unless a project override (see below) or
-external version manifest is used. To generate a version manifest use
-the `omnibus manifest` command:
+Git-based software definitions may specify branches as their default_version. In this case, the exact git revision to use will be determined at build-time unless a project override (see below) or external version manifest is used. To generate a version manifest use the `omnibus manifest` command:
 
 ```
 omnibus manifest PROJECT -l warn
 ```
 
-This will output a JSON-formatted manifest containing the resolved
-version of every software definition.
+This will output a JSON-formatted manifest containing the resolved version of every software definition.
 
-Whitelisting Libraries
-----------------------
+## Whitelisting Libraries
 
-Sometimes a platform has libraries that need to be whitelisted so the healthcheck
-can pass. The whitelist found in the [healthcheck](https://github.com/chef/omnibus/blob/master/lib/omnibus/health_check.rb)
-code comprises the minimal required for successful builds on supported platforms.
+Sometimes a platform has libraries that need to be whitelisted so the healthcheck can pass. The whitelist found in the [healthcheck](https://github.com/chef/omnibus/blob/master/lib/omnibus/health_check.rb) code comprises the minimal required for successful builds on supported platforms.
+
+To add your own whitelisted library, simply add the a regex to your software definition in your omnibus project as follows:
 
-To add your own whitelisted library, simply add the a regex to your software
-definition in your omnibus project as follows:
 ```
 whitelist_file /libpcrecpp\.so\..+/
 ```
-It is typically a good idea to add a conditional to whitelist based on the specific
-platform that requires it.
 
-*Warning: You should only add libraries to the whitelist that are guaranteed to
-be on the system you install to; if a library comes from a non-default package
-you should instead build it into the package.*
+It is typically a good idea to add a conditional to whitelist based on the specific platform that requires it.
+
+_Warning: You should only add libraries to the whitelist that are guaranteed to be on the system you install to; if a library comes from a non-default package you should instead build it into the package._
+
+## Changelog
 
-Changelog
----------
-STATUS: *EXPERIMENTAL*
+STATUS: _EXPERIMENTAL_
 
-`omnibus changelog generate` will generate a changelog for an omnibus
-project.  This command currently assumes:
+`omnibus changelog generate` will generate a changelog for an omnibus project. This command currently assumes:
 
 - version-manifest.json is checked into the project root
 - the project is a git repository
 - each version is tagged with a SemVer compliant annotated tag
 - Any git-based sources are checked out at ../COMPONENT_NAME
-- Any commit message line prepended with ChangeLog-Entry: should be
-  added to the changelog.
+- Any commit message line prepended with ChangeLog-Entry: should be added to the changelog.
 
-These assumptions *will* change as we determine what works best for a
-number of our projects.
+These assumptions _will_ change as we determine what works best for a number of our projects.
 
+## Caveats
 
-Caveats
--------
 ### Overrides
+
 The project definitions can override specific software dependencies by passing in `override` to use the correct version:
 
 ```ruby
@@ -326,6 +308,7 @@ dependency "chef"
 **The overridden version must be defined in the associated software!**
 
 ### Debugging
+
 By default, Omnibus will log at the `warn` level. You can override this by passing the `--log-level` flag to your Omnibus call:
 
 ```shell
@@ -333,15 +316,19 @@ $ bin/omnibus build <project> --log-level info # or "debug"
 ```
 
 ### Git caching
+
 by default, Omnibus caches compiled software definitions, so n+1 Omnibus project builds are much faster. This functionality can be disabled by adding the following to your `omnibus.rb`:
 
 ```ruby
 use_git_caching false
 ```
 
+## Contributing
+
+For information on contributing to this project see <https://github.com/chef/chef/blob/master/CONTRIBUTING.md>
+
+## License
 
-License
--------
 ```text
 Copyright 2012-2016 Chef Software, Inc.
 
@@ -357,3 +344,7 @@ 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.
 ```
+
+[appveyor]: https://ci.appveyor.com/project/chef/omnibus
+[gem]: https://rubygems.org/gems/omnibus
+[travis]: https://travis-ci.org/chef/omnibus