|
||||||||
|
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.
even if you could parse the poms at the end of the build but it won't help.
e.g.
perform the release (in jenkins)
parse pom
dev checks in 5000 changes.
jenkins is not polling and not building this source code
next release (info is outdated).
The buildwrappers are called before the code checkout so I doubt there is much that can be done to ensure that the numbers (and module list) is always correct.