Closed felixbarny closed 5 years ago
let's start in apm-ci, we can change anytime we need it.
Sounds good 👍🏻 So the owners of the language specific loggers will let you know when they need CI
FYI: @elastic/ecs-logging
For the record, the ECS repo is using Travis CI. I'd be happy to have ECS use this CI instead of Travis :-)
@felixbarny Did you accidentally close this issue? If this was intentional, is there another issue we can track?
This issue was about the general approach. I think there should be separate issues for each project that wants CI. I expect the requirements to be vastly different.
Hey @kuisathaverat,
could you or someone from the automation team help to set up a CI Server for these projects? The idea would be to have one or more repos for Java, PHP, .NET, Ruby, JavaScript, Python and go.
Do you think it makes sense to have a separate CI server for that or would you prefer to re-use the observability/apm-ci for that?