[#1994] Migrate build.gradle from Groovy to Kotlin

[nseah21]

Fixes #1994

Migrate build.gradle from Groovy to Kotlin

The current build script uses Groovy syntax. 

Kotlin has been recommended, however, due to cleaner syntax 
and a better editing experience, owing to its similarity with Java.

Let's refactor the build.gradle file to use Kotlin instead, so that
someone who starts work on build.gradle.kts will find it easier 
to transition to the Java code.

Other information

It is worth noting that builds using Kotlin tend to be slower than builds using Groovy.

However, it is assumed that the added benefit of a more standardised syntax (as mentioned in #1994) outweighs this performance tradeoff.

[nseah21]

When running gradlew clean build in root directory, the build terminates with an exception after executing the :installFrontend task.

Could I kindly request for some guidance on how to resolve the following issue?

> Task :installFrontend FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':installFrontend'.
> Process 'command 'cmd'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 28s
9 actionable tasks: 9 executed

[sikai00]

I ran the changes in your PR with the scan and info flag:

I got this:

Starting process 'command '/Users/sikai/RepoSense/build/node/bin/node''. Working directory: /Users/sikai/RepoSense/frontend Command: /Users/sikai/RepoSense/build/node/bin/node /Users/sikai/RepoSense/build/node/lib/node_modules/npm/bin/npm-cli.js ci --production false --cache /Users/sikai/RepoSense/frontend --loglevel info --progress true
Successfully started process 'command '/Users/sikai/RepoSense/build/node/bin/node''
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]

Usage: npm <command>

versus master branch:

This might be a good starting point. Seems like the arguments were not passed into npm directly but rather through /Users/sikai/RepoSense/build/node/lib/node_modules/npm/bin/npm-cli.js ci --production false --cache .

[nseah21]

@sikai00 Thank you for pointing me in the right direction. I have re-attempted the migration and have gotten most of the tasks to run successfully.

However, the task :run seems to have broken, as invoking gradlew run -Dargs="--view --repo <repo-url>" results in the following:

> Task :run
02:21:42 - Config path not provided, using the config folder as default.
02:21:42 - Parsed header of CSV file, repo-config.csv, and recognized columns: ...

instead of:

> Task :run
02:24:29 - Log temp folder has been successfully created
02:24:30 - Cloning in parallel from <repo-url>...

when building with the original build.gradle file.

Has anyone experienced this issue previously when writing the build.gradle in Groovy?

[gok99]

Changes are looking good so far! Don't forget the newline at EOF so that the CI tests can run.

[gok99]

Bumping the failing build: setCommandLine("cmd") wouldn't work on Linux and Mac. @nseah21 Have you tried using the liferay node plugin we used in the groovy build.gradle?

[yhtMinceraft1010X]

@nseah21 Have you tried running ./gradlew clean checkstyleAll test systemTest coverage (must be this exact command, iirc gradlew clean build won't run the coverage task) with --info or --debug flags on your local machine?

The additional logging info might help in determining the exact cause behind Unable to read execution data file /Users/runner/work/RepoSense/RepoSense/build/test-results/systemtest/binary

[yhtMinceraft1010X]

Task dependency should not be introduced here

[github-actions]

Hi,
We are going to mark this PR as stale because it has been inactive for the past 30 days.
If no further activity occurs within the following 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 7 days and leave a comment to remove the stale label.
Do let us know if you are stuck so that we can help you!'

[sikai00]

Per the error message,

Gradle detected a problem with the following location: 'D:\a\RepoSense\RepoSense\build\jacoco\test.exec'. Reason: Task ':coverage' uses this output of task ':test' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

it seems the fix to your issue is to declare an explicit dependency for the predefined task 'test'. This follows from coverage using 'test' to know the amount of coverage.

As for the second issue, I did some Googling online. Perhaps this may help?

Hope this helps you fix the issues you are facing!

[MarcusTXK]

Hi @nseah21, just bumping this PR to check its progress. Could I check if there are any major blockers for you currently?

[nseah21]

Hi @MarcusTXK, I am still trying to troubleshoot an issue with reading the execution data file.

* What went wrong:
Execution failed for task ':coverage'.
> Unable to read execution data file <file_path>\RepoSense\build\test-results\systemtest\binary

I have attempted the fix posted by @sikai00 above but the build is still throwing the error.

May I request for some guidance on this issue? Thank you.

[damithc]

@nseah21 I'm not sure if we want to merge this PR in the end, as I mentioned in #1994 (comment)
Even if we don't merge it in the end, it is still fine to continue until we reach a LGTM state so that at least we know what it would look like.

[github-actions]

Hi,
We are going to mark this PR as stale because it has been inactive for the past 30 days.
If no further activity occurs within the following 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 7 days and leave a comment to remove the stale label.
Do let us know if you are stuck so that we can help you!'

[nseah21]

@gok99 @yhtMinceraft1010X This pull request is ready for the next round of reviews.

[github-actions]

The following links are for previewing this pull request:

• Dashboard Preview: https://dashboard-2008-pr-reposense-reposense.surge.sh
• Docs Preview: https://docs-2008-pr-reposense-reposense.surge.sh