capistrano 3.3.5 → 3.16.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: c070509b8ffb4ed5817485be5837b7f33b98a99c
-  data.tar.gz: 08c9555174d74715e0615738d7deb4f472e77595
+SHA256:
+  metadata.gz: 34b4f8bf408d7e3aeeb3adcb61a44af437f1015c2206d41dae97602445411558
+  data.tar.gz: 99d880dedf50994b9e8ac61d43ed3ad5a7a2e11a84269a085f59bc463aff3407
 SHA512:
-  metadata.gz: 338b464cb5443d6ce1f63a121637c5d3acb5c8b956add0b7a0af1fbd27d92d57ebf34ecb052dccdd6ff1d7fb1579cbc54027a9c4d219b6dc269998af6457bdfb
-  data.tar.gz: d4e7ab991450dc7f6072137b09e10e5500cbbb79c536896b8b4228a4976cd6e7a37dd57970d3908662d2083e78457a4376d45d0144e753bc13a50f307cfc9544
+  metadata.gz: b07d663529584f6a0fb8b324f55cc4033eabb6812d7212e8dfc5dff4c84a2c6afd038341070811370d92bbbff5fbc93836118e3d5be949a48b47e1c7af5099cf
+  data.tar.gz: a0cd52b0c258c527320fec4057b98014856ebbecebfe187ac29f88f3c562843882457cfcfb33addfe2c17a4c6d0b4b3af625941812ef9bf779998cc4d1aa6cb3

data/.github/issue_template.md

@@ -0,0 +1,19 @@
+**Important:** GitHub issues are for feature requests or bug reports. The Capistrano team recommends you use [Stack Overflow](http://stackoverflow.com/questions/tagged/capistrano) for general questions. For more details, please see our [contribution policy](https://github.com/capistrano/capistrano/blob/master/CONTRIBUTING.md).
+
+---
+
+### Steps to reproduce
+If reasonable, you can help by creating a Capistrano skeleton example project which reproduces the issue you are seeing. You can then upload the individual files to a GitHub Gist or a GitHub project. Others can simply modify the configuration to point at a test server/repository of their own. Often times, an issue is resolved simply by making this test case.
+
+An example test case is here: https://gist.github.com/will-in-wi/527327e31af30b3eae2068e2965be05b
+
+### Expected behavior
+Tell us what should happen
+
+### Actual behavior
+Tell us what happens instead
+
+### System configuration
+Please link to the output of `cap <stage> doctor` in a GitHub Gist.
+
+Thanks for helping improve Capistrano!

data/.github/pull_request_template.md

@@ -0,0 +1,22 @@
+### Summary
+
+(Guidelines for creating a bug report are available
+here: https://github.com/capistrano/capistrano/blob/master/DEVELOPMENT.md)
+
+Provide a general description of the code changes in your pull
+request... were there any bugs you had fixed? If so, mention them. If
+these bugs have open GitHub issues, be sure to tag them here as well,
+to keep the conversation linked together.
+
+### Short checklist
+
+- [ ] Did you run `bundle exec rubocop -a` to fix linter issues?
+- [ ] If relevant, did you create a test?
+- [ ] Did you confirm that the RSpec tests pass?
+
+### Other Information
+
+If there's anything else that's important and relevant to your pull
+request, mention that information here.
+
+Thanks for helping improve Capistrano!

data/.github/release-drafter.yml

@@ -0,0 +1,17 @@
+name-template: "$NEXT_PATCH_VERSION"
+tag-template: "v$NEXT_PATCH_VERSION"
+categories:
+  - title: "⚠️ Breaking Changes"
+    label: "⚠️ Breaking"
+  - title: "✨ New Features"
+    label: "✨ Feature"
+  - title: "🐛 Bug Fixes"
+    label: "🐛 Bug Fix"
+  - title: "📚 Documentation"
+    label: "📚 Docs"
+  - title: "🏠 Housekeeping"
+    label: "🏠 Housekeeping"
+change-template: "- $TITLE (#$NUMBER) @$AUTHOR"
+no-changes-template: "- No changes"
+template: |
+  $CHANGES

data/.github/workflows/push.yml

@@ -0,0 +1,12 @@
+on: push
+name: Push
+jobs:
+  draftRelease:
+    name: Draft Release
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@master
+      - name: Draft Release
+        uses: toolmantim/release-drafter@v5.2.0
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

data/.gitignore

@@ -1,10 +1,15 @@
 *.gem
 *.rbc
+*.swp
 .bundle
 .config
+.rspec
+.rspec-local
+.ruby-version
 .yardoc
 Gemfile.lock
 InstalledFiles
+_site
 _yardoc
 coverage
 doc/
@@ -12,11 +17,9 @@ lib/bundler/man
 pkg
 rdoc
 spec/reports
+tags
 test/tmp
 test/version_tmp
 tmp
-.rspec-local
-.ruby-version
-_site
-.rspec
-*.swp
+/docs/_site/
+vendor/

data/.rubocop.yml

@@ -0,0 +1,62 @@
+AllCops:
+  DisplayCopNames: true
+  DisplayStyleGuide: true
+  TargetRubyVersion: 2.0
+
+Lint/AmbiguousBlockAssociation:
+  Enabled:
+    false
+Metrics/BlockLength:
+  Exclude:
+    - "*.gemspec"
+    - "spec/**/*"
+    - "lib/**/*.rake"
+Style/BarePercentLiterals:
+  EnforcedStyle: percent_q
+Style/ClassAndModuleChildren:
+  Enabled: false
+Style/DoubleNegation:
+  Enabled: false
+Style/FileName:
+  Exclude:
+    - "Dangerfile"
+Style/IndentHeredoc:
+  Enabled: false
+Style/SpaceAroundEqualsInParameterDefault:
+  EnforcedStyle: no_space
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+Style/TrivialAccessors:
+  AllowPredicates: true
+Style/PercentLiteralDelimiters:
+  Enabled: false
+Style/SingleLineBlockParams:
+  Enabled: false
+Style/ModuleFunction:
+  Enabled: false
+
+# Enable someday
+Style/Documentation:
+  Enabled: false
+
+# Needs refactors
+Metrics/PerceivedComplexity:
+  Enabled: false
+Metrics/CyclomaticComplexity:
+  Enabled: false
+Metrics/MethodLength:
+  Enabled: false
+Style/PredicateName:
+  Enabled: false
+Metrics/LineLength:
+  Enabled: false
+Metrics/AbcSize:
+  Enabled: false
+Style/PerlBackrefs:
+  Enabled: false
+Metrics/ClassLength:
+  Enabled: false
+Metrics/ModuleLength:
+  Enabled: false
+Style/AccessorMethodName:
+  Enabled: false

data/.travis.yml

@@ -1,12 +1,30 @@
 language: ruby
 rvm:
-  - 2.1.0
-  - 2.0.0
-  - 1.9.3
-  - rbx-2
-script: bundle exec rake spec
+  - 3.0
+  - 2.7
+  - 2.6
+  - 2.5
+  - 2.4
+  - 2.3
+  - 2.2
+  - 2.1
+  - 2.0
+matrix:
+  # Rubinius periodically fails in general, and it always segfaults for RuboCop
+  # in particular. Until we figure out how to make it work consistently, allow
+  # it to fail without breaking the build.
+  allow_failures:
+    - rvm: rbx-2
+  include:
+    - rvm: rbx-2
+      script: bundle exec rake spec
+    # Run Danger only once, on 2.5
+    - rvm: 2.5
+      before_script: bundle exec danger
+
+script: bundle exec rake spec rubocop
 install: bundle install --jobs=1
 cache: bundler
 branches:
-  except:
-    - legacy-v2
+  only:
+    - master

data/CHANGELOG.md

@@ -1,273 +1 @@
-# Capistrano 3.x Changelog
-
-Reverse Chronological Order:
-
-## master
-
-https://github.com/capistrano/capistrano/compare/v3.3.5...HEAD
-
-## `3.3.5`
-
-https://github.com/capistrano/capistrano/compare/v3.3.4...v3.3.5
-
-* Fixed setting properties twice when creating new server. See [issue
-  #1214](https://github.com/capistrano/capistrano/issues/1214) (@ayastreb)
-
-## `3.3.4`
-
-https://github.com/capistrano/capistrano/compare/v3.3.3...v3.3.4
-
-* Minor changes:
-  * Rely on a newer version of capistrano-stats with better privacy (@leehambley)
-  * Fix cucumber spec for loading tasks from stage configs (@sponomarev)
-  * Minor documentation fixes (@deeeki, @seuros, @andresilveira)
-  * Spec improvements (@dimitrid, @sponomarev)
-  * Fix to CLI flags for git-ls-remote (@dimitrid)
-
-## `3.3.3`
-
-https://github.com/capistrano/capistrano/compare/v3.2.1...v3.3.3
-
-* Enhancement (@townsen)
-  * Added the variable `:repo_tree` which allows the specification of a sub-tree that
-    will be extracted from the repository. This is useful when deploying a project
-    that lives in a subdirectory of a larger repository.
-    Implemented only for git and hg.
-    If not defined then the behaviour is as previously and the whole repository is
-    extracted (subject to git-archive `.gitattributes` of course).
-
-* Enhancement (@townsen): Remove unnecessary entries from default backtrace
-
-    When the `--backtrace` (or `--trace`) command line option is not supplied
-    Rake lowers the noise level in exception backtraces by building
-    a regular expression containing all the system library paths and
-    using it to exclude backtrace entries that match.
-
-    This does not always go far enough, particularly in RVM environments when
-    many gem paths are added. This commit reverses that approach and _only_
-    include backtrace entries that fall within the Capfile and list of tasks
-    imported thereafter. This makes reading exceptions much easier on the eye.
-
-    If the full unexpurgated backtrace is required then the --backtrace
-    and --trace options supply it as before.
-
-* Disable loading stages configs on `cap -T` (@sponomarev)
-* Track (anonymous) statistics, see https://github.com/capistrano/stats
-
-* Enhancements (@townsen)
-  * Fix matching on hosts with custom ports or users set
-  * Previously filtering would affect any generated configuration files so that
-    files newly deployed would not be the same as those on the hosts previously
-    deployed (and now excluded by filters). This is almost certainly not what is
-    wanted: the filters should apply only to the on() method and thus any
-    configuration files deployed will be identical across the set of servers
-    making up the stage.
-  * Host and Role filtering now affects only `on()` commands
-    and not the `roles()`, `release_roles()` and `primary()` methods.
-  * This applies to filters defined via the command line, the environment
-    and the :filter variable.
-  * Filtering now supports Regular expressions
-  * This change _could_ cause existing scripts that use filtering and depend on
-    the old behaviour to fail, though it is unlikely. Users who rely on
-    filtering should check that generated configuration files are correct, and
-    where not introduce server properties to do the filtering. For example, if a
-    filter was used to specify an active subset of servers (by hostname), it should
-    be removed and replaced with an 'active' property (set to true or false) on the
-    server definitions. This keeps the stage file as the canonical model of the
-    deployment environment.
-
-  * See the documentation in the README.md file
-
-* Enhancements (@townsen)
-  * Added set_if_empty method to DSL to allow conditional setting
-  * Altered standard Capistrano defaults so that they are not set
-    at the start of a stage if they have been previously set. This
-    allows variables like :default_env to be set in deploy.rb.
-  * Deep copy properties added using the 'roles' keyword
-  * If a property exists on a server when another definition is
-    encountered and is an Array, Set or Hash then add the new values
-
-    This allows roles to specify properties common to all servers and
-    then for individual servers to modify them, keeping things DRY
-
-Breaking Changes:
-  * By using Ruby's noecho method introduced in Ruby version 1.9.3, we dropped support for Ruby versions prior to 1.9.3. See [issue #878](https://github.com/capistrano/capistrano/issues/878) and [PR #1112](https://github.com/capistrano/capistrano/pull/1112) for more information. (@kaikuchn)
-
-* Bug Fixes:
-  * Fixed compatibility with FreeBSD tar (@robbertkl)
-  * remote_file can be used inside a namespace (@mikz)
-
-* Minor Changes
-  * Remove -v flag from mkdir call. (@caligo-mentis)
-  * Capistrano now allows to customize `local_user` for revision log. (@sauliusgrigaitis)
-  * Added tests for after/before hooks features (@juanibiapina, @miry)
-  * Added `--force` flag to `svn export` command to fix errors when the release directory already exists.
-  * Improved the output of `cap --help`. (@mbrictson)
-  * Cucumber suite now runs on the latest version of Vagrant (@tpett)
-  * The `ask` method now supports the `echo: false` option. (@mbrictson, @kaikuchn)
-  * Cucumber scenario improvements (@bruno-)
-  * Added suggestion to Capfile to use 'capistrano-passenger' gem, replacing suggestion in config/deploy.rb to re-implement 'deploy:restart' (@betesh)
-  * Updated svn fetch_revision method to use `svnversion`
-  * `cap install` no longer overwrites existing files. (@dmarkow)
-
-## `3.2.1`
-
-https://github.com/capistrano/capistrano/compare/v3.2.0...v3.2.1
-
-* Bug Fixes:
-  * 3.2.0 introduced some behaviour to modify the way before/after hooks were called, to allow the optional
-    preservation of arguments to be passed to tasks. This release reverts that commit in order to restore
-    original functionality, and fix (fairly serious) bugs introduced by the refactoring.
-
-* Minor changes:
-  * Update dsl#local_user method and add test for it. (@bruno-)
-  * Revert short sha1 revision with git. (@blaugueux)
-  * Changed asking question to more standard format (like common unix commandline tools) (@sponomarev)
-  * Fixed typos in the README. (@sponomarev)
-  * Added `keys` method to Configuration to allow introspection of configuration options. (@juanibiapina)
-  * Improve error message when git:check fails (raise instead of silently `exit 1`) (@mbrictson)
-
-## `3.2.0`
-
-The changelog entries here are incomplete, because many authors choose not to
-be credited for their work, check the tag comparison link for Github.
-
-https://github.com/capistrano/capistrano/compare/v3.1.0...v3.2.0
-
-* Minor changes:
-  * Added `keys` method to Server properties to allow introspection of automatically added
-    properties.
-  * Compatibility with Rake 10.2.0 - `ensure_task` is now added to `@top_level_tasks` as a string. (@dmarkow)
-  * Amended the git check command, "ls-remote", to use "-h", limiting the list to refs/heads
-
-## `3.1.0`
-
-https://github.com/capistrano/capistrano/compare/v3.0.1...v3.1.0
-
-Breaking changes:
-
-  * `deploy:restart` task **is no longer run by default**.
-    From this version, developers who restart the app on each deploy need to declare it in their deploy flow (eg `after 'deploy:publishing', 'deploy:restart'`)
-    or, for passenger applications, use the capistrano-passenger gem.
-
-    Please, check https://github.com/capistrano/capistrano/commit/4e6523e1f50707499cf75eb53dce37a89528a9b0 for more information. (@kirs)
-
-* Minor changes
-  * Tasks that used `linked_dirs` and `linked_files` now run on all roles, not just app roles (@mikespokefire)
-  * Tasks `deploy:linked_dirs`, `deploy:make_linked_dirs`, `deploy:linked_files`, `deploy:cleanup_rollback`,
-    `deploy:log_revision` and `deploy:revert_release` now use `release_roles()` not `roles()` meaning that they
-    will only run on servers where the `no_release` property is not falsy. (@leehambley)
-  * Fixed bug when `deploy:cleanup` was executed twice by default (@kirs)
-  * Config location can now be changed with `deploy_config_path` and `stage_config_path` options (@seenmyfate)
-  * `no_release` option is now available (@seenmyfate)
-  * Raise an error if developer tries to define `:all` role, which is reserved (@kirs)
-  * `deploy:failed` hook was added to add some custom behaviour on failed deploy (@seenmyfate)
-  * Correctly infer namespace in task enhancements (@seenmyfate)
-  * Add SHA to revision log (@blackxored)
-  * Allow configuration of multiple servers with same hostname but different ports (@rsslldnphy)
-  * Add command line option to control role filtering (@andytinycat)
-  * Make use of recent changes in Rake to over-ride the application name (@shime)
-  * Readme corrections (@nathanstitt)
-  * Allow roles to be fetched with a variable containing an array (@seenmyfate)
-  * Improve console (@jage)
-  * Add ability to filter tasks to specific servers (host filtering). (@andytinycat)
-  * Add a command line option to control role filter (`--roles`) (@andytinycat)
-  * Use an SCM object with a pluggable strategy (@coffeeaddict)
-
-Big thanks to @Kriechi for his help.
-
-## `3.0.1`
-
-https://github.com/capistrano/capistrano/compare/v3.0.0...v3.0.1
-
-  * `capify` not listed as executable (@leehambley)
-  * Confirm license as MIT (@leehambley)
-  * Move the git ssh helper to application path (@mpapis)
-
-## `3.0.0`
-
-https://github.com/capistrano/capistrano/compare/2.15.5...v3.0.0
-
-If you are coming here to wonder why your Capfile doesn't work anymore, please
-vendor lock your Capistrano at 2.x, whichever version was working for you
-until today.
-
-Capistrano 3 is a ground-up rewrite with modularity, stability, speed and
-future proofing in mind. It's a big change, but now the code is 10x smaller,
-runs faster, is easier to read, and quicker to extend. In the reduction we've
-come up with a great gem based modular system for plugins and we're really
-proud of this release.
-
-The 3.0.0 release contains 38 patches from the following amazing people:
-
-  * Tom `seenmyfate` Clements: more than 28 patches including cucumber integration tests! Not to
-    mention Rails asset pipeline code, and bundler integrations.
-  * Lee Hambley: Small changes around compatibility and log formatting
-  * Kir Shatrov: for improvements in the core to make it easier to write extensions, for
-    improving documentation, and for effectively building the chruby, rvm and rbenv integrations.
-  * Michael Nikitochkin: Fixing a bug around linked files and directories.
-  * Jack Thorne: for improvements to the default `Capfile` to fix some bad example syntax.
-  * Erik Hetzner: for (what looks like great) work on the Mercurial (Hg) support. The Hg and Git
-    source control mechanisms do not work the same way, but rather lean on the strengths of the
-    underlying tools.
-
-    (If I missed anyone, I'm sorry, your contributions have been awesome)
-
-The 2.x branch of code is now no longer maintained. Towards the end of it's
-useful life there were an increasing number of features and pieces of code
-which didn't make sense for certain groups of people, in certain situations,
-leading a to a ping-pong tennis effect with pull requests every few weeks
-"fixing" a use-case which had already been "fixed" shortly before. As many of
-the use-cases are outside the scope of the testing environments I (and by
-extension the trusted contributors and IRC regulars) were able to test for.
-
-There's a more extensive post about my failure to be able to keep up with the
-demands of maintaining v2 whilst trying to build something which is appropriate
-for the current landscape. If you are affected by the unsupported 2 branch,
-please contact me (Lee Hambley) to discuss how my company can help support you.
-Otherwise, please try v3, we're sure you'll like it, and the code is designed
-to be so simple that anyone can work on it.
-
-## `3.0.0.pre14`
-
- * Thanks to numerous contributors, in particular (@teohm) for a series of improvements.
-
-## `3.0.0.pre13`
-
- * Fixed typos in the Capfile. (@teohm)
- * Allow setting SSH options globally. (@korin)
- * Change the flow (and hooks) see http://www.capistranorb.com/documentation/getting-started/flow/ for more information. Requires min SSHKit 0.0.34 (@teohm)
- * Fix sorting releases in lexicographical order (@teohm)
-
-## `3.0.0.pre12`
-
- * `capistrano/bundler` now runs bundle on all roles, this addresses the same
-   issue as the related changes in `pre11`. (@leehambley)
-
-## `3.0.0.pre11`
-
- * Some deploy.rake tasks now apply to all servers, not expecting a
-   primary(:app) server which may not exist in all deploy environments.
-   (@leehambley).
-
-## `3.0.0.pre10`
-
- * Fixes pre9.
-
-## `3.0.0.pre9`
-
- * Fixes a syntax error introduced with filtering (with tests) introduced in
-   `pre8`. (@leehambley)
-
-## `3.0.0.pre8`
-
- * Fixed a syntax where `roles(:foo, :bar)` was being mistaken as a filter
-   (roles(:foo, :bar => nil). The correct syntax to use is: roles([:foo,:bar])
-   (@leehambley)
-
-## `3.0.0.pre7`
-
- * Fix Git https authentication. (@leehambley)
- * Capfile template fixes (repo/repo_url) (@teohm)
- * Readme Fixes (@ffmike, @kejadlen, @dwickwire)
- * Fix the positioning of the bundler hook, now immediately after finalize. (@teohm)
+Release notes for this project are kept here: https://github.com/capistrano/capistrano/releases