First of all let me say thank you to all the hard-working developers of the Buildship plugin.
I’m suspecting there is an easy answer to this that I’m just not seeing.
We have a multi-project setup that builds EAR archives for deployment on a WebSphere server, as well as a JAR for deployment on a different server.
We recently stood up a Jenkins server that builds this project using gradle scripts and it is a huge help.
However, the developers on the team use Eclipse for their work on their local development machine, and this is leading to some inconsistencies. For example:
The developers workflow is to make changes to their code, then do a Run As > Run on Server or a Republish to deploy their changes to their local WebSphere instance. Now we have been running into issues where a developer will use this workflow, their feature will work correctly, but when Jenkins picks it up the build either fails or (worse) we experience runtime errors because the developers are unable to use gradle to build and deploy the project - the only alternative we have seen so far is to go from:
- Right click the server in the Servers view and click “Republish”
- Run the gradle build task
- Go to the gradle build output folder to retrieve the EAR file
- Open the local WebSphere administration console
- Upload the EAR file to update the application
- Do this two more times for the other EARs in our project.
As you can see, we’re anxious to find a solution.
We are also having issues related to runtime dependencies because a developer will run e.g. methods on a JAR project via Eclipse, everything works fine, but then when it is built using gradle on the Jenkins server, it is discovered that that dependency was not included.
Is there an easy way to run our WebSphere EAR projects and our JAR projects via Eclipse using the gradle scripts? Or does our workflow need to change to “only edit in Eclipse, and run via the command line/deploy EARs manually to test the actual build.gradle output?”