I have a strange behaviour while analysing my Java Code.
The analysis is done on a daily basis.
On the first run some issue are identified, so far so good.
After the next run there are issues marked as Fixed.
The Message i got in sonarQube:
Juli 2015 10:33 Uhr Created
Juli 2015 20:30 Uhr Resolution changed to FIXED
Status changed to CLOSED (was OPEN)
But there was no change at this File between the two runs.....
Java: JDK 1.8.0_u45
SonarQube: 5.1.1
Any Idea???
Thanks in advance
Kai
Related
I am using open-source Pentaho distribution from github.com (version 6.1-SNAPSHOT).
In Spoon there are some step missing (e.g. There is no Mongodb input/output step listed) and I cant add dataservice to step (There are no errors, this option just isn't on the list).
I have reinstalled everything (removed .kettle and .pentaho directories as well as whole source and distribution) but it didn't help.
This is what I get at spoon startup:
16:05:50,304 INFO [KarafInstance]
* Karaf Instance Number: 1 at ~/pentaho-kettle/d
ist/./system/karaf//data1
Karaf Port:8801
OSGI Service Port:9050 *
Dec 23, 2015 4:05:51 PM org.apache.karaf.main.Main$KarafLockCallback
lockAquired
INFO: Lock acquired. Setting startlevel to 100
2015/12/23 16:05:53 - cfgbuilder - Warning: The configuration
parameter [org] is not supported by the default configuration builder
for scheme: sftp
Dec 23, 2015 4:05:58 PM
org.pentaho.caching.impl.PentahoCacheManagerFactory$RegistrationHandler$1
onSuccess INFO: New Caching Service registered
16:06:04,009 ERROR [KarafLifecycleListener] The Kettle Karaf Lifycycle
Listener failed to execute properly. Releasing lifecycle hold, but
some services may be unavailable.
I suspect that
ERROR [KarafLifecycleListener] The Kettle Karaf Lifycycle Listener
failed to execute properly. Releasing lifecycle hold, but some
services may be unavailable.
has something to do with it as missing plugins reside somewhere under karaf/ directory.
It was working just fine week ago.
I am using Ubuntu 15.04.
I will be grateful for any hints.
Greetings.
you are using a non stable release. this is the place where you can download the latest stable release http://sourceforge.net/projects/pentaho/
Agreed with jipipayo, For Pentaho CE version, download it from http://community.pentaho.com/ official instead of github. It is highly possible that the codes in github might be in unstable condition.
Also in case you have a missing plugin, try using the Pentaho Marketplace and download the required plugins.
Hope this helps :)
I have setup a project with a specific date in sonar.timemachine.period5 in my project.properties file. This usually works perfectly, but sometimes the sonarqube runner doesn't make the comparison.
sonar.timemachine.period5=2015-11-04
Here is a part of the log output from two consecutive sonar-runner analysis:
This one is not comparing against period 5:
10:28:17.546 INFO - Loaded quality gate 'MyProject'
10:28:17.591 INFO - Compare to previous analysis (2015-10-26)
10:28:17.596 INFO - Compare over 30 days (2015-10-24, analysis of Mon Oct 26 09:26:01 CET 2015)
10:28:17.597 INFO - Compare to previous version (2015-10-26)
while this one is....
10:37:43.996 INFO - Loaded quality gate 'MyProject'
10:37:44.054 INFO - Compare to previous analysis (2015-11-23)
10:37:44.060 INFO - Compare over 30 days (2015-10-24, analysis of Mon Oct 26 09:26:01 CET 2015)
10:37:44.061 INFO - Compare to previous version (2015-11-23)
10:37:44.062 INFO - Compare to date 2015-11-04 (analysis of 2015-11-23
Any clues on why this is happening?
The result is that the project sometimes passes the qualitygate when it certainly shouldn't.
Im running SonarQube 5.1.2 and using Sonar-Runner 2.4
Periods 4 and 5 are not set globally but on the project level. Double-check your first project to make sure it has a valid Period 5 value.
I have been pulling my hair out trying to install Security Update 2015-006 on my MacBook7,1. Tried AppStore 3x, no go. Downloaded standalone Installer and tried this one 5x. Same result every time. Gets all the way through 95+% to the point where it's simply cleaning up and then it just falls with:
The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
In the system log:
Sep 8 18:30:20 MacBookPro71.local Installer[1022]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
Sep 8 18:30:20 MacBookPro71.local Installer[1022]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Sep 8 18:30:22 MacBookPro71.local com.apple.kextd[12]: /: kextcache has had enough tries; not launching any more
-----
I've already tried deleting the contents of /Library/Updates and /var/folders which has worked in the past but makes no difference this time.
Anybody ?
TIA !
I'm getting the following lines on app startup.
Application works fine though:
Jun 22 18:29:54 Alexeys-iPod-touch xxx[1169] : WARNING: The
runtime version supported by this application is unavailable. Jun 22
18:29:54 Alexeys-iPod-touch xxx[1169] : Using default
runtime: v4.0.30319
What should I do about it (and should I)?
This is just some debug spew we haven't had time to remove yet.
You can safely ignore it.
I need to know the teamcity settings which prevents the re-trigger/trigger of outdated builds/jobs if the new builds are successful.
I am facing a issue where teamcity jobs can be re triggered even if the next builds are successful.And If the trigger event is fired before, then it must stop teamcity to run that job if the latest build is successful.
So I have to 2 jobs in TC for 1 branch -- Build-Precheck and the other is Build-compile
So I could see that Build-compile is just picking the latest available successful build from Build-Precheck and then queing up the next which may be the outdated build.
Build-Precheck is just taking 2 min to finish the builds , it quickly triggers the latest builds , I guess following the principal First In First Out
Build-Precheck
06 Oct 14 14:33 - 14:35 (2m:01s) –7.1.4345
06 Oct 14 14:41 - 14:43 (2m:16s)- 7.1.4346
06 Oct 14 14:45 - 14:47 (2m:10s)- 7.1.4347
Build-compile
06 Oct 14 14:35 - 15:00 -7.1.0.4345
06 Oct 14 14:52 - 15:20 (28m:02s)- 7.1.4347
06 Oct 14 16:08 - 16:33 (24m:52s)- 7.1.4346
Is there any fix for this that TC runs incremental builds rather than outdated ones
Sounds like you are looking for Configuring Build Trigger.
AFAIK, there isn't a way to cancel queued builds if a given build passes. However, you can adjust the Build Triggers that queue those builds. Most likely, you'll need to set the Quiet Period on your VCS Build Trigger to longer than it takes for your build.
For example, if your full build takes 5 minutes, you should set the Quiet Period to 7. This way additional builds wont queue while a build is running.