The challenge is that SSB’s ant script is very mature and battle tested, it WORKS. It has many options and additional tools as targets.
The most effective combination I’ve see was to wrap ant build target win Maven. You would still build the application in ant but you could run junit using Maven.
So in essence it is possible to move to Maven or Gradle but it will take a lot of work and errors and custom code(which would have to be rewritten for maven) written for ant.
And the result is not tested by 100’s of other deployments.
I can understand that it would be a nice to have but what is the main purpose of such move?
What you get for free in Maven is dependencies, but this you will not get from Sailpoint as there is no Sailpoint pom file. You would still have to do it yourself.
imho: If you are hardcode Maven shop(and you must use that in you CI/CD pipeline) wrap existing ant target with Mave and use that. Otherwise don’t do this.
Thanks for sharing the link and the update! It’s great to hear it’s running smoothly in dev. Out of curiosity, are you following any specific approach or workflow to integrate the toolkit with your setup? Would love to understand how it fits in practice.
SailPoint already provided this DevSecOps Toolkit that we can integrate with our environment setup. Process is simple, you need to run maven commands to create the project structure and then place all your custom xml, java files, custom jar, custom UI files in their respective folders. Also, you can develop IIQ plugin project as well using this Utility.
Let me know if you need more details. We have configured this in our production setup as well and it is working smoothly.