[JIRA] (JENKINS-13235) sloccount report formating on build summary
[ https://issues.jenkins-ci.org/browse/JENKINS-13235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162959#comment-162959 ] SCM/JIRA link daemon commented on JENKINS-13235: Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/sloccount/model/Countable.java src/main/java/hudson/plugins/sloccount/model/File.java src/main/java/hudson/plugins/sloccount/model/FileContainer.java src/main/java/hudson/plugins/sloccount/model/Folder.java src/main/java/hudson/plugins/sloccount/model/Language.java src/main/java/hudson/plugins/sloccount/model/SloccountReport.java src/main/java/hudson/plugins/sloccount/util/StringUtil.java src/main/resources/hudson/plugins/sloccount/SloccountResult/files.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/folders.jelly src/main/resources/hudson/plugins/sloccount/SloccountResult/languages.jelly http://jenkins-ci.org/commit/sloccount-plugin/7ef65b2d7888071638791195a964119d4340117e Log: [JENKINS-13235] use commas in numbers for readability sloccount report formating on build summary --- Key: JENKINS-13235 URL: https://issues.jenkins-ci.org/browse/JENKINS-13235 Project: Jenkins Issue Type: Improvement Components: sloccount Affects Versions: current Reporter: Greg Moncreaff Assignee: npiguet Priority: Minor 2 enhancements: a) use commas in numbers for readability (e.g. have 9,876,543,210 instead of 9876543210) b) attempt some alignment of data? (maybe put data into a sortable html table along the lines of, (but smaller screen real estate) the drill in report (language tab) with additional columns for build delta lang/file/sloc? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13235) sloccount report formating on build summary
[ https://issues.jenkins-ci.org/browse/JENKINS-13235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162960#comment-162960 ] dogfood commented on JENKINS-13235: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_sloccount #25|http://ci.jenkins-ci.org/job/plugins_sloccount/25/] [JENKINS-13235] use commas in numbers for readability (Revision 7ef65b2d7888071638791195a964119d4340117e) Result = SUCCESS Seiji Sogabe : Files : * src/main/resources/hudson/plugins/sloccount/SloccountResult/languages.jelly * src/main/java/hudson/plugins/sloccount/model/FileContainer.java * src/main/java/hudson/plugins/sloccount/model/Language.java * src/main/resources/hudson/plugins/sloccount/SloccountResult/files.jelly * src/main/resources/hudson/plugins/sloccount/SloccountResult/folders.jelly * src/main/java/hudson/plugins/sloccount/util/StringUtil.java * src/main/java/hudson/plugins/sloccount/model/SloccountReport.java * src/main/java/hudson/plugins/sloccount/model/File.java * src/main/java/hudson/plugins/sloccount/model/Folder.java * src/main/java/hudson/plugins/sloccount/model/Countable.java sloccount report formating on build summary --- Key: JENKINS-13235 URL: https://issues.jenkins-ci.org/browse/JENKINS-13235 Project: Jenkins Issue Type: Improvement Components: sloccount Affects Versions: current Reporter: Greg Moncreaff Assignee: npiguet Priority: Minor 2 enhancements: a) use commas in numbers for readability (e.g. have 9,876,543,210 instead of 9876543210) b) attempt some alignment of data? (maybe put data into a sortable html table along the lines of, (but smaller screen real estate) the drill in report (language tab) with additional columns for build delta lang/file/sloc? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11941) Configuration Slicing Plugin's Execute shell slicer lists first execute shell step only
[ https://issues.jenkins-ci.org/browse/JENKINS-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jacob_robertson resolved JENKINS-11941. --- Assignee: jacob_robertson (was: mdonohue) Resolution: Fixed Look for this feature in the most recent version 1.29. It is explained on the wiki @ https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin under the String slicing multiple Builders section. Configuration Slicing Plugin's Execute shell slicer lists first execute shell step only - Key: JENKINS-11941 URL: https://issues.jenkins-ci.org/browse/JENKINS-11941 Project: Jenkins Issue Type: Improvement Components: configurationslicing Environment: Debian squeeze, Configuration Slicing Plugin, Version 1.26, Jenkins version 1.440 Reporter: Michael Prokop Assignee: jacob_robertson The Execute shell slicer option of the Configuration Slicing Plugin seems to list only the first shell build step. Would be great if all the shell build steps could be listed. For example I'm cleaning up in a first shell build step, then copy artifacts from another project and finally have another shell build step which executes the real[tm] stuff: http://michael-prokop.at/screeni/gkrellShoot_11-11-30_225905.png Now in the Execute shell slicer option of the Configuration Slicing Plugin I see and can edit only the first shell build step (which does the clean up in the example above), whereas the more important stuff happens in the build step that's not available in Execute shell slicer. If there's any chance that could be improved you'd make my day. :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11774) Mass-configure triggers in Email-Ext-plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162963#comment-162963 ] jacob_robertson commented on JENKINS-11774: --- I've added a new ticket to address William's issues https://issues.jenkins-ci.org/browse/JENKINS-13834 Mass-configure triggers in Email-Ext-plugin --- Key: JENKINS-11774 URL: https://issues.jenkins-ci.org/browse/JENKINS-11774 Project: Jenkins Issue Type: New Feature Components: configurationslicing Affects Versions: current Environment: Jenkins 1.409.3 Config slicing plugin 1.25 Email-ext plugin 2.14.1 Reporter: tfnico Assignee: mdonohue Labels: email, email-ext A thing I repeatedly have to do for each job is to configure Triggers under the Advanced section of the Editable Email Notification. By default, the Email notification will trigger on 'Failure'. However, we also like to receive notification on 'Unstable' and 'Fixed'. Would it be possible to include this somehow in the slicer? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13834) E-mail Notification Slicer issues
jacob_robertson created JENKINS-13834: - Summary: E-mail Notification Slicer issues Key: JENKINS-13834 URL: https://issues.jenkins-ci.org/browse/JENKINS-13834 Project: Jenkins Issue Type: Bug Components: configurationslicing Reporter: jacob_robertson Assignee: mdonohue +1, We noticed to issues while using the two plugins, for us: Jenkins: 1.446 Config slicing plugin: 1.28.1 Email-ext plugin: 2.16 First issue was that the Slicer only was modifying the default setting (which we do not use, we use the Failure case almost always.) Secondly the default subject and default content was not filled out by default. We started to get a ton of e-mails with no subject nor body. After consulting with the team we realized we'd recently made these changes using the slicer and they were not being filled out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12655) GIT_BRANCH is incorrect in build steps when branch choosing strategy is set to inverse (but it is correct in build name macro)
[
https://issues.jenkins-ci.org/browse/JENKINS-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162964#comment-162964
]
Ruth Morgenstein commented on JENKINS-12655:
Still broken in 1.18.
GIT_BRANCH is incorrect in build steps when branch choosing strategy is set
to inverse (but it is correct in build name macro)
--
Key: JENKINS-12655
URL: https://issues.jenkins-ci.org/browse/JENKINS-12655
Project: Jenkins
Issue Type: Bug
Components: git
Reporter: Ruth Morgenstein
Assignee: abayer
Context: I'm trying to create a parameterized job chain for our branches.
Version info:
Jenkins 1.450
Git 1.1.15
build-name-setter 1.3
parametrized trigger 2.12
1) Set the git branch to */master and in advanced, select branching strategy
= inverse
2) Set the build name (using plugin) to #${BUILD_NUMBER}.${GIT_BRANCH}
3) In the build, use shell to execute: echo ${BUILD_BRANCH}
4) Push a change into a branch in git then manually start the build in Jenkins
Result:
The build string is set correctly to the branch used in step#4, but the echo
in step #3 incorrectly says origin/master. Note, that the wrong GIT_BRANCH is
also sent in my parameterized trigger.
The setting for GIT_BRANCH is correct at all times when Default choosing
strategy is selected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13835) upgrading Subversion Plugin to 1.40 totally ruined our CI server
pancake created JENKINS-13835:
-
Summary: upgrading Subversion Plugin to 1.40 totally ruined our CI
server
Key: JENKINS-13835
URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
Project: Jenkins
Issue Type: Bug
Components: subversion
Environment: Jenkins ver. 1.460; Subversion Plugin 1.40, 1.39; Windows
Server 2003 R2 x64 SP2
Reporter: pancake
Priority: Blocker
Updating Subversion Plugin to 1.40 caused multiple bugs. Rolling back to 1.39
resulted to {color:red}complete inability to perform a checkout. CI server is
totally unusable now.{color}
*Issue #1*
After updating to Subversion Plugin to 1.40 (from 1.39) this exception started
occurring _sometimes_ (various salves, various jobs):
{quote}
Checking out a fresh workspace because there's no workspace at
C:\_JenkinsCI\workspace\XXX
Cleaning local Directory .
Checking out http://oursvnserver/svn/svnLatest/.../XXX
A ...
ERROR: Failed to check out http://oursvnserver/svn/svnLatest/.../XXX
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT
/svn/svnLatest/!svn/vcc/default failed
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
at
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:216)
at
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:100)
at
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756)
at
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14)
at
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9)
at
org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:781)
at
hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:85)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:152)
at
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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)
Caused by: svn: E175002: REPORT /svn/svnLatest/!svn/vcc/default failed
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 35 more
FATAL: null
java.lang.NullPointerException
{quote}
*Issue #2*
{{Emulate clean checkout by first deleting unversioned/ignored files, then 'svn
update'}} no longer deletes unversioned files in 1.40.
*Issue #3*
Because of #2 and #3 I've decided to roll back to 1.39. So, I've
[JIRA] (JENKINS-4867) Two simultaneous sloccount executions fails
[ https://issues.jenkins-ci.org/browse/JENKINS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe resolved JENKINS-4867. - Assignee: sogabe (was: npiguet) Resolution: Not A Defect Updated wiki. Two simultaneous sloccount executions fails --- Key: JENKINS-4867 URL: https://issues.jenkins-ci.org/browse/JENKINS-4867 Project: Jenkins Issue Type: Bug Components: sloccount Affects Versions: current Environment: Platform: All, OS: All Reporter: worsaae Assignee: sogabe If you uses sloccount for multiple jobs sometimes two jobs end at the same time and sloccount is executed simultaneously This will fail since sloccount (per default) uses one temp data folder in $HOME/.slocdata Either change sloccount to not use a temp data dir or change the setup explanation so novice users (like me) are explained to use the --datadir option in order to get a datadir per hudson job. This seems to work: [ -d slocdata ] || mkdir slocdata sloccount --datadir slocdata --details your source path sloccount.sc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12166) add a sloccount portlet to dashboard
[ https://issues.jenkins-ci.org/browse/JENKINS-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe resolved JENKINS-12166. -- Resolution: Duplicate add a sloccount portlet to dashboard Key: JENKINS-12166 URL: https://issues.jenkins-ci.org/browse/JENKINS-12166 Project: Jenkins Issue Type: New Feature Components: dashboard-view, sloccount Reporter: Greg Moncreaff Assignee: Peter Hayes to summarize all counts by language and chart the trends -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13525) SLOCCount Plugin doesn't work in multi-configuration projects
[ https://issues.jenkins-ci.org/browse/JENKINS-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe resolved JENKINS-13525. -- Resolution: Duplicate SLOCCount Plugin doesn't work in multi-configuration projects - Key: JENKINS-13525 URL: https://issues.jenkins-ci.org/browse/JENKINS-13525 Project: Jenkins Issue Type: Bug Components: sloccount Affects Versions: current Environment: Jenkins ver 1.459. Ubuntu 10.04 server Reporter: lesterp Assignee: npiguet Labels: plugins No SLOCCount configuration options are presented in a multi-configuration project (the 'Publish SLOCCount analysis results' checkbox). This checkbox is available in the freestyle and Maven projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13836) Stable release issues|Loading All Build History Fails in stable release 1.447.1
Arvind Ramalingam created JENKINS-13836: --- Summary: Stable release issues|Loading All Build History Fails in stable release 1.447.1 Key: JENKINS-13836 URL: https://issues.jenkins-ci.org/browse/JENKINS-13836 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Prodution Reporter: Arvind Ramalingam Priority: Blocker Hi I have upgraded my Production Jenkins to 1.447.1 and I am not able to see my build history.When I try to view more of my build history I get the below error.Please let me know which stable release should i revert back to and I was at 1.409 and everything was fine. HTTP Status 404 - type Status report message description The requested resource () is not available. Apache Tomcat/6.0.26 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13775) String index out of range
[
https://issues.jenkins-ci.org/browse/JENKINS-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-13775.
Resolution: Fixed
String index out of range
-
Key: JENKINS-13775
URL: https://issues.jenkins-ci.org/browse/JENKINS-13775
Project: Jenkins
Issue Type: Bug
Components: sloccount
Affects Versions: current
Environment: Linux:redhat9
jenkins:1.463
Reporter: wang y
Assignee: npiguet
Labels: plugin
console output:
{quote}
ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to
exception
java.lang.StringIndexOutOfBoundsException: String index out of range: -5
at java.lang.String.substring(String.java:1937)
at java.lang.String.substring(String.java:1904)
at hudson.plugins.sloccount.model.Folder.simplifyName(Folder.java:22)
at
hudson.plugins.sloccount.model.SloccountReport.simplifyNames(SloccountReport.java:175)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:42)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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)
{quote}
sloccount file:
{quote}
Have a non-directory at the top, so creating directory top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-check-Make to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck_reports.xml to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-suppress to top_dir
Creating filelist for driver
Adding /g2m_builder_test/railway-svn-code/support/sloccount.sc to top_dir
Creating filelist for test
Categorizing files.
Computing results.
43ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDisp.c
197 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspEnc.c
268 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspCap.c
179 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDec.c
87ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.c
636 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/dm648api.c
387 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspApi.c
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/dm648api.h
27ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspCommon.h
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspApi.h
5 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.h
6 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/SdkVersion.h
240 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/ShareStruct.h
37makefiletest
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Makefile
174 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconDecodeArea.cpp
236 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconPreviewArea.cpp
223 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/mainWindow.cpp
12cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/main.cpp
39cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/public/sunday.cpp
220 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/public/yuv.cpp
143 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/thread/Timer.cpp
41cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/thread/Thread.cpp
295 cpp test
[JIRA] (JENKINS-13775) String index out of range
[
https://issues.jenkins-ci.org/browse/JENKINS-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162968#comment-162968
]
dogfood commented on JENKINS-13775:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_sloccount #28|http://ci.jenkins-ci.org/job/plugins_sloccount/28/]
[FIXED JENKINS-13775] String index out of range. (Revision
5bd7f990d3fe5bc6567210286ff544455a258057)
Result = SUCCESS
Seiji Sogabe :
Files :
* src/main/java/hudson/plugins/sloccount/model/SloccountReport.java
String index out of range
-
Key: JENKINS-13775
URL: https://issues.jenkins-ci.org/browse/JENKINS-13775
Project: Jenkins
Issue Type: Bug
Components: sloccount
Affects Versions: current
Environment: Linux:redhat9
jenkins:1.463
Reporter: wang y
Assignee: npiguet
Labels: plugin
console output:
{quote}
ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to
exception
java.lang.StringIndexOutOfBoundsException: String index out of range: -5
at java.lang.String.substring(String.java:1937)
at java.lang.String.substring(String.java:1904)
at hudson.plugins.sloccount.model.Folder.simplifyName(Folder.java:22)
at
hudson.plugins.sloccount.model.SloccountReport.simplifyNames(SloccountReport.java:175)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:42)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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)
{quote}
sloccount file:
{quote}
Have a non-directory at the top, so creating directory top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-check-Make to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck_reports.xml to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-suppress to top_dir
Creating filelist for driver
Adding /g2m_builder_test/railway-svn-code/support/sloccount.sc to top_dir
Creating filelist for test
Categorizing files.
Computing results.
43ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDisp.c
197 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspEnc.c
268 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspCap.c
179 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDec.c
87ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.c
636 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/dm648api.c
387 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspApi.c
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/dm648api.h
27ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspCommon.h
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspApi.h
5 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.h
6 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/SdkVersion.h
240 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/ShareStruct.h
37makefiletest
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Makefile
174 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconDecodeArea.cpp
236 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconPreviewArea.cpp
223 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/mainWindow.cpp
12cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/main.cpp
39cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/public/sunday.cpp
