Splunk AppDynamics

limit transformClassesWithAppDynamicsForXX to certain buildTypes (appdynamics-gradle-plugin)

Jerg_Weick
Explorer

subject: 

appdynamics-gradle-plugin

problem:

transformation runs on every buildType built

Hello,

i'm looking for a way to limit the class-transformation (gradle task is called "transformClassesWithAppDynamicsFor<buildType>") to certain build-types.

I'm aware of the flag 

adeum {
..
enabledForDebugBuilds = false
..
}

to limit transformation to release-builds, but that does not solve our problem, as we build several "release"-builds in our release-job(CI) but only 2 of them need to be instrumented and thus have it's classes transformed.

I wouldn't mind it at all if the transform-task would not take more than 6! minutes for a single build-type.

I'd appreciate any suggestion on how to achieve this.

regards,

Jerg

Labels (1)
0 Karma

Sergiu_Cosmin
Explorer

Hello, 

This should be possible now starting with 23.4.1. 

You have the option to disable based on build type, product flavor or variant. The properties you can use are exemplified below:  

adeum {
  disabledForBuildTypes = ["debug"]
  disabledForProductFlavors = ["app"] 
  disabledForVariants = ["appDebug"]
}
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...