|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This was something I had planned (and very much wanted) to do, but I didn't get time, and haven't had time since then to even support this plugin really.
The solution is pretty straightforward, but would take a bit of work. The basic approach is to attach an IvyListener to the build process which can then filter through all of the different IvyEvent objects fired during the build process, recording the resolve events to fingerprint all dependencies and recording the publish events for automatic archiving and fingerprinting of artifacts.
The Jenkins Artifactory plugin already has a lot of this code for its integration with the Jenkins Ivy plugin, so their general approach could likely just be copied.
I really am not going to have any time at all to work on this though, so I can only hope that some other dev will eventually come along and implement it.