You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the ocb binary is released in the opentelemetry-collector repository, as opposed to the rest of the binaries related to the collector, including core, contrib, and k8s distributions in the opentelemetry-collector-releases repository. Since many OpenTelemetry Collector users actually build their own custom opentelemetry collector using ocb, it may be confusing to find the binary in a different repository
I would like to migrate the release workflows from the opentelemetry-collector repository to the opentelemetry-collector-releases repository.
Alternatively, the workflows could remain inside the opentelemetry-collector repo but be modified to publish the binaries to the opentelemetry-collector-releases repository instead of the collector repository when the release train is run. I am not opposed to either solution, but will have to get more familiar with the actions and scripts involved with the build and release process (would love to dive into any documentation we have about this process)!
I intend to add a standard dockerfile for the ocb binary, in reference to Issue 5712, but in that ticket and the subsequent PR, it was generally agreed that the ocb binary should be released to the opentelemetry-collector-releases repository prior to adding dockerfile support.
Anyone available to point me in the right direction for the build/release process for the collector? Thanks!
The text was updated successfully, but these errors were encountered:
Currently, the ocb binary is released in the opentelemetry-collector repository, as opposed to the rest of the binaries related to the collector, including core, contrib, and k8s distributions in the opentelemetry-collector-releases repository. Since many OpenTelemetry Collector users actually build their own custom opentelemetry collector using ocb, it may be confusing to find the binary in a different repository
I would like to migrate the release workflows from the opentelemetry-collector repository to the opentelemetry-collector-releases repository.
Alternatively, the workflows could remain inside the opentelemetry-collector repo but be modified to publish the binaries to the opentelemetry-collector-releases repository instead of the collector repository when the release train is run. I am not opposed to either solution, but will have to get more familiar with the actions and scripts involved with the build and release process (would love to dive into any documentation we have about this process)!
I intend to add a standard dockerfile for the ocb binary, in reference to Issue 5712, but in that ticket and the subsequent PR, it was generally agreed that the ocb binary should be released to the opentelemetry-collector-releases repository prior to adding dockerfile support.
Anyone available to point me in the right direction for the build/release process for the collector? Thanks!
The text was updated successfully, but these errors were encountered: