I like the idea of teeing to a file and capturing using logstash


On Mon, Mar 25, 2013 at 8:46 AM, Matthew Trahan <notifications@github.com>wrote:

> In src/snakes/deploy.py:
>
> > +import json
> > +
> > +bucket_name = os.environ.get('GEARBOX_BUCKET', 's3_ops')
> > +chef_repo = os.environ.get('CHEF_REPO', 'git@github.com:NarrativeScience/chef-repo.git')
> > +
> > +def deploy(package, stage):
> > +    print 'Deploying {0} to {1}'.format(package,stage)
> > +    version = get_latest_version(package)
> > +    print '  using version {0}'.format(version)
> > +    print sh.rm('-rf', 'chef-repo')
> > +    print sh.git('clone', chef_repo)
> > +    print sh.cd('chef-repo')
> > +    env_config_file_path = 'environments/{0}.json'.format(stage)
> > +    update_environment_config(env_config_file_path, package, version)
> > +    # Commit and push to chef-repo
> > +    print sh.git('add', '-A')
>
> Jenkins will already capture archive the output of this, up to a point. Is
> that sufficient? It also may be easier to configure if we just tee the
> output to a file and publish that with log stash.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/NarrativeScience/snakegit/pull/60/files#r3511715>
> .
>



-- 
Tom Howe | Narrative Science
Bender of Turtles
(773) 809-6334