kotovalexarian-likes-github/capistrano
1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Code Releases Activity
capistrano/CHANGELOG.md
Hartog C. de Mik e7a95e5872 Use an SCM object with a pluggable strategy 
I've taken the responsibility for executing scm commands away from the
rake tasks and have placed them in an SCM object. This object can be
loaded with any given strategy.

A default strategy is supplied (the commands as they where in the rake
tasks)

Moved Hg to the new strategy pattern
2013-12-11 15:09:03 +01:00

5.6 KiB
Raw Blame History

Capistrano 3.x Changelog

Reverse Chronological Order:

master

  • Add a command line option to control role filter (--roles) (@andytinycat)
  • Use an SCM object with a pluggable strategy

3.1.0 (not released)

  • 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)
  • 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 (@kirs)
  • 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:fallback 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)

3.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

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 dicsuss 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

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)