Skip to content

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

Closed
dawon opened this issue Nov 13, 2017 · 6 comments
Closed

Maven build with modules #309

dawon opened this issue Nov 13, 2017 · 6 comments
Assignees
Milestone

Comments

@dawon
Copy link

dawon commented Nov 13, 2017

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

@chimisu
Copy link

chimisu commented Dec 15, 2017

build.details().getConsoleOutputText()

@dawon
Copy link
Author

dawon commented Jan 29, 2018

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

@khmarbaise
Copy link
Member

What about making a pull request ?

dawon pushed a commit to dawon/java-client-api that referenced this issue May 30, 2018
@dawon
Copy link
Author

dawon commented May 30, 2018

Pull Request submitted. Hope I did it the right way since this is my first Pull Request (ever)...

dawon pushed a commit to dawon/java-client-api that referenced this issue May 30, 2018
dawon pushed a commit to dawon/java-client-api that referenced this issue May 31, 2018
dawon pushed a commit to dawon/java-client-api that referenced this issue May 31, 2018
@khmarbaise
Copy link
Member

@dawon would you please so kind to squash your commits...and create a issue for this ...and reference it in the commit message like:

Fixed #XX
 o Supplemental explanations

This would help a lot...

@dawon
Copy link
Author

dawon commented Jun 23, 2018

@khmarbaise I squashed the commits and created issue for it, or at least I thought I did:

see dawon@6512454

khmarbaise pushed a commit that referenced this issue May 25, 2019
 - slight modifications based on removement of Guava
@khmarbaise khmarbaise added this to the Release 0.4.0 milestone May 25, 2019
@khmarbaise khmarbaise self-assigned this May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants