Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Continuous Integration using Buildkite #20

Open
geigerzaehler opened this issue Aug 22, 2019 · 6 comments
Open

Continuous Integration using Buildkite #20

geigerzaehler opened this issue Aug 22, 2019 · 6 comments
Assignees

Comments

@geigerzaehler
Copy link
Collaborator

We can use buildkite with our own machines for CI. This promises to provide faster build times, more control over the process, more security and a generally better development experience.

No use buildkite we need to

  • Setup a buildkite project for this repo
  • Configure build commands based on what we currently run on circle
  • Provide a base image for the build using a dockerfile in the repo

Buildkite is already set up for osrank which we can use as a resource.

@kim set up buildkite and he is our point of contact.

A nice to have would be to build the base image also in CI.

@rockbmb
Copy link
Contributor

rockbmb commented Aug 24, 2019

@geigerzaehler what is the rationale for doing this?

I am in favor of having less CI services so we can pool different project's resources together.

@geigerzaehler
Copy link
Collaborator Author

@geigerzaehler what is the rationale for doing this?

As I mentioned in the description these are the main reasons:

This promises to provide faster build times, more control over the process, more security and a generally better development experience.

I am in favor of having less CI services so we can pool different project's resources together.

I’m not sure what you mean by pooling resources. We would also ditch Circle CI if buidkite works well.

@rockbmb
Copy link
Contributor

rockbmb commented Aug 26, 2019

@geigerzaehler by pooling resources I mean we aren't the only team in the organization that needs CI: if we use the same service, it'll be one service to maintain instead of more.

@geigerzaehler
Copy link
Collaborator Author

@geigerzaehler by pooling resources I mean we aren't the only team in the organization that needs CI: if we use the same service, it'll be one service to maintain instead of more.

I understand. Most likely the whole team will be using buidkite. This is a decision that we made when discussing the broom and micro-broom project proposal.s

@rockbmb
Copy link
Contributor

rockbmb commented Aug 27, 2019

@geigerzaehler do you mind if I give this issue a try?

@geigerzaehler
Copy link
Collaborator Author

Of course not!

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

Successfully merging a pull request may close this issue.

2 participants