[JIRA] (JENKINS-14261) Builds hanging right before e-mail notifications are sent out - Mercurial
Slide-O-Mix commented on JENKINS-14261 Builds hanging right before e-mail notifications are sent out - Mercurial This looks like its having issues with mail address resolution. This is similar to issues that several other users are having with the email address resolution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9895) Wall Display Plugin shows "MavenModuleSet:MavenModuleSet"
cforce commented on JENKINS-9895 Wall Display Plugin shows "MavenModuleSet:MavenModuleSet" Its working now. Tx for fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9895) Wall Display Plugin shows "MavenModuleSet:MavenModuleSet"
cforce closed JENKINS-9895 as Fixed Wall Display Plugin shows "MavenModuleSet:MavenModuleSet" Fixed! Change By: cforce (12/Jul/12 6:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9216) Make OpenID work with Google Apps accounts
SCM/JIRA link daemon resolved JENKINS-9216 as Fixed Make OpenID work with Google Apps accounts Change By: SCM/JIRA link daemon (12/Jul/12 1:57 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9216) Make OpenID work with Google Apps accounts
SCM/JIRA link daemon commented on JENKINS-9216 Make OpenID work with Google Apps accounts Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/openid/GoogleAppSsoSecurityRealm.java http://jenkins-ci.org/commit/openid-plugin/c2f725f9dd25462edf95a5e3a59759538ab23136 Log: [FIXED JENKINS-9216] Reworked the change based on the comment in the ticket. This approach does not skip any checks, so it doesn't compromise on security. Compare: https://github.com/jenkinsci/openid-plugin/compare/51272cc7dd48...c2f725f9dd25 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14399) Failed to parse form data. Please report this problem as a bug
Kamal Ahmed
created JENKINS-14399
Failed to parse form data. Please report this problem as a bug
Issue Type:
Bug
Affects Versions:
current
Assignee:
nidaley
Components:
plot
Created:
12/Jul/12 1:02 AM
Description:
Failed to parse form data. Please report this problem as a bug
JSON={"":"Monitor Disk Usage of self","builder":{"command":"#!/bin/bash\necho \"YVALUE=\"`df -H 1073741824 | grep rootfs | awk – '{print $5}' | tr -d %` > disk-used_root.properties\necho \"YVALUE=\"`df -H 1073741824 | grep /var/temp | awk – '{print $4}' | tr -d %` > disk-used_tmp.properties\ncat disk-used_share.properties\ncat disk-used_data.properties","kind":"hudson.tasks.Shell","stapler-class":"hudson.tasks.Shell"},"core:apply":"","description":"Monitor Disk Usage of self","displayNameOrNull":"","hudson-triggers-TimerTrigger":{"spec":"@daily"},"logrotate":{"logrotate_artifact_days":"","logrotate_artifact_nums":"","logrotate_days":"","logrotate_nums":"20"},"name":"DiskUsage","properties":{"hudson-model-ParametersDefinitionProperty":{},"hudson-plugins-svn_release_mgr-JobPropertyImpl":{},"hudson-plugins-trackingsvn-TrackingSVNProperty":{},"stapler-class-bag":"true"},"publisher":{"kind":"hudson.plugins.plot.PlotPublisher","plots":{"csvFileName":"","group":"Disk Usage QA-Jenkins","numBuilds":"20","series":[{"file":"disk-used_root.properties"},{"file":"disk-used_tmp.properties","fileType":{"label":"tmp","value":"properties"}}],"style":"line","title":"Disk Usage","useDescr":true,"yaxis":"GB"},"stapler-class":"hudson.plugins.plot.PlotPublisher"},"scm":{"value":"1"}}
net.sf.json.JSONException: null object
at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2428)
at net.sf.json.JSONObject.element(JSONObject.java:1486)
at net.sf.json.JSONObject.element(JSONObject.java:1469)
at net.sf.json.JSONObject.put(JSONObject.java:2065)
at hudson.plugins.plot.SeriesFactory.createSeries(SeriesFactory.java:27)
at hudson.plugins.plot.SeriesFactory.createSeriesList(SeriesFactory.java:43)
at hudson.plugins.plot.PlotPublisher$DescriptorImpl.bindPlot(PlotPublisher.java:231)
at hudson.plugins.plot.PlotPublisher$DescriptorImpl.newInstance(PlotPublisher.java:224)
at hudson.plugins.plot.PlotPublisher$DescriptorImpl.newInstance(PlotPublisher.java:202)
at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:912)
at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:899)
at hudson.util.DescribableList.rebuildHetero(DescribableList.java:184)
at hudson.model.Project.submit(Project.java:203)
at hudson.model.Job.doConfigSubmit(Job.java:990)
at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:691)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher
[JIRA] (JENKINS-14397) create jenkins user with full name
abayer commented on JENKINS-14397 create jenkins user with full name So I've opted to solve this in jclouds via just setting the GECOS field to the username for now, which will mean we don't need to do anything on the Jenkins side. woo! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11973) AVD should be in workspace instead of system-global
Jørgen Tjernø commented on JENKINS-11973 AVD should be in workspace instead of system-global I ended up making this configurable on a global level, that made more sense to me. Feel free to change it to per-job (maybe later?) if you think that's better - but I'd rather not have to go and enable it on all our jobs. Pull request: https://github.com/jenkinsci/android-emulator-plugin/pull/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14398) Hard to find IP address of jclouds created slave
Monty Taylor created JENKINS-14398 Hard to find IP address of jclouds created slave Issue Type: Bug Assignee: abayer Components: jclouds Created: 11/Jul/12 11:12 PM Description: When jclouds creates a slave and something goes wrong, I want to log in to it to investigate. Unfortunately, it's kinda hard to find the IP address of the node. It would be stellar if it could be recorded or shown somewhere fun. Project: Jenkins Priority: Major Reporter: Monty Taylor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14397) create jenkins user with full name
Monty Taylor created JENKINS-14397 create jenkins user with full name Issue Type: Bug Assignee: abayer Components: jclouds Created: 11/Jul/12 11:11 PM Description: When jclouds creates the jenkins user, it does so with a blank full name. There is a jclouds issue to provide support in AdminAccess to specify one. http://code.google.com/p/jclouds/issues/detail?id=1020 It doesn't really matter what it is - is just needs to be something or else git whinges. Project: Jenkins Priority: Major Reporter: Monty Taylor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14396) honor Remote FS root
Monty Taylor created JENKINS-14396 honor Remote FS root Issue Type: Bug Assignee: abayer Components: jclouds Created: 11/Jul/12 11:10 PM Description: I spun up slaves with jclouds-plugin. I had remote fs root set to /home/jenkins - it created the homedir as /home/users/jenkins instead. This will cause my puppet things that want to put things in /home/jenkins to be unhappy. Project: Jenkins Priority: Major Reporter: Monty Taylor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14365) Wacky number for changes in build using Mercurial plugin
dogfood commented on JENKINS-14365 Wacky number for changes in build using Mercurial plugin Integrated in jenkins_main_trunk #1805 Result = UNSTABLE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14330) NPE from UnlabeldLoadStatistics.computeTotalExecutors
dogfood commented on JENKINS-14330 NPE from UnlabeldLoadStatistics.computeTotalExecutors Integrated in jenkins_main_trunk #1805 Result = UNSTABLE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14325) CCE "...cannot be cast to jenkins.model.Jenkins" in job index page
dogfood commented on JENKINS-14325 CCE "...cannot be cast to jenkins.model.Jenkins" in job index page Integrated in jenkins_main_trunk #1805 Result = UNSTABLE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14395) S3 Plugin credentials stored insecurely
Theral Mackey created JENKINS-14395 S3 Plugin credentials stored insecurely Issue Type: Bug Assignee: mcrooney Components: s3 Created: 11/Jul/12 10:07 PM Description: S3 Bucket credential keys (both access and secret) are stored/managed in such a way that anyone with access to the config page can easily retreive them (easy as in view-source). Once saved, they should not be retrievable through the web interface. Project: Jenkins Priority: Critical Reporter: Theral Mackey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14347) Global & node level self-referencing variables should work
SCM/JIRA link daemon commented on JENKINS-14347 Global & node level self-referencing variables should work Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectComputerListener.java http://jenkins-ci.org/commit/envinject-plugin/224689bc0adc5cd3ab4918704cd5b48324b54064 Log: Fix JENKINS-14347 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14379) Wall Display Plugin fails when hits the build with 'yellow' status
SCM/JIRA link daemon commented on JENKINS-14379 Wall Display Plugin fails when hits the build with 'yellow' status Code changed in jenkins User: Pelle Pelster Path: src/main/webapp/utils.js http://jenkins-ci.org/commit/walldisplay-plugin/2f4883da16109ef95e51d6fc7b3de24e85947432 Log: JENKINS-14379 Wall Display Plugin fails when hits the build with 'yellow' status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14394) The version 1.1.21 breaks
Yi Wen created JENKINS-14394 The version 1.1.21 breaks Issue Type: Bug Assignee: Nicolas De Loof Attachments: Screen Shot 2012-07-11 at 3.28.26 PM.png, Screen Shot 2012-07-11 at 3.29.30 PM.png Components: git Created: 11/Jul/12 8:29 PM Description: Hi, I have a job which requires a param: to specify a branch name. Up to the version 1.1.20. In 1.2.11, when I do that. error happens like this: Fetching changes from 1 remote Git repository Fetching upstream changes from g...@github.com:mycompany/myrepo.git Pruning obsolete local branches ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Recording fingerprints An attempt to send an e-mail to empty list of recipients, ignored. Email was triggered for: Failure Sending email for trigger: Failure An attempt to send an e-mail to empty list of recipients, ignored. Notifying upstream projects of job completion Finished: FAILURE No clue why. Downgrade to 1.1.20. The job back to normal. Please see the attached files to see my config related to git Thanks Project: Jenkins Priority: Major Reporter: Yi Wen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14379) Wall Display Plugin fails when hits the build with 'yellow' status
Christian Pelster resolved JENKINS-14379 as Fixed Wall Display Plugin fails when hits the build with 'yellow' status thanks for the quick fix Change By: Christian Pelster (11/Jul/12 8:25 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14355) create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD)
Antoine Musso assigned JENKINS-14355 to Marc Sanfacon create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD) Sending you this finger print plugin bug. Might be a core issue though. Change By: Antoine Musso (11/Jul/12 7:50 PM) Assignee: Marc Sanfacon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14356) JIRA: no 'create-fingerprint-plugin' component
Antoine Musso closed JENKINS-14356 as Fixed JIRA: no 'create-fingerprint-plugin' component Change By: Antoine Musso (11/Jul/12 7:51 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14355) create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD)
Antoine Musso updated JENKINS-14355 create-fingerprint-plugin cant find .dotfiles (e.g.: .git/FETCH_HEAD) Change By: Antoine Musso (11/Jul/12 7:51 PM) Component/s: fingerprint Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14356) JIRA: no 'create-fingerprint-plugin' component
Antoine Musso resolved JENKINS-14356 as Fixed JIRA: no 'create-fingerprint-plugin' component solved by imod via IRC. jenkins-admin: Create fingerprint in the issue tracker for hashar Adding a new subcomponent fingerprint to the bug tracker, owned by hashar jenkins-admin: Make marcsanfacon the lead of fingerprint Changing default assignee of subcomponent fingerprint to marcsanfacon Change By: Antoine Musso (11/Jul/12 7:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14393) Jenkins CLI is not giving enough information to builds that it kicks off
Kyle Allan commented on JENKINS-14393 Jenkins CLI is not giving enough information to builds that it kicks off I will be forking and submitting a pull request to fix this bug shortly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14393) Jenkins CLI is not giving enough information to builds that it kicks off
Kyle Allan
updated JENKINS-14393
Jenkins CLI is not giving enough information to builds that it kicks off
Change By:
Kyle Allan
(11/Jul/12 6:28 PM)
Description:
When I kick off a build using jenkins-cli.jar, the causes element is as follows:"causes": [{"shortDescription": "Started by command line by kallan"}]When I kick off the same build from the web UI, I have access to more information:"causes": [{"shortDescription": "Started by user Kyle Allan","userId": "kallan","userName": "Kyle Allan"}]When Jenkins is working in conjunction with: Email-ext Plugin, version 2.22, this is not enough information to trigger the code to send an email to 'Requestors' (the individual who kicks off the build). The relevant code for this logic can be found in https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java#L463
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14393) Jenkins CLI is not giving enough information to builds that it kicks off
Kyle Allan created JENKINS-14393 Jenkins CLI is not giving enough information to builds that it kicks off Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli, core Created: 11/Jul/12 6:25 PM Project: Jenkins Priority: Minor Reporter: Kyle Allan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9364) Add support for tokens from the token-macro plug-in
Vlad Melnyk
commented on JENKINS-9364
Add support for tokens from the token-macro plug-in
This build of ${ENV, var="application"} on ${ENV, var="branch"} was triggered by commit "http://git.mycompany.com/?p=rep.git&a=commit&h=${ENV, var="commit"}">${ENV, var="commit"}: ${ENV,var="commit_message"}
Author: ${ENV, var="author_name"}
Email: ${ENV, var="author_email"}
Failed Tests
You can check complete test results "${BUILD_URL}testReport">here
${FAILED_TESTS, showStack="false"}
Build Log
You can check the complete build log "${BUILD_URL}console">here
${BUILD_LOG, maxLines=100, escapeHtml=true}
I received the following email:
This build of ${ENV, var="application"} on ${ENV, var="branch"} was triggered by commit ${ENV, var="commit"}: ${ENV,var="commit_message"}
Author: ${ENV, var="author_name"}
Email: ${ENV, var="author_email"}
Failed Tests
You can check complete test results here
1 tests failed.
..
Build Log
You can check the complete build log here
[...truncated 188 lines...]
Before I installed 2.23-SNAPSHOT I also got the following messag ein the logs:
Error substituting with token-macro plugin: org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'search'
When I removed ${BUILD_LOG, maxLines=100, escapeHtml=true} token, EVN token were expended properly. Looks like "search" token is present in my console logs
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6368) SVN plugin is not supported by github.com
Michael Prokop commented on JENKINS-6368 SVN plugin is not supported by github.com Verified with Jenkins 1.472 and Jenkins Subversion Plug-in 1.42, this issue is still present. Is there any chance that this might be supported? 19:21:45 Checking out a fresh workspace because /var/lib/jenkins/workspace/selenium-server-svn-source/source doesn't exist 19:21:45 Cleaning local Directory ./source 19:21:45 Checking out https://github.com/[...]/selenium-deb-pkg 19:21:48 ERROR: Failed to check out https://github.com/[...]/selenium-deb-pkg 19:21:48 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /[...]/selenium-deb-pkg/!svn/vcc/default failed 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304) 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289) 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277) 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696) 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328) 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:318) 19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:200) 19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:475) 19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getLocations(SVNBasicDelegate.java:838) 19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:527) 19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:925) 19:21:48 at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19) 19:21:48 at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8) 19:21:48 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14392) Optional Extensions are reloaded when dependencies are dynamically loaded
recampbell created JENKINS-14392 Optional Extensions are reloaded when dependencies are dynamically loaded Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Jul/12 5:36 PM Description: If a plugin A has an optional dependency on plugin B, and has marked an @Extension (optional=true), Jenkins will properly fail to load that extension. However, if plugin B is then later installed, the optional dependencies from plugin A are not re-evaluated. Jenkins should keep track of optional extensions which failed to load, and retry them when new plugins are installed. Perhaps it could only due so if the plugin for that extension expressed an optional dependency on the newly installed plugin, but even that doesn't seem necessary? This is really just a usability issue (since you can restart to fix it), but may prove frustrating for novice users. Project: Jenkins Priority: Major Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13841) "Base folder" for deploying the artifacty from source folder to remote directory
SCM/JIRA link daemon commented on JENKINS-13841 "Base folder" for deploying the artifacty from source folder to remote directory Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerBuilder.java src/main/java/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerEntry.java src/main/java/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerPublisher.java src/main/java/org/jenkinsci/plugins/artifactdeployer/DeployedArtifacts.java src/main/java/org/jenkinsci/plugins/artifactdeployer/service/ArtifactDeployerCopy.java src/main/java/org/jenkinsci/plugins/artifactdeployer/service/ArtifactDeployerManager.java src/main/resources/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerBuilder/help-basedir.html src/main/resources/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerBuilder/help-includes.html src/main/resources/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerPublisher/config.jelly src/main/resources/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerPublisher/help-basedir.html src/main/resources/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerPublisher/help-includes.html http://jenkins-ci.org/commit/artifactdeployer-plugin/ad3f87bf90647e84499629b13c3c055f2f3f0254 Log: Fix JENKINS-13841 Compare: https://github.com/jenkinsci/artifactdeployer-plugin/compare/7cadf00e2ffd...ad3f87bf9064 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}
Ronan Jouchet
commented on JENKINS-13347
Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}
Works! I think the more general bug remains valid, so I won't close yet.
Thanks for the help
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3002) TFS Support to get labels
Stanley Fong commented on JENKINS-3002 TFS Support to get labels When will this feature be supported and is there a workaround? We have a need to checkout from TFS using labels. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14382) Error in substituting macro when sending email
Slide-O-Mix resolved JENKINS-14382 as Duplicate Error in substituting macro when sending email Duplicate of JENKINS-14224 Change By: Slide-O-Mix (11/Jul/12 3:30 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14390) Distinguish user aborted from timeout aborted icon
Ben Golding created JENKINS-14390 Distinguish user aborted from timeout aborted icon Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 11/Jul/12 2:55 PM Description: I would like a different icon for a build that was aborted by the timeout plugin, versus a build that a user aborted through the web UI (or some other mechanism). Mouse-over the icon should also show different text (currently shows "Aborted", suggest "User Aborted" or "Timeout") This may require an extension to Jenkins core? Please reassign if necessary Environment: Jenkins 1.474 Build Timeout 1.10 Project: Jenkins Priority: Minor Reporter: Ben Golding This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14389) Extract total number of violations
Dror Banin created JENKINS-14389 Extract total number of violations Issue Type: Bug Assignee: peterkittreilly Components: violations Created: 11/Jul/12 2:52 PM Description: Hi, i need to get the total number of violations, and write a script that checks if this number had increased. Somebody know how/where can i extract this number? Thanks! Project: Jenkins Priority: Major Reporter: Dror Banin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14027) Can't run build flow configuration with parralell jobs
Vladimir Turin
commented on JENKINS-14027
Can't run build flow configuration with parralell jobs
I use different parameters in build. It works. The only problem was (in 0.3 version) to get it from parameters of flow. As far as I can see in discussion of plugin (see comments in wiki for Build+Flow+Plugin) the following sting should work in 0.4 version:
build("paramJob1", PARAM_1:params["BUILD_PARAM"])
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14388) Allow other emma-maven-plugins as precondition for Jenkins Emma Plugin
jglick commented on JENKINS-14388 Allow other emma-maven-plugins as precondition for Jenkins Emma Plugin Pull requests on https://github.com/jenkinsci/emma-plugin preferred to attaching patches, I think - easier to track and review. BTW your patch changes whitespace gratuitously. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14388) Allow other emma-maven-plugins as precondition for Jenkins Emma Plugin
Carsten Schalm created JENKINS-14388 Allow other emma-maven-plugins as precondition for Jenkins Emma Plugin Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: Jenkins-Emma-Plugin.patch Components: emma Created: 11/Jul/12 1:45 PM Description: Currently the Jenkins Emma Plugin only runs if the emma-maven-plugin from org.codehaus.mojo did run before. We use the plugin from org.sonatype.maven.plugin and don't get any coverage reports in Jenkins. Please be more liberal regarding the preconditions for running Jenkins Emma Plugin. For me the changes you can find in the attached patch-file helped to get coverage-reports, maybe checking of the groupId could be skipped completely? Project: Jenkins Labels: plugin jenkins emma Priority: Major Reporter: Carsten Schalm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14387) Cause of rebuilt job should be Cause.UserIdCause
blalor created JENKINS-14387 Cause of rebuilt job should be Cause.UserIdCause Issue Type: Improvement Assignee: ragesh_nair Components: rebuild Created: 11/Jul/12 1:26 PM Description: Cause.UserCause is deprecated. Project: Jenkins Priority: Major Reporter: blalor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14386) User-defined Axis used together with Slaves or label expression axis produces unusable environment variable values
aleksas created JENKINS-14386 User-defined Axis used together with Slaves or label _expression_ axis produces unusable environment variable values Issue Type: Bug Assignee: Unassigned Components: matrix Created: 11/Jul/12 1:19 PM Description: Using "User-defined Axis" to make two builds. Running them sets appropriate environment variables. To filter slaves on which to run builds I'm using label _expression_. This causes label _expression_ to be attached to variable defined in "User-defined Axis" value making it unusable. E.g. User-defined Axis: Target=x86 x64 Label _expression_: windows this case will produce env. variable Target=x86,ConditionA&&windows and Target=x64,windows when Target=x86 or Target=x64 is expected. Environment: Windows 2008 x64 java.runtime.version 1.7.0_04-b22 Project: Jenkins Priority: Major Reporter: aleksas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14027) Can't run build flow configuration with parralell jobs
Shailesh Ligade
commented on JENKINS-14027
Can't run build flow configuration with parralell jobs
I am using 1.471 with plugin 0.3. I have configured 9 parameterized jobs (defaults set). with anonymous access, it works properly with default parameter values. If I migrate plugin to 0.4 it fails as it can't use default parameter..
Is this plugin supposed to handle parameters? I mean If I make this job parameterized, and set up following way
parallel (
{ build ( "job1" , p1: "${p1}", p2: "${p2}", p3: "${p3}" ) },
{ build ( "job2" , p1: "${p1}", p2: "${p2}", p3: "${p3}" ) }
)
should it work?
Thanks
S
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14385) Jenkins stops responding after multiple chages to different jobs.
Kevin Thieling created JENKINS-14385 Jenkins stops responding after multiple chages to different jobs. Issue Type: Bug Assignee: wolfs Components: all-changes Created: 11/Jul/12 1:07 PM Description: We are having repeated issues of having to restart the Jenkins services if we make multiple changes close together in time. Jenkins will eventually stop responding until we restart the services. When this occurs the Servers CPU usage spikes. We do have multiple slaves , however, a lot of jobs are running on the master still. But, these issues do not appear to happen as something is building, only when making changes. I am not sure if this is an issue wil a certain plugin or something with the server that it can't handle all of those changes close together. Environment: Windows Server 2008 R2 64 bit Quad Core 3.10 Ghz 4GB RAM Project: Jenkins Priority: Critical Reporter: Kevin Thieling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14384) OutOfMemoryError at startup when parsing the build.xml
Richard Underhill created JENKINS-14384 OutOfMemoryError at startup when parsing the build.xml Issue Type: Bug Assignee: Unassigned Attachments: jenkis.log Components: core Created: 11/Jul/12 11:33 AM Description: We have a total of 29 jobs. 3 are "top-level" jobs that can be manually startet. 12 are intermediate "matrix jobs" and 14 are "leaf jobs" where the real work is done. Each of the 14 leaf job is called about 50 times when one top-level job is executed. So after a couple of days there are thousands of build artifacts. (I have a limit of 1000 per job). The problem occurs when jenkins must be stopped. Restarting jenkins does not work. The process takes up 100% CPU power and runs forever (I terminated it after a night. I have already increased the memory size (according to https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+OutOfMemoryError): java.exe -Xms512m -Xmx512m -jar jenkins.war But this does not help. I have to set up the server from scatch every time jenkins must be stopped. Otherwise the server runs smoothly for a couple of months, i.e. there is no memory shortage during normal operation only during startup. Environment: WinXP SP3, All versions since we started using Jenkins (1.445 was the first; currently we use 1.472). Project: Jenkins Labels: jenkins Priority: Major Reporter: Richard Underhill This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14383) Warnings Plugin: Slow Performance on customized parsing rules with Regular Expression
Tobias Schmetzer
created JENKINS-14383
Warnings Plugin: Slow Performance on customized parsing rules with Regular _expression_
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Ulli Hafner
Attachments:
logoutput.anonym.txt
Components:
warnings
Created:
11/Jul/12 11:13 AM
Description:
Hello,
I encountered severe performance problems when using the customized warnings parser plugin with regex.
It takes about a minute to parse the 250kb file in the attachment for warnings. Even a simple regex like just "INFO" takes 40 seks for the attached file.
A 6 MB log file took about 18 minutes with a slightly more dificult skript.
When I tested a log on java with about the same size and similar amount of categorys, it terminated after 2 seconds.
Skript:
import hudson.plugins.warnings.parser.Warning
return new Warning("fileName", 1, "Dynamic Parser", "category" , "normal")
Regex:
^([A-Z])\s)[(.)].at:\s(\w\.java)((\d+))(\s)$
Project:
Jenkins
Labels:
plugins
warnings
Priority:
Major
Reporter:
Tobias Schmetzer
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14382) Error in substituting macro when sending email
Krzysztof Malinowski
created JENKINS-14382
Error in substituting macro when sending email
Issue Type:
Bug
Affects Versions:
current
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
11/Jul/12 10:30 AM
Description:
On a failed build, the following message is shown in the build log when the build comes to sending email:
Error substituting with token-macro plugin: org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'ConnectionHandler' in '[here comes html mail filled template]'
The email itself is sent to the recipients. The issue also does not occur on successful builds.
It also seems that the issue is not always present for the failed builds. Sometimes mail goes without any errors. It also seems that this 'unrecognized macro' also varies; I just found another occurrence complaining about unrecognized 'AbstractBuildExecution'
I am using globally configured email-ext with content: ${JELLY_SCRIPT, template="html"}
Environment:
Jenkins 1.472 on RHEL 5 x86_64, email-ext 2.22
Project:
Jenkins
Priority:
Minor
Reporter:
Krzysztof Malinowski
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13754) Error when compiling a plugin against jenkins version 1.463
Holger Mense reopened JENKINS-13754 Error when compiling a plugin against jenkins version 1.463 I am reopening this issue, because I think it has been accidentally closed by Steven Aerts. His patch does not have any connection to this issue and SCM comment also mentions another issue (13743), which is still opened. Furthermore, I am also seeing the original problem with Jenkins 1.473, when trying to build the PTC Integrity Plugin. Change By: Holger Mense (11/Jul/12 9:57 AM) Resolution: Fixed Status: Resolved Reopened Assignee: Steven Aerts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14027) Can't run build flow configuration with parralell jobs
Vladimir Turin commented on JENKINS-14027 Can't run build flow configuration with parralell jobs I have arrows from a circle to executed jobs (Jenkins 1.472, build-flow 0.4), so it is looks like a bug of your configuration or limitation of current plugin (see #13520 part 2). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14163) CVS Polling Log error
Oliver Whiteman edited a comment on JENKINS-14163 CVS Polling Log error This is where the threads are stuck: SCM polling for hudson.model.FreeStyleProject@38ddab20[Mods] "SCM polling for hudson.model.FreeStyleProject@38ddab20[Mods]" Id=83 Group=main RUNNABLE at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366) at java.util.regex.Pattern$Curly.match(Pattern.java:3737) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227) at java.util.regex.Pattern$Curly.match1(Pattern.java:3797) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Curly.match0(Pattern.java:3782) at java.util.regex.Pattern$Curly.match(Pattern.java:3744) at java.util.regex.Pattern$Start.match(Pattern.java:3055) at java.util.regex.Matcher.search(Matcher.java:1105) at java.util.regex.Matcher.find(Matcher.java:535) at hudson.scm.CvsChangeLogHelper.mapCvsLog(CvsChangeLogHelper.java:169) at hudson.scm.CVSSCM.calculateRepositoryState(CVSSCM.java:465) at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:320) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1377) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Number of locked synchronizers = 1 java.util.concurrent.locks.ReentrantLock$NonfairSync@16cb436a SCM polling for hudson.model.FreeStyleProject@409a6317[Mods] "SCM polling for hudson.model.FreeStyleProject@409a6317[Mods]" Id=82 Group=main RUNNABLE at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345) at java.util.regex.Pattern$Curly.match1(Pattern.java:3803) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Curly.match0(Pattern.java:3782) at java.util.regex.Pattern$Curly.match(Pattern.java:3744) at java.util.regex.Pattern$Start.match(Pattern.java:3055) at java.util.regex.Matcher.search(Matcher.java:1105) at java.util.regex.Matcher.find(Matcher.java:535) at hudson.scm.CvsChangeLogHelper.mapCvsLog(CvsChangeLogHelper.java:169) at hudson.scm.CVSSCM.calculateRepositoryState(CVSSCM.java:465) at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:320) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1377) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Number of locked synchronizers = 1 java.util.concurrent.locks.ReentrantLock$NonfairSync@7ab6efd6 Running for 14 hours now! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14163) CVS Polling Log error
Oliver Whiteman commented on JENKINS-14163 CVS Polling Log error This is where the threads are stuck: SCM polling for hudson.model.FreeStyleProject@38ddab20[B_FOG_ORBISGAMESPACKAGE25_0Mods] "SCM polling for hudson.model.FreeStyleProject@38ddab20[B_FOG_ORBISGAMESPACKAGE25_0Mods]" Id=83 Group=main RUNNABLE at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366) at java.util.regex.Pattern$Curly.match(Pattern.java:3737) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227) at java.util.regex.Pattern$Curly.match1(Pattern.java:3797) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Curly.match0(Pattern.java:3782) at java.util.regex.Pattern$Curly.match(Pattern.java:3744) at java.util.regex.Pattern$Start.match(Pattern.java:3055) at java.util.regex.Matcher.search(Matcher.java:1105) at java.util.regex.Matcher.find(Matcher.java:535) at hudson.scm.CvsChangeLogHelper.mapCvsLog(CvsChangeLogHelper.java:169) at hudson.scm.CVSSCM.calculateRepositoryState(CVSSCM.java:465) at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:320) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1377) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Number of locked synchronizers = 1 java.util.concurrent.locks.ReentrantLock$NonfairSync@16cb436a SCM polling for hudson.model.FreeStyleProject@409a6317[B_FOG_ORBISGAMESPACKAGE24_0Mods] "SCM polling for hudson.model.FreeStyleProject@409a6317[B_FOG_ORBISGAMESPACKAGE24_0Mods]" Id=82 Group=main RUNNABLE at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345) at java.util.regex.Pattern$Curly.match1(Pattern.java:3803) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Curly.match0(Pattern.java:3782) at java.util.regex.Pattern$Curly.match(Pattern.java:3744) at java.util.regex.Pattern$Start.match(Pattern.java:3055) at java.util.regex.Matcher.search(Matcher.java:1105) at java.util.regex.Matcher.find(Matcher.java:535) at hudson.scm.CvsChangeLogHelper.mapCvsLog(CvsChangeLogHelper.java:169) at hudson.scm.CVSSCM.calculateRepositoryState(CVSSCM.java:465) at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:320) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1377) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Number of locked synchronizers = 1 java.util.concurrent.locks.ReentrantLock$NonfairSync@7ab6efd6 Running for 14 hours now! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Karsten Brandt commented on JENKINS-14135 NPE @ssogabe: This issue can be closed, if https://github.com/jenkinsci/sloccount-plugin/pull/8 merged into the repository. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
