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

Move CI from GitLab to CircleCI #4

Closed
jmaupetit opened this issue May 23, 2018 · 2 comments
Closed

Move CI from GitLab to CircleCI #4

jmaupetit opened this issue May 23, 2018 · 2 comments
Assignees

Comments

@jmaupetit
Copy link
Contributor

jmaupetit commented May 23, 2018

Purpose

Historically, this project has been initiated using our own GitLab instance, hence, we designed a GitLab-CI-based continuous integration (CI) workflow. When we decided to open-source this project and move it to GitHub, we lost our CI. As it is a prerequisite for this project (for every project in fact), we need to improve and re-implement it.

Proposal

As we usually use CircleCI, let's stick to it for Arnold. We have the advantage that CircleCI and GitLab-CI philosophies are quite close. Therefor, we might thought that this will be an easy task, but it's not. The way we designed our original CI workflow is not sustainable for an open source project (the last step is a deployment to our OpenShift instance).

My first idea is to use a trashable MiniShift instance in our CI workflow, but this will be a really tricky part.

Dear contributors, I invite you to make proposals; nothing has been decided yet.

@cchaudier
Copy link
Contributor

cchaudier commented May 29, 2018

The project openshift-acme use the oc cluster up command to launch OpenShift on Travis.
I think we can try it on CircleCI.

@cchaudier
Copy link
Contributor

For the OpenShift deploy I've create the Issue #48

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

2 participants