[GRADLE-2797] Enhance tooling api to ease debugging of tests run via gradle Created: 20/Jun/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

Tooling api should provide convenient interface for debugging tests executed by gradle.

The only facility available at the moment is to define a 'debug' property at the gradle script and use hard-coded port 5005 for remote debugging ([1]http://www.gradle.org/docs/current/ds...)

However, it's rather inconvenient for ide users because ideally they don't want to change anything at gradle config and just hit 'debug' button and get the job done. It's also possible that port 5005 is already occupied at local environment.

I.e. the tooling api should allow to do the following:
1. Specify that 'test' task should be executed at 'debug' mode;
2. Customize the port used for receiving remote debugger connections;
----------------------------------------------------------------------------------------
[1] http://www.gradle.org/docs/current/dsl/org.gradle.api.tasks.testing.Test.html

 Comments   
Comment by Ryan Shillington [ 01/Nov/13 ]

As a workaround, try putting this in your gradle build file

tests {
   // With this, you can attach a debugger at any time, on port 5050.  Change suspend=y to wait for a debugger before starting the test.
    jvmArgs '-Xdebug', 
        '-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5050'
}

Answer courtesy of this guy: http://blogs.steeplesoft.com/posts/2013/09/10/gradle-tip-attaching-a-debugger/

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:31:47 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.