the command 'mvn versions:display-dependency-updates' gives the latest updates for my dependancies.
Is there a way of getting a HTML report of the same? Something like
http://awhitford.github.io/lombok.maven/lombok-maven-plugin/dependency-updates-report.html
thanks in advance,
-anish
Sorry folks - i should have a little more careful in reading the manual
mvn versions:dependency-updates-report
creates the HTML report while
mvn versions:display-dependency-updates
prints to the console
Related
I am having error “Could not parse build number : ${${build.number}} while executing maven / java project through Jenkins.
If i run directly through Maven it works.
Any idea what could be the cause of this issue?
Thanks
You can refer the build number directly like,
${BUILD_NUMBER} instead of ${${build.number}}
otherwise you can pass it from goals and options sections.
clean install -Dbuild.number=${BUILD_NUMBER}
then you can refer it in POM like ${build.number}
Use ${env.BUILD_NUMBER} instead of ${${build.number}}
I am trying to get jacoco report for my project using jenkins. But its giving wrong report. it includes __cobertura* methods also.
effective pom here
I am getting correct report using maven install from eclipse.
But if I build using jenkins for the same class I am getting weird results. It includes __copertura generated methods. and there are huge difference in the other method coverages too. can I get the same result as I am getting in eclipse ?
[click][2]
[2]: https://i.stack.imgur.com/aojJ7.png
Found the problem
gave this maven command in jenkins
-B -U clean install cobertura:cobertura -Dcobertura.report.format=xml pmd:pmd pmd:cpd findbugs:findbugs
now removed and gave -B -U clean install alone. its working now
The question says it all really. How can I download or view the surefire-reports generated during a build on Travis?
You can just do
after_failure:
- cat target/surefire-reports/*.txt
Having not found a direct way to access the surefire-report files I came up with the this workaround:
In .travis.yml I added an after_failure hook:
after_failure: print_surefire_reports.sh
In the hook print_surefire_reports.sh I put:
#!/usr/bin/env sh
echo "Current directory is $(pwd)"
echo "\n=== SUREFIRE REPORTS ===\n"
for F in target/surefire-reports/*.txt
do
echo $F
cat $F
echo
done
I am using python html2text in travis after script phase.
My travis script looks like:
after_script:
- python html2text.py target/site/surefire-report.html
surefire-report.html is generated by surefire-report-plugin
See example output here: https://travis-ci.org/rmpestano/dbunit-rules/builds/160170324#L3541
Based on this bug report and this question, there is not a clean way to do this. There are, however, a couple unsupported methods of getting the reports listed in the bug report.
Those may provide options for you to look into, but the Travis CI maintainers have not provided or supported an explicit way to handle this yet. Note that those bug reports/questions are well over a year old too.
The prevailing suggestion in those threads seems to be to have Travis recommit the build artifacts back to the user's repository. This, however, requires authentication, which you probably shouldn't store in your .travis.yml file
Im working on getting our CI (Jenkins) to use and run our qunit test, we have qunit-reporter, qunit.compposite and phantomjs to execute the whole. Im not ant expert so im using windows batch command as a prestep with the following command
phantomjs src\test\webapp\js\runner.js src\test\webapp\jquery.all.test.html > test-report.xml
Now this runs and generates the junit xml file, with a few issues, firstly since I use pipe phantomjs performance information is also put into the file so that's my first issue
My second issue is that I have no idea in the world how I can get Jenkins to actually read the xml file instead of just considering it random stuff, similar to it interpreting when we have junit test run.
Just for reference the project is a maven project.
All advice is welcome :)
In Jenkins, configure your job, add a post build action, select publish JUnit test result report then add the path to your xml file in the requested field.
A couple years ago, a colleague of mine and I worked on getting PhantomJS to run QUnit tests and output JUnit XML that Jenkins can consume:
http://www.cameronjtinker.com/post/2013/09/24/QUnit-JSCoverage-and-Jenkins.aspx
I had forgotten to post this on my blog after we worked on this so I just posted it today when I saw your question. Much has changed since 2011 when this was originally written, but it should have most of the same concepts involved.
I'm trying to run a jython script from my Junit testcases. I have included the maven-jython-plugin.jar and jython.jar as well. As well as updated my pom.xml file accordingly. But when I run 'mvn install', I get following error:
Failed to execute goal net.sf.mavenjython:jython-compile-maven-plugin:1.0:jython (pydevLockUnlock) on project NTLauncherTest: extracting org/python/antlr/op/AugLoad.class from jython artifact jar failed: target/jython-plugins-tmp/org/python/antlr/op/AugLoad.class (Too many open files)
Does anyone know what I might be doing wrong and have a solution for this?
The issue is that maven can keep a lot of jar filehandles open. Check out this link for suggestions on how to troubleshoot that.
http://www.thinkplexx.com/learn/howto/maven2/debug/fixing-too-many-open-files-maven-problem-solution-for-teamcity-hudson-local-and-ssh-shell-environments
I've found that just re-running mvn install can lead to a successful build.