Skip to content

Commit de8763c

Browse files
authoredDec 21, 2020
Document release process for OTEL hotfixes (#191)
* Document how to do hotfixes for OTEL Signed-off-by: Pavol Loffay <p.loffay@gmail.com> * Fix Signed-off-by: Pavol Loffay <p.loffay@gmail.com> * typos Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
1 parent c320487 commit de8763c

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed
 

‎OPENTELEMETRY_AGENT_HOTFIXES.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Hotfixes for OpenTelemetry javaagent
2+
3+
All fixes for the core [open-telemetry/opentelemetry-java-instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation)
4+
should be submitted to the upstream project. However, merge and release into upstream might take some time
5+
therefore urgent hotfixes can be submitted to the fork [hypertrace/opentelemetry-java-instrumentation](https://github.com/hypertrace/opentelemetry-java-instrumentation).
6+
7+
Changes to the fork are done in a maintenance branches e.g. `v0.13.x` and locally tested and released.
8+
The fixed artifacts are published to the [Hypertrace Binray](https://bintray.com/hypertrace/maven).
9+
Then the released artifacts can be consumed by version(s) change in gradle scripts in this repository.
10+
11+
## Hotfix release of hypertrace/opentelemetry-java-instrumentation
12+
13+
This [commit](https://github.com/hypertrace/opentelemetry-java-instrumentation/commit/88c2b113d0cc2fad01ddde9cccdab3b09cbfb6da)
14+
shows an example of release configuration for `javaagent` artifact.
15+
16+
```bash
17+
git checkout -b v0.13.x
18+
# make required changes and run tests locally
19+
git tag 0.13.2-ht # use -ht suffix to denote that this is forked version
20+
ORG_GRADLE_PROJECT_publishUser=<bintray-user> ORG_GRADLE_PROJECT_publishApiKey=<bintray-api-key> ./gradlew bintrayPublish -Prelease.useLastTag=true
21+
```

0 commit comments

Comments
 (0)
Please sign in to comment.