Permalink
Commits on Dec 11, 2013
  1. Merge pull request #84 from cloudbees/master

    rtyler committed Dec 11, 2013
    Don't force port 22 if the port is not set.
Commits on Sep 27, 2013
  1. Don't force port 22 if the port is not set.

    kohsuke committed Sep 27, 2013
    In this way ~/.ssh/config can take effect
Commits on Aug 15, 2013
  1. Merge pull request #83 from cloudbees/master

    rtyler committed Aug 15, 2013
    Only import the keypair if it doesn't exist
Commits on Jul 3, 2013
  1. Merge pull request #82 from cloudbees/master

    rtyler committed Jul 3, 2013
    Adds a new box type 'existing'
  2. Added a new box type 'existing'

    kohsuke committed Jul 3, 2013
    This box type is useful for controlling existing non-cloud machines
    under blimpy
Commits on Jul 1, 2013
  1. Sanitize hostnames for keypairs

    rtyler committed Jul 1, 2013
    Fixes #76
Commits on May 17, 2013
Commits on Apr 26, 2013
  1. Merge pull request #79 from jblaine/master

    rtyler committed Apr 26, 2013
    Use Puppetlabs repo site, not gems
Commits on Apr 25, 2013
  1. Use Puppetlabs repo site, not gems

    jblaine committed Apr 25, 2013
    Tested with "precise" 12.x ships, should adapt to any Ubuntu
    on its own. Targets Puppet 2.7.* as the gem install used to.
  2. Intro .provision_on_start flag for ships

    jblaine committed Apr 25, 2013
    Allows control over when the livery provisioning happens for
    ships. This was needed because sometimes we don't want to
    provision (Puppet) until all ships are up and we know their
    hostnames in AWS, etc.
Commits on Mar 30, 2013
  1. Merge pull request #75 from cloudbees/master

    rtyler committed Mar 30, 2013
    Reverting wait_for_ssh command
  2. Revert "Fixing the unit test failure"

    kohsuke committed Mar 30, 2013
    This reverts commit 8827307.
Commits on Mar 29, 2013
  1. Revisiting 8b38008

    kohsuke committed Mar 29, 2013
    (04:25:26 PM) rtyler: kohsuke: so `blimpy ssh` is going to return immediately now?
    (04:25:41 PM) kohsuke: yes, it fails if ssh fails
    (04:26:09 PM) ***rtyler is a bit confused
    (04:26:14 PM) rtyler: this seems like a big UX change then
    (04:26:21 PM) ***rtyler should read more carefully
    (04:27:13 PM) kohsuke: Yes, modifying a test case made me wonder if there's a better way to do it
    (04:28:00 PM) kohsuke: (though in practice you wouldn't see any change as "blimpy provision" does wait for ssh to come online)
    (04:28:13 PM) rtyler: but a `blimpy ssh` won't log me into the machine?
    (04:28:51 PM) kohsuke: I think just reporting ">> Connecting: SHIPNAME..." if the first attempt fails would be sufficient
    (04:29:25 PM) kohsuke: The "gotcha" that made me write that patch is that my first attempt to use blimpy failed miserably at "blimpy ssh"
    (04:29:51 PM) kohsuke: because it was trying a wrong user name, and I couldn't Ctrl+C it because of another bug that since then I fixed
    (04:30:11 PM) rtyler: with aws and openstack it connects multiple times, usually the machine isn't accepting ssh connections right away
    (04:30:14 PM) rtyler: especially on a fresh image
    (04:30:25 PM) kohsuke: yes, I understand why you wrote it the way you did the first place
    (04:31:17 PM) rtyler: heh
    (04:31:21 PM) rtyler: alright
    (04:32:05 PM) kohsuke: Let me change it to ">> Connecting: user@SHIPNAME:port" with dots added over time,
    (04:32:15 PM) kohsuke: and if it's killed by SIGINT I'll run ssh one last time but without -q
    (04:32:22 PM) kohsuke: so you see the error message
    (04:32:41 PM) kohsuke: does that sound OK to you?
    (04:34:30 PM) rtyler: that does sound good
    
    It turns out some mode of failure includes ssh hanging (such as trying a
    wrong port), so silently re-running SSH again wasn't very wise. Instead,
    show the command line needed to let the user run the ssh command by
    himself.
  2. Merge pull request #74 from cloudbees/master

    rtyler committed Mar 29, 2013
    Fixed the test regression and then some
  3. Fixing the unit test failure

    kohsuke committed Mar 29, 2013
    Since these tests do not use any livery, explicit wait_for_ssh command
    is required
  4. Fixed a system/local conflict problem

    kohsuke committed Mar 29, 2013
    If blimpy gem is already installed, this ends up picking blimpy from the installed gem, as opposed to the local workspace.
  5. Making it work again with fog 1.10

    kohsuke committed Mar 29, 2013
    in 1.9, the original code was sufficient, but 1.10 has a massive
    refactoring in the way of registering providers. Unless at least one
    provider is registered, the providers hash is empty, and it causes
    an exception like the following:
    
    /var/lib/gems/1.8/gems/fog-1.10.0/lib/fog/compute.rb:39:in `new': undefined method `include?' for nil:NilClass (NoMethodError)
        from /home/kohsuke/ws/cloudbees/blimpy/lib/blimpy/boxes/aws.rb:39:in `fog'
        from /home/kohsuke/ws/cloudbees/blimpy/lib/blimpy/boxes/aws.rb:32:in `validate!'
        from /home/kohsuke/ws/cloudbees/blimpy/lib/blimpy/fleet.rb:110:in `start'
        from /home/kohsuke/ws/cloudbees/blimpy/lib/blimpy/fleet.rb:109:in `each'
        from /home/kohsuke/ws/cloudbees/blimpy/lib/blimpy/fleet.rb:109:in `start'
        from /home/kohsuke/ws/cloudbees/blimpy/lib/blimpy/cli.rb:73:in `start'
        from /var/lib/gems/1.8/gems/thor-0.18.0/lib/thor/command.rb:27:in `__send__'
        from /var/lib/gems/1.8/gems/thor-0.18.0/lib/thor/command.rb:27:in `run'
        from /var/lib/gems/1.8/gems/thor-0.18.0/lib/thor/invocation.rb:120:in `invoke_command'
        from /var/lib/gems/1.8/gems/thor-0.18.0/lib/thor.rb:363:in `dispatch'
        from /var/lib/gems/1.8/gems/thor-0.18.0/lib/thor/base.rb:427:in `start'
        from /home/kohsuke/ws/cloudbees/blimpy/bin/blimpy:24
    
    By forcing the registration of a provider, it works against with fog
    1.10. Looking at the source tree, this change should also work with fog
    1.9.
  6. SSH returns 255 for connection refused errors.

    kohsuke committed Mar 29, 2013
    So limiting the range down a bit.
  7. only works with Ruby 1.9+

    kohsuke committed Mar 29, 2013
  8. Adding multi-file scp

    kohsuke committed Mar 29, 2013
  9. Merge pull request #73 from cloudbees/master

    rtyler committed Mar 29, 2013
    Bunch O changes
Commits on Mar 28, 2013
Commits on Mar 26, 2013
  1. don't waste a line if there's no need to

    kohsuke committed Dec 19, 2012
    Blimpy prints unnecessary empty line if the SSH connection goes through
    fast enough. Don't do it.
  2. function like this touching ARGV is abstraction violation, as it prev…

    kohsuke committed Dec 19, 2012
    …ents other driver code from legitimately launching interactive shell.
    
     Better to let the calling command handle this
  3. Forcing ssh_wait is considered harmful.

    kohsuke committed Dec 19, 2012
    1. If your Blimpfile is misconfigured, you'll not get any diagnostics information.
    2. When you press Ctrl+C, blimpy doesn't exit because it's just ssh getting killed (and blimp ignores that)
    
    There appears to be no provision for handling options, so I just made it a separate command
Commits on Feb 19, 2013
Commits on Feb 7, 2013
  1. Merge pull request #71 from jblaine/master

    rtyler committed Feb 7, 2013
    Serialize ship.tags to state file, mention ship.tags in README
Commits on Feb 6, 2013
  1. Expose ship.tags in README

    jblaine committed Feb 6, 2013
    Found in the code that I could set this to alter EC2 tags