[JIRA] [git-client] (JENKINS-22039) Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials
Marcus Bristol commented on JENKINS-22039 Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials The "Force polling using workspace" setting seems to have done the trick. Thanks. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials
Marcus Bristol commented on JENKINS-22039 Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials OK, I've added the setting - we'll see how it goes. Unfortunately I had to switch back from JGit as its still broken (doesn't seem to update the repository nor push changes correctly). Thanks for your 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials
Marcus Bristol edited a comment on JENKINS-22039 Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials There was an existing empty git repo in the temp folder. I removed it and created a .git file as suggested, manually kicked off the build, and it all worked fine. However, when initiating a build via remote polling I get this: Started on 20/03/2014 3:59:54 PM Using strategy: Default [poll] Last Built Revision: Revision be2c3d7df7fa6eb0de12b3b7b50c1180ad63cb2f (origin/master) using .gitcredentials to set credentials Could not remove the credential section from the git configuration FATAL: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: Invalid gitfile format: C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git hudson.util.IOException2: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: Invalid gitfile format: C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:458) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1584) at hudson.model.AbstractProject.poll(AbstractProject.java:1493) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: Invalid gitfile format: C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1183) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1160) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1156) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1152) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1045) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:998) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:989) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1535) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:491) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:456) ... 13 more Done. Took 2.6 sec No changes 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials
Marcus Bristol commented on JENKINS-22039 Credentialed git init fails with "file exists" - reuses same tmp dir for all credentials There is an existing empty git repo in the temp folder. I created a .git file as suggested, manually kicked off the build, and it all worked fine. However, when initiating a build via remote polling I get this: Started on 20/03/2014 3:59:54 PM Using strategy: Default [poll] Last Built Revision: Revision be2c3d7df7fa6eb0de12b3b7b50c1180ad63cb2f (origin/master) using .gitcredentials to set credentials Could not remove the credential section from the git configuration FATAL: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: Invalid gitfile format: C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git hudson.util.IOException2: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: Invalid gitfile format: C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:458) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1584) at hudson.model.AbstractProject.poll(AbstractProject.java:1493) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: Invalid gitfile format: C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1183) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1160) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1156) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1152) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1045) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:998) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:989) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1535) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:491) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:456) ... 13 more Done. Took 2.6 sec No changes 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol commented on JENKINS-22039 git init is failing with a "file exists" error Note that it does use the workspace for the actual build - this just seems to be for some kind of initialisation. My guess is that it was something to do with how it manages credentials. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol commented on JENKINS-22039 git init is failing with a "file exists" error The only variables that have a reference to that folder are: java.io.tmpdir C:\DOCUME~1!SYSCA~1\LOCALS~1\Temp\ TEMPC:\DOCUME~1!SYSCA~1\LOCALS~1\Temp TMP C:\DOCUME~1!SYSCA~1\LOCALS~1\Temp 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol commented on JENKINS-22039 git init is failing with a "file exists" error Changing to JGit has had positive results so far, but as this is an intermittent problem I'll test over the next few days. Thanks. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol updated JENKINS-22039 git init is failing with a "file exists" error Job definition Change By: Marcus Bristol (05/Mar/14 3:05 AM) Attachment: jenkins.xml 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol commented on JENKINS-22039 git init is failing with a "file exists" error There seemed to only be the one Jenkins job active. Agreed that the destination path seemed suspicious, but we haven't defined any specific directories, and I couldn't find any setting to change it. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol edited a comment on JENKINS-22039 git init is failing with a "file exists" error I have attached the job definition 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-22039) git init is failing with a "file exists" error
Marcus Bristol created JENKINS-22039 git init is failing with a "file exists" error Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 05/Mar/14 2:03 AM Description: After a remote trigger the git init command failed with the following exception: Started on 5/03/2014 1:42:45 PM Using strategy: Default [poll] Last Built Revision: Revision 6c615c2d4570d1aa9288afd73588a7328073e832 (origin/master) using .gitcredentials to set credentials Could not remove the credential section from the git configuration FATAL: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: cannot copy 'C:\Program Files\Git/share/git-core/templates/description' to 'C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git/description': File exists [8mha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mhudson.util.IOException2: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: cannot copy 'C:\Program Files\Git/share/git-core/templates/description' to 'C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git/description': File exists at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:459) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1581) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: cannot copy 'C:\Program Files\Git/share/git-core/templates/description' to 'C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git/description': File exists at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1173) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1150) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1146) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1142) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1035) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:988) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:979) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1526) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:489) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457) ... 13 more Done. Took 0.5 sec No changes The second time it failed with a similar exception: Started on 5/03/2014 1:46:38 PM Using strategy: Default [poll] Last Built Revision: Revision 6c615c2d4570d1aa9288afd73588a7328073e832 (origin/master) using .gitcredentials to set credentials Could not remove the credential section from the git configuration FATAL: hudson.plugins.git.GitException: Command "git init" returned status code 128: stdout: stderr: fatal: cannot copy 'C:\Program Files\Git/share/git-core/templates/hooks/post-update.sample' to 'C:/DOCUME~1/!SYSCA~1/LOCALS~1/Temp/.git/hooks/post-update.sample': File exists [8mha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAck
[JIRA] (JENKINS-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Marcus Bristol commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 I have a similar issue, but my error is: java.lang.LinkageError: loader (instance of java/net/URLClassLoader): attempted duplicate class definition for name: "hudson/plugins/warnings/parser/Messages" at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at hudson.plugins.warnings.parser.ParserRegistry.getAllParsers(ParserRegistry.java:199) at hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:171) at hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:141) at hudson.plugins.warnings.parser.ParserRegistry.exists(ParserRegistry.java:188) at hudson.plugins.warnings.ParserConfiguration.filterExisting(ParserConfiguration.java:80) at hudson.plugins.warnings.WarningsPublisher.getParserConfigurations(WarningsPublisher.java:174) at hudson.plugins.warnings.WarningsPublisher.getParsers(WarningsPublisher.java:262) at hudson.plugins.warnings.WarningsPublisher.getProjectActions(WarningsPublisher.java:251) at hudson.model.Project.createTransientActions(Project.java:213) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:665) at hudson.model.AbstractProject.onLoad(AbstractProject.java:299) at hudson.model.Project.onLoad(Project.java:88) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2507) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Worked fine for me in 1.485 though, so I presume its a different issue. 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-12955) Stylecop file report is blank
Marcus Bristol commented on JENKINS-12955 Stylecop file report is blank Unfortunately that was a one-off hack for a random build to try to determine what the issue was. I'll see if I can find the root cause over the weekend, and hopefully determine a workaround that I can post. 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-13471) Tests listed in incorrect namespace
Marcus Bristol created JENKINS-13471:
Summary: Tests listed in incorrect namespace
Key: JENKINS-13471
URL: https://issues.jenkins-ci.org/browse/JENKINS-13471
Project: Jenkins
Issue Type: Bug
Components: nunit
Affects Versions: current
Reporter: Marcus Bristol
Assignee: redsolo
Attachments: nunit-results.xml
Unit test results are occasionally put under different namespaces, depending on
the type of the tests.
The issue is in the transform file {{nunit-to-junit.xsl}}.
Specifically, the cause is due to the {{firstTestName}} variable. The original
is:
{code:xml}
{code}
The "fixed" version is:
{code:xml}
{code}
This fixes my current issue, but I don't know if it introduces any new (or old)
issues.
I have attached an example nunit results file that will generate the error (one
of the 3 {{Inflector.OrdinalizeTests}} testsuites has the name {{Inflector}}
rather than {{Inflector.OrdinalizeTests}})
--
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-12955) Stylecop file report is blank
[ https://issues.jenkins-ci.org/browse/JENKINS-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Bristol updated JENKINS-12955: - Description: Clicking file link in a stylecop violations report page takes you to an empty file report page. I am using Jenkins ver. 1.452 and violations plugin 0.7.10 in 2 environments, windows 2003 server and windows 2008 server. It seems that the violating file xml is missing line elements. I added some dummy line elements to the xml and the page then rendered fine. was: Clicking file link in a stylecop violations report page takes you to an empty file report page. I am using Jenkins ver. 1.452 and violations plugin 0.7.10 in 2 environments, windows 2003 server and windows 2008 server. It seems that the violating file xml is missing line elements. I added some dummy lines and the page then rendered fine. > Stylecop file report is blank > - > > Key: JENKINS-12955 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12955 > Project: Jenkins > Issue Type: Bug > Components: violations >Affects Versions: current >Reporter: Marcus Bristol >Assignee: peterkittreilly >Priority: Minor > Labels: plugin > > Clicking file link in a stylecop violations report page takes you to an empty > file report page. > I am using Jenkins ver. 1.452 and violations plugin 0.7.10 in 2 environments, > windows 2003 server and windows 2008 server. > It seems that the violating file xml is missing line elements. I added some > dummy line elements to the xml and the page then rendered fine. -- 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-12955) Stylecop file report is blank
Marcus Bristol created JENKINS-12955: Summary: Stylecop file report is blank Key: JENKINS-12955 URL: https://issues.jenkins-ci.org/browse/JENKINS-12955 Project: Jenkins Issue Type: Bug Components: violations Affects Versions: current Reporter: Marcus Bristol Assignee: peterkittreilly Priority: Minor Clicking file link in a stylecop violations report page takes you to an empty file report page. I am using Jenkins ver. 1.452 and violations plugin 0.7.10 in 2 environments, windows 2003 server and windows 2008 server. It seems that the violating file xml is missing line elements. I added some dummy lines and the page then rendered fine. -- 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
