This Docker image has been moved to a new location. Future updates and releases will be published at:
👉 cqse/teamscale-java-profiler
Please update your docker pull commands and FROM statements in Dockerfiles to use the new repository.
./gradlew assembledocker build -f agent/src/docker/Dockerfile .For IntelliJ, there is a run config SampleApp which profiles the included sample-debugging-app and can be used to debug the agent. This run config omits relocating packages in the shadow jar because with relocating, the package names in the jar would not match with the ones IntelliJ knows from the code and so debugging would not work.
The agent is configured in the config file sample-debugging-app/jacocoagent.properties. By default, no upload is configured but the file includes all required options to upload to Teamscale, they are just commented out. Feel free to adapt it to your needs.
If you get an IllegalStateException: Cannot process instrumented class com/example/Main, make sure that you use the built in IntelliJ functionality for building and running instead of gradle (IntelliJ Settings -> Build, Execution, Deplyment -> Build Tools -> Gradle -> Build and run using: IntelliJ IDEA).
build.gradle and in BuildVersion.kt./gradlew publishToMavenLocal will deploy your checked out version to your local m2 cacheshare.cqse.eu repository with the mavenLocal() repository in the buildscript section of the project's build.gradlerepositories { mavenLocal(); mavenCentral() } to the body of the build.gradle./gradlew with --no-daemon -Dorg.gradle.debug=true.
The build will pause and wait for you to attach a debugger, via IntelliJ's Run > Attach to Process../gradlew with --no-daemon --debug-jvm and wait for the test phase to start.
The build will pause and wait for you to attach a debugger, via IntelliJ's Run > Attach to Process.When master has accumulated changes you want to release, please perform the following on master in a single commit:
21.3.0.appVersion accordingly.#release-crew via Slack) that the artifacts can now be promoted to Maven Central.Releases are numbered according to semantic versioning (see full changelog).
All tags are built automatically using Github Actions and Docker Cloud Build with the release binaries being uploaded to the GitHub Releases.
Only use GitHub releases in production. This ensures that we always know which code is running in production.
ext.jacocoVersion in the build script./gradlew distContent type
Image
Digest
sha256:2c75cc70c…
Size
16.4 MB
Last updated
about 1 month ago
docker pull cqse/teamscale-jacoco-agent