Use Gradle Tasks Instead Configuration Parameters to Determine Whether a Module Uses Java

jenkinsci / peass-ci-plugin

Jenkins plugin for peass to support performance measurement in CI

https://plugins.jenkins.io/peass-ci/

GNU Affero General Public License v3.0

4 stars 12 forks source link

Use Gradle Tasks Instead Configuration Parameters to Determine Whether a Module Uses Java #142

Closed DaGeRe closed 2 years ago

DaGeRe commented 2 years ago

What feature do you want to see added?

Peass needs to know whether a module uses Java, Spring Boot or Android, or has an integrationTest task, to configure them. This is hard for gradle files, because custom plugins may build upon the original Java plugin.

Therefore, Peass should determine this by executing ./gradlew tasks instead of parsing the buildfiles.

Upstream changes

No response

DaGeRe commented 2 years ago

The implementation has started with https://github.com/DaGeRe/peass/commit/97a3ab53eed436799daa2cc9abaa3bded175961d .

DaGeRe commented 2 years ago

This should work now. @bam-hbt @mawHBT Could you check whether this works for you?

mawHBT commented 2 years ago

Plugin detection was tested with several jobs.