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

[Research] How to get back into GHE #87

Closed
fokusferit opened this issue Oct 6, 2017 · 1 comment
Closed

[Research] How to get back into GHE #87

fokusferit opened this issue Oct 6, 2017 · 1 comment
Milestone

Comments

@fokusferit
Copy link
Contributor

As with CDP we could move back to GHE. Investigate how we can use CircleCI set up within CDP and move back to GHE.

@fokusferit
Copy link
Contributor Author

fokusferit commented Oct 6, 2017

Current state:

  • CDP allows us to configure easily with a YAML file our CI pipeline, it is similiar to CircleCI, TravisCI in a way that for PR testing you define commands which needs to be executed succesfully.

Limitations:

  • CDP doesn't allow to push a commit back to the source repository. Generally it limits any access to internal GHE. Therefore it is not possible to automatically bump our package.json number and do automated npm releases, create git releases with Changelog etc.

  • A possible solution might be to use a deployment workflow where we create a docker image on aws and access the repository via this image. Issue here is that you can't use this functionality until you have a Zalando-X-Team which is officially registered.

Outcome:

  • We could move back to GHE but we would need to do manual releases, e.g. run a release-script which is basically doing the release steps from our circle.yaml file , this might not be a huge time consuming issue but it would be a manual step which a) we need to do after each PR merge or b) on a regular basis (weekly, bi-weekly, daily...)

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

1 participant