David Zuelke 00a5fc7f0b call out subprocess termination from signals
when hitting Ctrl+C in a 'docker run bob …', the main script itself actually can't be terminated by Ctrl+C, because it's PID 1

in that case, rather than just shutting down silently (by terminating itself using a SIGINT), we will see the subprocess exit (because Ctrl+C is sent to the whole process group)

When this happens, the return code of the process will be negative, to indicate that it didn't exit with that code, but instead got terminated by a signal of that (absolute) number
2020-01-15 16:53:35 +01:00
2014-04-02 11:45:25 -04:00
2014-03-17 13:09:21 -04:00
2020-01-14 23:15:11 +01:00
2017-05-26 11:49:06 -04:00
2017-05-30 22:49:39 +01:00
2017-05-30 22:49:39 +01:00
2020-01-15 02:01:38 +01:00

Bob: The Binary Build Toolkit

This repo exists as a framework for the compilation and deployment of binaries and libraries on Heroku.

It is inspired by (and extracted from) kennethreitz/python-versions.

Intended Design

  • Flexible type hierarchy
  • Flat dependency resolution
  • Version agnostic (careful curation and naming conventions preferred)
  • Import already-deployed sub-dependencies during a build (optionally fetch from UPSTREAM_S3_BUCKET)

Powered By

  • Bash, mostly
  • A litle bit of Python
  • Boto

Getting Started (Staging)

  • $ heroku create build-toolkit-python-staging --buildpack https://github.com/kennethreitz/conda-buildpack.git
  • $ heroku config:set AWS_ACCESS_KEY_ID=xxx AWS_SECRET_ACCESS_KEY=xxx S3_BUCKET=xxx

Now that your Heroku app for building is created, push a repo containing your formula to the app (e.g. the python buildpack repo).

$ heroku run bash

$ bob build runtimes/python-2.7.6
$ bob deploy runtimes/python-2.7.6


S
Description
No description provided
Readme 2.4 MiB
Languages
Python 95.3%
Shell 4.7%