-
-
Notifications
You must be signed in to change notification settings - Fork 470
Maven build with modules #309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
build.details().getConsoleOutputText() |
Hi, this one doesn't do what I need. However I have written few classes, which add better Module support, so I guess this issue can be closed. Thank you Jakub |
What about making a pull request ? |
Pull Request submitted. Hope I did it the right way since this is my first Pull Request (ever)... |
@dawon would you please so kind to squash your commits...and create a issue for this ...and reference it in the commit message like:
This would help a lot... |
@khmarbaise I squashed the commits and created issue for it, or at least I thought I did: see dawon@6512454 |
- slight modifications based on removement of Guava
Hello,
I have a job with several modules, is it possible to access details (such as whether the build of module was successful, unstable, failed, console log of module and test results)? I was unable to find methods to obtain such info. Even though api allows to get this information (/job/[jobName]/[build]/[module]/api/xml)
Only thing I found was getMavenModule and getModuleRecords which gets me only information from pom file.
Thank you very much for any advice
Jakub
The text was updated successfully, but these errors were encountered: