Domi, I have updated the M2 release plugin to version 0.9, so now in the build configuration I see a new entry "Release envrionment variable" with value IS_M2RELEASEBUILD. In the sonar configuration, I have set this value in the "Skip if environment variable is defined". I think with these two configurations sonar should be skipped in a maven release, however sonar keeps executing. Am I doing something wrong? Is this the way to exclude sonar ina maven release?
Thanks in advance. On Jan 31, 6:43 pm, domi <d...@fortysix.ch> wrote: > Tomasz, > this is possible as soon as the new version of the m2release plugin is out > (see the new features in the history of the next release > version):https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin > One of the new features is: parameters defined on the job will also be > presented to you when doing a release build. > So together with the newest version of the sonar plugin, this will allow you > to disable the sonar step during a release build. > I made a private release of the plugin and we already use this feature at > work. > James, the maintainer of the m2release plugin, is about to release the new > version soon, so please be patient for some more days and you'll get what you > are looking for :) > regards Domi > > On 31.01.2012, at 09:38, Tomasz Kaczanowski wrote: > > > > > > > > > Hi All, > > > I have a multimodule build which uses Sonar. All works fine when performing > > "normal builds" (e.g. by clicking Build Now) - mvn clean install runs, all > > modules are build, and then Sonar is executed. Nice. > > > The problem starts when performing maven release. I use M2 release plugin > > for this. The flow is the following > > 1) mvn does its job (release:perform etc) > > 2) mvn updates pom to x.y-SNAPSHOT (but does not build them nor install > > them) > > 3) sonar executes, and tries to work with x.y-SNAPSHOT > > 4) sonar fails because the x.y-SNAPSHOT is nowhere to be found > > > How to make this scenario work? I would be happy to: > > a) disable sonar for release builds > > b) make sonar work with x.y instead x.y-SNAPSHOT with when performing > > release > > > Of course, I could add another job (so I have myproject and > > myproject-release jobs) and switch off sonar for the second job, but I > > would like to have only one job if possible. Any hints? > > > My configuration: Jenkins: 1.449, Sonar plugin 1.8, M2 Release plugin 0.8.1 > > > -- > > Tomasz Kaczanowski > > Senior Software Engineer > > > Software Mind SA| Where Quality Meets the Future > > ul. Bociana 22a > > 31-231 Krakow > > Poland > > Tel. +48 12 252 34 00 > > Fax: +48 12 252 34 01 > > tomasz.kaczanow...@softwaremind.pl > > skype: tkaczanowski_sm > >http://www.softwaremind.pl > > > Software Mind SA based in Krakow at ul. Bociana 22A, 31-231 Krakow > > NIP 9452012822, seed capital PLN 500,000.00 (fully paid up) > > District Court Kraków Śródmieście, XI Economics Department > > of the National Court Register, KRS 0000300409 > > > ****************************** LEGAL DISCLAIMER************************* > > This email may contain confidential and privileged material for the > > sole use of the intended recipient(s). Any review, use, retention, > > distribution or disclosure by others is strictly prohibited. If you are > > not the intended recipient (or authorized to receive for the > > recipient), please contact the sender by reply email and delete all > > copies of this message. Also, email is susceptible to data corruption, > > interception, tampering, unauthorized amendment and viruses. We only > > send and receive emails on the basis that we are not liable for any > > such corruption, interception, tampering, amendment or viruses or any > > consequence thereof.
