Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use captain to build #2

Open
ejholmes opened this issue Aug 6, 2015 · 13 comments
Open

Use captain to build #2

ejholmes opened this issue Aug 6, 2015 · 13 comments

Comments

@ejholmes
Copy link
Contributor

ejholmes commented Aug 6, 2015

Using captain in the default builder image would be nice for a couple of reasons:

  1. It supports a captain.yml file to build multiple Dockerfiles.
  2. captain could be used locally to build as well.

Only thing that prevents this atm is that captain tags the docker image with a short sha instead of the full sha.

@mwildehahn
Copy link
Contributor

I need this as well to build multiple frontend images with different assets, filed: harbur/captain#31.

I think the full commit sha is more of a nice to have, I'm going to start working on a branch that uses captain.

@ejholmes
Copy link
Contributor Author

ejholmes commented Jan 8, 2016

@mhahn You can also just fork the remind101/conveyor-builder image and pass your own image as --builder.image: https://github.com/remind101/conveyor/blob/master/cmd/conveyor/worker.go#L28-L31

@mwildehahn
Copy link
Contributor

yea i did that to use a more updated version of conveyor-builder but captain also provides a similar flow to circleci which is what builds all our images now, so i think its a win

@dkapanidis
Copy link

Intrigued and interested to see conveyor and captain work together. I can check the full-sha issue, would a flag-enabling option be sufficient for that?

@mwildehahn
Copy link
Contributor

@Spiddy any update on this?

@mwildehahn
Copy link
Contributor

@ejholmes i started looking at this last night. I had some questions about how you would recommend structuring it.

One option like you mentioned is to fork: https://github.com/remind101/conveyor/blob/master/builder/docker/bin/build and use captain instead. I wasn't sure how to integrate that into the current app structure or if i should just do it as a separate repo

@dkapanidis
Copy link

captain code is merged. It can be activated using -l flag (or --long-sha)

@mwildehahn
Copy link
Contributor

thanks @Spiddy

On Mon, Feb 1, 2016 at 2:22 AM spiddy [email protected] wrote:

captain code is merged. It can be activated using -l flag (or --long-sha)


Reply to this email directly or view it on GitHub
#2 (comment).

@ejholmes
Copy link
Contributor Author

ejholmes commented Feb 1, 2016

@mhahn I think with long sha support, captain can just replace the shell commands that we have in ./bin/build.

@mwildehahn
Copy link
Contributor

yea, i've started that here: https://github.com/lunohq/conveyor-builder-captain/blob/master/bin/build

only regression is retrying docker push 3 times, i opened: harbur/captain#34 to track adding support for that in captain

@ejholmes
Copy link
Contributor Author

ejholmes commented Feb 4, 2016

FYI, I just pulled out remind101/conveyor-builder to https://github.com/remind101/conveyor-builder. If we make any changes to the builder, that'll be the place to do it.

@mwildehahn
Copy link
Contributor

Nice it felt weird inside this repo :)
On Wed, Feb 3, 2016 at 6:31 PM Eric Holmes [email protected] wrote:

FYI, I just pulled out remind101/conveyor-builder to
https://github.com/remind101/conveyor-builder. If we make any changes to
the builder, that'll be the place to do it.


Reply to this email directly or view it on GitHub
#2 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants