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

Using Dockerfile to start bbd instead of scripts only #10

Closed
samuelololol opened this issue Nov 25, 2014 · 6 comments
Closed

Using Dockerfile to start bbd instead of scripts only #10

samuelololol opened this issue Nov 25, 2014 · 6 comments
Assignees

Comments

@samuelololol
Copy link
Owner

using Dockerfile to enable

  1. mount pointer owner
  2. additional files
  3. reduce the parameter of create-script
@samuelololol
Copy link
Owner Author

using Dockerfile will go along with samuelololol/gentoo-buildbot:0.8, brings some work-around from 0.9 directly(ie. mount folder, links configs, repo url, ssh keys ...), lets list below:

  1. mount folder: /buildbot
  2. link files:
    1. buildbot.tac(master)
    2. buildbot.tac(slave)
    3. master.cfg
    4. ssh keys
  3. repo path
  4. expose port

@samuelololol
Copy link
Owner Author

1a09d8a
8b8dca8
0bba394

@samuelololol
Copy link
Owner Author

script with parameters

  1. repo url
  2. repo branch
  3. ssh key

@samuelololol
Copy link
Owner Author

need another scripts for 1 clicked launch, which only accepts

  1. repo url
  2. repo branch
  3. ssh keys(optional)

For now, prepare_image.sh accpets only 2 arguments, buildbot-setting folder and dockerfile.diff. It has to combine with create_bbd.sh scripts.

@samuelololol
Copy link
Owner Author

add Fig

@samuelololol
Copy link
Owner Author

solved with #11
using docker-compose(Fig)

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

No branches or pull requests

1 participant