I am using Jenkins for Code analysis. My problem is when I am building project using option "built now". It is not showing me process status. I have to reload page every time I click on any place. In project built, if I am clicking on console output then even in console output is not showing until I am reload browser page. When I started initial I haven't faced this problem. Problem started after project built count is above 50. As I am building daily I am facing this problem after 50 days.
Details :
**
jenkins 1.617
sonarcube 5.1.1
sonar runner 2.4
**
There is an option to enable auto refresh in jenkins - hope that helps
Related
I was using Jenkins for a while and everything was working perfectly fine. But two or three days back i need to change some configuration for one of my project and when i hit apply button after performing those change. This error screen appears. Even i don't change anything and click apply button same error screen pops up.
I am currently using Jenkins version 2.265
this error occur when i hit this button
I downgrade jenkins to version 2.263 and everything starts working fine. So i think this issue is specific to Jenkins version 2.265
I had the same issue and it was caused by the now deprecated Coverity plugin. I would suggest you to check your deprecated plugins that add a section/options in the configuration and remove them.
I had same issue, it was because of "dark mode extension" on google chrome. It was ok on firefox, but chrome not. I suggest to disable dark mode extension on chrome when using jenkins.
Ever since we upgraded to 1.614 we have a problem with a certain hierarchy of tasks.
Two tasks are being stuck in "pending" every once in a while.
One task is descendant of the other and we indicate:"Block build when downstream project is building"
Notice that it does not say "Downstream project <> ..."
I have tried to upgrade again and we are currently on version 1.616
To solve this I cancel one of the tasks manually and the other one starts to run, but they are stuck until I notice that.
Can I prevent it from happening or at least auto cancel somehow when it happens?
Re "Can I [...] auto cancel somehow when it happens?"
See Build-timeout Plugin:
This plugin allows you to automatically abort a build if it's taking too long. Once the timeout is reached, Jenkins behaves as if an invisible hand has clicked the "abort build" button.
Seems like there is an issue in Jenkins that should was solved in 1.618
Problem did not reoccur after upgrading
I am facing an issue while running sonar through Jenkins, after configuration when I making build by build now trigger my build runs and creating EAR successfully then sonar deployment starts which also run successfully and showing ANALYSIS SUCCESSFUL in the end of Jenkins build processing but even after successful analysis of sonar build continue to process and it never ends even after a long time wait. Very last line of build processing is
"12:55:14.159 INFO - <- Delete aborted builds"
pls see attached screenshot to refer.
can anybody help me out over this issue?
what is the reason behind this continuous processing of sonar analysis?
it never complete. what should I do at my end to complete build process so that my build become successful in the end?
Try restarting Jenkins. It solved the issue for me.
The ANALYSIS SUCCESSFUL message just means that all sensors and decorators have completed. There are still some post-analysis tasks which must take place (specifically, any class extending PostJob). I've found that the final log output message is not always an accurate indicator of what's wrong. There are some plugins which churn forever but don't produce any output. But I wouldn't be surprised if your analyses really are stuck at "Delete aborted builds." Sometimes the Database Cleaner can take a long time, but if it's more than 10 minutes, it's stuck. It's very likely a problem with database interaction.
The way to continue is to enable all possible SQL tracing. Enable all the options -- sonar.showProfiling=true, sonar.showSql=true, sonar.showSqlResults=true, and sonar.verbose=true. See the Sonar Analysis Parameters for more information.
If that doesn't tell you what's wrong, you might have some luck getting more information out of sonar.log by editing wrapper.conf to show DEBUG log output.
I've got a job that runs for a long time (for example, it builds few solutions), Is there a way to know the current solution that is beind compiled on runtine?
I mean, the Log is very long, so sometimes is confusing to know what is the current compilation that is running.
I want to know what is the current solution that is being compiled now...
Any plugin or a way to do that?
It would be easier to diagnose problems if you split the job into multiple jobs (each one building a single solution). If you have dependencies between the different builds (i.e. one part of the build cannot happen until another part has completed), you can create a build pipeline, where once one job finishes, it triggers the next job in the pipeline. You can do this using the post-build action Build other projects in the job configuration.
There is also an excellent build pipeline plugin which helps you visualize your build pipeline.
If it is the case that you must have the whole solution built in a single job, then one approach would be to use the Jenkins log parser plugin to display a cut-down version of your build log, which just highlights the key events you are interested in to diagnose such problems.
More details of this plugin can be found at:
https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin
I've got two ideas for a possible solution but they needed to be implemented:
1. Adding a prefix for each row in the Log. The prefix could be a string.
for example, if there was a new Project Compilation started then the Log finds the line
----- Rebuild All started: Project: PROJ1 , Configuration: Release x64 ------
Then it adds all the rows after it the prefix "Building PROJ1"
until the log reads the next project:
----- Rebuild All started: Project: PROJ2 , Configuration: Release x64 ------
2. Adding a the current project name that's building to the flashing Job status blue ball.
I mean, finding the current building project from the Log, then adding it next to the current job status (the flickering ball).
We use a few tweaked Build Process Template, developed for TFS2010 for all of our builds, but these BPTs are not using any custom activities. We recently upgraded to TFS2012, and during the upgrade converted our BPTs according to these instructions.
This works fine, most of the time, but periodically, it coughs up:
TF215097: An error occurred while initializing a build for build definition \Project1 (Dev10)\Simple - Manual: The values provided for the root activity's arguments did not satisfy the root activity's requirements:
'DynamicActivity': Expected an input parameter value of type 'Microsoft.TeamFoundation.Build.Workflow.Activities.BuildSettings' for parameter named 'BuildSettings'.
There's nothing in any log, there's nothing visible that I can see as the root cause in any way. The only fix is to restart the Build Controller, at which time the error vanishes for a few hours. When I unregistered and re-registered the Controller, the problem went away for about a day.
The important thing here is that these build process templates do work on TFS2012, but then they suddenly stop working for no reason I can determine.
As it turns out, some builds were still using legacy 2010-style Build Process Templates. Any time someone queued one of those builds, the entire build controller started freaking out. By getting rid of those BPTs, we resolved the issue.