Add support for gradle ecosystem metrics collection

[amazimbe]

What are you trying to accomplish?

Update the Gradle ecosystem to add support for gathering ecosystem metrics.

Anything you want to highlight for special attention from reviewers?

As agreed at standup, in this PR, I'm returning jvm_based_languages as the language name. In addition, NOT-AVAILABLE is being returned for the language and gradle versions as there is no consistent way to extract this data based on the Gradle dependency file alone. In future, we might be able to improve on this but that will have to await the completion of install Gradle on docker images.

How will you know you've accomplished your goal?

• I'll be able to see Gradle ecosystem metrics in datadog

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[robaiken]

Since Gradle can build non-JVM projects like C++ and JavaScript, is jvm_languages is the right value here?

[amazimbe]

In that case, perhaps, I should just use unknown / not available

[thavaahariharangit]

Just FYI

To identify the programming language from a Gradle build file, you can look for specific plugins and configurations that are commonly associated with certain languages. Here are some key indicators:

1. Java: Look for the java plugin.

plugins {
    id 'java'
}

2. Kotlin: Look for the kotlin plugin.

plugins {
    id 'org.jetbrains.kotlin.jvm' version '1.5.21'
}

3. Groovy: Look for the groovy plugin.

plugins {
    id 'groovy'
}

4. Scala: Look for the scala plugin.

plugins {
    id 'scala'
}

5. Android: Look for the com.android.application or com.android.library plugins.

plugins {
    id 'com.android.application'
}

By examining the plugins section of the build.gradle file, you can determine the primary programming language used in the project.

And for
6. C++

plugins {
    id 'cpp'
}

7. Javacript

plugins {
    id 'com.github.node-gradle.node' version '3.0.1'
}

If this information is not there then we can say unknown. This is my reading, Nonblocking comment

[robaiken]

@thavaahariharangit can you provide a doc for this, it might be useful for @amazimbe

[thavaahariharangit]

If there is no plugins.id in the build.gradle file, you can look for other indicators to identify the programming language. Here are some additional clues:

1. Java: Look for apply plugin: 'java' or dependencies like implementation 'org.springframework.boot:spring-boot-starter'.
2. Kotlin: Look for apply plugin: 'kotlin' or dependencies like implementation "org.jetbrains.kotlin:kotlin-stdlib".
3. Groovy: Look for apply plugin: 'groovy' or dependencies like implementation 'org.codehaus.groovy:groovy-all'.
4. Scala: Look for apply plugin: 'scala' or dependencies like implementation 'org.scala-lang:scala-library'.
5. Android: Look for apply plugin: 'com.android.application' or apply plugin: 'com.android.library'.

By examining these elements, you can determine the primary programming language used in the project.

JavaScript

Look for:
apply plugin: 'node'
apply plugin: 'com.github.node-gradle.node'
Dependencies like implementation 'org.nodejs:node' or implementation 'com.github.node-gradle:node'

C++

Look for:
apply plugin: 'cpp'
Dependencies like implementation 'org.gradle.cpp:cpp-library'
By examining these elements, you can determine if the project is using JavaScript or C++.

[thavaahariharangit]

Related Readings:
https://docs.gradle.org/current/userguide/plugins.html
https://docs.gradle.org/current/userguide/tutorial_using_tasks.html

[amazimbe]

I'll merge this but will create another PR if I manage to do the parsing consistently and reliably.