Skip to content

Commit

Permalink
Add debugging ports to gradle cargoRunLocal config
Browse files Browse the repository at this point in the history 
Signed-off-by: Jennifer Hamon <[email protected]>
  • Loading branch information
@DennisDenuto @jhamon
DennisDenuto authored and jhamon committed Jul 6, 2018
1 parent 666c4d2 commit 0192d1d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion build.gradle
View file
Original file line number Diff line number Diff line change
Expand Up @@ -307,7 +307,7 @@ cargo {

local {
timeout = 540000
jvmArgs = "-javaagent:${jacocoLocation}=output=file,dumponexit=true,append=false,destfile=${integrationTestCoverageExecutionData} -DLOGIN_CONFIG_URL=file://" + new File(".").absolutePath + "/uaa/src/main/resources/required_configuration.yml"
jvmArgs = "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 -javaagent:${jacocoLocation}=output=file,dumponexit=true,append=false,destfile=${integrationTestCoverageExecutionData} -DLOGIN_CONFIG_URL=file://" + new File(".").absolutePath + "/uaa/src/main/resources/required_configuration.yml"
outputFile = file('uaa/build/reports/tests/uaa-server.log')
configFile {
file = file('scripts/travis/tomcat-conf/context.xml')
Expand Down

1 comment on commit 0192d1d

@strehle
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

see here: bmuschko/gradle-cargo-plugin#99 and
bmuschko/gradle-cargo-plugin#138

currently the integration tests fail because of
ERROR: transport error 202: could not find free port in debug port range: Transport endpoint is not connected
JDWP exit error ERROR_unknown(510): could not listen [transport.c:616]
ERROR: JDWP could not listen, jvmtiError=ERROR_unknown(510)

maybe better to add an option similar to spring profiles ,e.g. to distinguesh database types something like localdebug in spring profiles and then add dynamically the debug option into jvmArgs.

Right now all integration tests fail because each task is done with debug options and start / stop uses the same debug port... debugging is useful if a human is starting the test , but for travis debugging is not needed.

regards,
-markus

Please sign in to comment.