Is best practice to run tests with Jenkins, and Deploy with Jenkins, and just use Gradle to Build?
It seems weird to offload so much to Gradle when the point of Jenkins is to coordinate the build steps
Just to share: there is value in the ability to run the build on any developer machine. Jenkinsfiles, GitHub Actions workflow yaml files, and GitLab CI yaml files can’t be run on any machine without some shim program to interpret and run those files.
So I see this as a separation of concerns problem. Jenkins is to run builds in a distributed manner, gradle or bash scripts are to orchestrate the build/testing.
Right now we have mix of Macs, Linux and Windows devs. I’m considering replacing bash scripts with Powershell Core in projects that do not have/want gradle. Powershell is promising and fully cross platform.
I personally believe gradle does to much. But there isn’t much choice in Java projects.
I’m going to understand more of what you’re saying, I’m used to GitHub actions but recently joined a heavy jenkins-gradle project
I haven’t had to do jenkins for like 6 years and it just seems so heavy and overkill