https://github.com/mwotton/deployer

deployer for compile-based systems
https://github.com/mwotton/deployer

Last synced: about 1 month ago
JSON representation

deployer for compile-based systems

• Host: GitHub
• URL: https://github.com/mwotton/deployer
• Owner: mwotton
• Created: 2012-04-21T21:50:59.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2012-04-21T22:17:40.000Z (over 12 years ago)
• Last Synced: 2024-10-27T18:28:28.906Z (3 months ago)
• Homepage:
• Size: 97.7 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
========

Deployer

========

Some vague ruminations on the flows we'd like to see from a dev point

of view.

Dev experience

==============

    $ # hack hack hack

    $ git commit . -m 'my awesome commits'

    $ git push buildbot master

      # wait a bit

      To git@buildbot:my_awesome_project.git

      ! [rejected]        master -> master (non-fast forward)

      error: failed to push some refs to 'git@buildbot:my_awesome_project.git'

      - your code didn't compile/failed some tests/smells funny

    $ # grumble grumble

    $ # hack hack hack

    $ git commit . -m 'fix up my awful commits'

    $ git push buildbot master

    $ # wait

      Build accepted! Merging to github, tagging as #abcd1234, deploying to staging

    $ # go off and check staging

    $  # all good!

# less sure about this stuff, open to comment

    $ prod_deploy abcd1234

    $ # check - oh shit, we used the wrong creds! Abort, abort

    $ prod_rollback

 

Implementation notes

====================

this should work for multiple repos. might be nice to have a

new_channel script that automatically sets up a project with a cabal

file, buildbot endpoint, etc etc etc.

Author

======

Mark Wotton @mwotton