{jenkins-plugin-info:support-core|jiraComponent=support-core|sourceDir=support-core-plugin} |
This plugin provides a common set of classes to assist in generating support bundles. |
The plugin provides the basic infrastructure for generating "bundles" of support information within Jenkins.
There are three ways of generating bundles:
<yourJenkinsInstanceUrl>/cli/command/support embedded documentation.
As part of the support bundle if the About Jenkins option is checked then you will receive a docker file in the bundle also. The docker file contains the current version of Jenkins, along with a wget operation to download all of the plugins on the Jenkins master. This creates a similar environment for testing or reproducing bugs.
First build the image:
docker build -f Dockerfile
then run the docker image
docker run -d -p 8080:80
This should create a new Jenkins master with the same version, and the same plugins and versions all bundled.
Various companies and organizations provide commercial support for Jenkins. They can provide additional content and branding to the support action. The following lists the known third party support providers (in date order) and the links to their support provider plugin.
The most common situation for this to happen is when the About Jenkins option is enabled.
Meanwhile, the support bundle is getting generated it looks like the generation process is stuck as the downloaded size stays at the same point for a long time. To diagnosis this issue the best is to take a threadDump when in the moment where it is stuck and check the Jenkins logs.
If a stacktrace like the one below appears
"Handling POST /support/download from XX.XX.XX.XX : RequestHandlerThread[#126]" Id=123772 Group=main RUNNABLE at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242) at java.io.File.isDirectory(File.java:849) at com.cloudbees.jenkins.support.impl.AboutJenkins$ItemsContent.printTo(AboutJenkins.java:641) at com.cloudbees.jenkins.support.api.PrintedContent.writeTo(PrintedContent.java:47) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:359) at com.cloudbees.jenkins.support.SupportAction.doDownload(SupportAction.java:154) |
and the Jenkins logs are populated with
2018-01-04 04:52:17.633+0000 [id=123769] WARNING c.c.j.support.SupportPlugin#writeBundle: Could not attach 'nodes/slave/Slave1/checksums.md5' to support bundle org.eclipse.jetty.io.EofException: Closed at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:476) at net.bull.javamelody.FilterServletOutputStream.write(FilterServletOutputStream.java:88) at net.bull.javamelody.CounterResponseStream.write(CounterResponseStream.java:82) at org.apache.tools.zip.ZipOutputStream.writeOut(ZipOutputStream.java:1029) at org.apache.tools.zip.ZipOutputStream.deflate(ZipOutputStream.java:680) at org.apache.tools.zip.ZipOutputStream.closeEntry(ZipOutputStream.java:432) at org.apache.tools.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:489) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:358) at com.cloudbees.jenkins.support.SupportAction.doDownload(SupportAction.java:154) |
Then, surely the problem is that you are hitting the Idle timeout in the load balancer and this makes the connection betweek the ELB and your broweser to drop. To workaround this problem you can:
Beginning in version 2.48, this plugin now allows for automated ContentFilter extensions to enable anonymizing of various data. By enabling this feature, the default set of filters will anonymize agent names, agent computer names, agent labels, view names (aka folders), job names, usernames, and IP addresses (both IPv4 and IPv6). These data are mapped to randomly generated fake names which are saved to Jenkins master. A Jenkins administrator can view these mappings by going to Manage Jenkins › Support Bundle Anonymization. All files written to the support bundle by this and all extensions of this plugin will replace all instances of the original values with their anonymized counterpart. Note that the Stop Words list on that page shows which terms are ignored when filtering names (case-insensitive full match).
Anonymization filters only apply to text files. It cannot handle non-Jenkins URLs, custom proprietary Jenkins plugin names, and exceptions quoting invalid Groovy code in a Jenkins pipeline. The active plugins, disabled plugins, failed plugins, and Dockerfile reports are not anonymized due to several Jenkins plugins and other Java libraries using version numbers that are indistinguishable from IP addresses. These reports are in the files plugins/active.txt, plugins/disabled.txt, plugins/failed.txt, and docker/Dockerfile. These files should all be manually reviewed if you do not wish to disclose the names of custom proprietary plugins.
Request/response statistics. Tallying command read/write events.
-Dcom.cloudbees.jenkins.support.impl.HeapUsageHistogram.DISABLED=false to restore heap histogram generation, pending a better fix.Sort thread dumps by name rather than ID.
Reduce pressure on master file descriptors.
ClassCastException possible on 2.50+.
ClassCircularityError after creating a log recorder with a blank logger name.No changelog recorded, blame Kohsuke Kawaguchi!
slow-requests was missing stack traces.other-logs/*.log.