[JIRA] [repository-connector] (JENKINS-24896) Repoistory Connector plugin fails to resolve LATEST version
redsolo created JENKINS-24896 Repoistory Connector plugin fails to resolve LATEST version Issue Type: Bug Assignee: Unassigned Components: repository-connector Created: 28/Sep/14 6:26 AM Description: I upgraded to version 1.0.1 from 0.8.2, and now it will not resolve LATEST version anymore. Instead of downloading the latest version it throws an exception Here is the plugin section of the config.xml: "repository-connector@1.0.1"> target com.flexlink.fucd fucd-console LATEST jar console.jar true false always always warn warn Here is the exception: INFO: define repo: [Repository id=central, type=default, url="" class="code-comment">//repo1.maven.org/maven2, isRepositoryManager=false] failed collecting dependency info for [Artifact com.flexlink.fucd:fucd-console:jar::LATEST] org.sonatype.aether.collection.DependencyCollectionException: Failed to collect dependencies for com.flexlink.fucd:fucd-console:jar:LATEST (provided) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:197) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:308) at org.jvnet.hudson.plugins.repositoryconnector.aether.Aether.resolve(Aether.java:154) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.download(ArtifactResolver.java:129) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for com.flexlink.fucd:fucd-console:jar:LATEST at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:243) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:191) ... 13 more Caused by: org.sonatype.aether.resolution.VersionResolutionException: Failed to resolve version for com.flexlink.fucd:fucd-console:jar:LATEST: Could not find metadata com.flexlink.fucd:fucd-console/maven-metadata.xml in local (C:\Windows\TEMP\repositoryconnector-repo) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion(DefaultVersionResolver.java:273) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:236) ... 15 more Caused by: org.sonatype.aether.transfer.MetadataNotFoundException: Could not find metadata com.flexlink.fucd:fucd-console/maven-metadata.xml in local (C:\Windows\TEMP\repositoryconnector-repo) at org.sonatype.aether.impl.internal.DefaultMetadataResolver.resolve(DefaultMetadataResolver.java:215) at org.sonatype.aether.impl.internal.DefaultMetadataResolver.resolveMetadata(DefaultMetadataResolver.java:173) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion(DefaultVersionResolver.java:211) ... 16 more Build step 'Artifact Resolver' marked build as failure I will have to downgrade to 0.8.2. I hope you can figure out what the problem is. Project: Jenkins
[JIRA] [disk-usage] (JENKINS-20308) Disk usage text not formatted properly in build page
redsolo commented on JENKINS-20308 Disk usage text not formatted properly in build page Thanks a lot! Will install asap monday morning 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] [disk-usage] (JENKINS-20308) Disk usage graph no longer showing in build page
redsolo commented on JENKINS-20308 Disk usage graph no longer showing in build page Yes, I mean the job page. Now it only shows the strange text with no size formatting at all. But if I enable the graphs in global diskusage configuration, I do see the graphs but the text is still not formatted properly. 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] [disk-usage] (JENKINS-20308) Disk usage text not formatted properly in build page
redsolo updated JENKINS-20308 Disk usage text not formatted properly in build page Change By: redsolo (11/Nov/13 8:44 AM) Summary: Disk usage graph no longer showing text not formatted properly in build page 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] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
redsolo edited a comment on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Im seeing this problem also after I have upgraded to the latest version of Jenkins, not sure if it was the upgrade of the Jenkins Windows Service or if it was the Jenkins.war that provoked this. Downgraded to 1.510 and it did not help OS : Windows Server 2008 R2 Standard Service Pack 1 JDK : Java version 1.6.0_43 Jenkins : 1.518 The service does not respond, it only spams the error log with an exception for each folder. 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] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
redsolo commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Im seeing this problem also after I have upgraded to the latest version of Jenkins, not sure if it was the upgrade of the Jenkins Windows Service or if it was the Jenkins.war that provoked this. OS : Windows Server 2008 R2 Standard Service Pack 1 JDK : Java version 1.6.0_43 Jenkins : 1.518 The service does not respond, it only spams the error log with an exception for each folder. 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] (JENKINS-15384) TFS Plugin does not seem to work (can't get latest)
redsolo commented on JENKINS-15384 TFS Plugin does not seem to work (can't get latest) Im not sure why this is happening and unfortunately i dont have a real TFS to work with. Instead I only can use the codeplex TFS instance which may work like all the other TSF versions out there. Its hard for me to fix this unless I get a good way of reproducing the issue, so if you can get any more details on when this issue happens that would be great. How reproducable is it for you? Every build, every day? Ive configure two jobs on my local jenkins instance to see if I get the "All files are up to date." issue when retrieving files from the TFS. Job pusher - triggers every 3 mins checks out a TFS project creates a local file containing the file stamp adds this to the TF workspace (tf add) commits the file (tf checkin) Job receiver - polls SCM every 10 min checks out the same TFS project fails the build if it finds the "All files are up to date." text in the console (using the text-finder plugin) Would the "Job receiver" resemble the problems you are seeing? ie, the "tf get" command would sometimes yield the "all files are up to date"? ive had this running for an hour now without any problems, but then again this very simple setup may not be applicable to the issue you are seeing. 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-15305) Job-level configuration is missing
redsolo resolved JENKINS-15305 as Won't Fix Job-level configuration is missing Resolving this as it is behaving as post-build steps should do. In an earlier version of Jenkins the post-build steps would be listed as the build-coinplugin is, but that has changed now to how it looks today. I dont want the plugin to behave differently from other post-build plugins. Change By: redsolo (12/Oct/12 7:13 AM) Status: Open Resolved Resolution: Won't 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-15470) Support for instant-messaging plugin (xmpp)
redsolo commented on JENKINS-15470 Support for instant-messaging plugin (xmpp) Is this really related to the ci-game plugin? The plugin should only give points to the users that have commited something to a build, ie they are referred in a SCM change set. 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-4021) TFS - unparseable date problem
redsolo commented on JENKINS-4021 TFS - unparseable date problem I dont think ignoring the date is a solution, but perhaps as David mentioned there could be an option where a custom locale can be configured at system- or project-level. This locale caould then be used for parsing the dates, overriding the guessing that the plugin has to do due to the output of the tf tool. Unless noone knows of a way to override the system regional setting a command prompt? 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-12908) TFS errors during get operation do not fail the build
redsolo commented on JENKINS-12908 TFS errors during get operation do not fail the build The code behind the execution of the TFS command line will check if the tf tool returns with 1 or 0, and those are marked as success. My guess is that the tf command line tool returned either 1 or 0 regardless of the errors. That makes it somewhat difficult for the jenkins plugin to know if there was a problem or not. If the authentication fails, then tf returns with the code 100 and thus the plugin fails the build. I reccon I could do some parsing of the console output that the TFS tool generates and fail the build if it finds anything resembling such a problem. But that would not be possible for the history command, because if someone checks in a comment resembling the text the plugin will look for then the plugin would fail the build for no good reason. Does this happen a lot for you? 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-4021) TFS - unparseable date problem
redsolo commented on JENKINS-4021 TFS - unparseable date problem I have looked into this issue before and I think that it is impossible to evaluate the date from java. Something to do with the locale that the slave /master is running. Mikael could you try to get the locale that is active in the jvm that is running? And if its possible, an example output that the plugin cannot parse? I think the problem is with the tfs tool that generates a locale based date... 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-15145) Unable to connect to the remote TFS server
redsolo commented on JENKINS-15145 Unable to connect to the remote TFS server Good to hear that you got it working! 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-15145) Unable to connect to the remote TFS server
redsolo commented on JENKINS-15145 Unable to connect to the remote TFS server Duane, Mikael has confirmed that his problem was related to user access issues when the service was run as the System local user. Could it be the same problem for you? 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-12908) TFS errors during get operation do not fail the build
redsolo commented on JENKINS-12908 TFS errors during get operation do not fail the build What kind of problems did it miss? If I have the incorrect server/auth then it will fail the build. But i guess there could be a problem with the TFS workspace if it has been moved to a new server... 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-15305) Job-level configuration is missing
redsolo commented on JENKINS-15305 Job-level configuration is missing When you say top level, do you mean that you enable it in the system configuration so ALL jobs have the game enabled? 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-14683) TFS Plugin parses pt_BR dates incorrectly
redsolo commented on JENKINS-14683 TFS Plugin parses pt_BR dates incorrectly How did you solve this problem? 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-15258) The TAP Plugin does not work with the CI Game Plugin
redsolo commented on JENKINS-15258 The TAP Plugin does not work with the CI Game Plugin Good to hear!! 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-15145) Unable to connect to the remote TFS server
redsolo
commented on JENKINS-15145
Unable to connect to the remote TFS server
Im guessing that it works if you remote desktop into the slave and run the command there? How is the slave started as a windows service or Web start?
If it is started as a windows service, perhaps you could start it as a JNLP/Web start slave? ie, logon to the machine and run {{java -jar slave.jar -jnlpUrl http://localhost:8080/computer/blaj/slave-agent.jnlp}} in a command prompt. This allows the slave to run in the same environment that you are using when testing the tf command.
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-15305) Job-level configuration is missing
redsolo commented on JENKINS-15305 Job-level configuration is missing I just tried it with the latest version of Jenkins and the plugin (1.483, 1.19) and it shows up as it should in the list of Post-Build Actions. To add it press the "Add post-build action" combo box and it should be shown in the drop down list. 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-14445) "Recording NUnit tests results" very slow
redsolo commented on JENKINS-14445 "Recording NUnit tests results" very slow Good to hear that the problem disappeared. 500 isn't that many so it must have been something else. let me know of you have any similar problem in the future – Posted from Bugbox for Android 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-14121) Nunit plugin 0.13 misses tests sometimes, sometimes not
redsolo commented on JENKINS-14121 Nunit plugin 0.13 misses tests sometimes, sometimes not It would be nice to look into the NUnit XML file when it does miss and does not miss tests. Otherwise it will hard to find the problem. 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-14445) "Recording NUnit tests results" very slow
redsolo commented on JENKINS-14445 "Recording NUnit tests results" very slow Im not sure, since the plugin is doing some XSL transformation which could take a long time. Do you have a lot of tests in the NUnit result? Is the NUnit XML file huge? Are there any other build steps that are run after the NUnit plugin? 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-13333) Clicking test result links in IE8 when you have JavaScript debugging on produces an error.
[ https://issues.jenkins-ci.org/browse/JENKINS-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161213#comment-161213 ] redsolo commented on JENKINS-1: --- The NUnit plugin is piggy backing on the JUnit framework for displaying tests. The plugin transforms the NUnit xml files into JUnit files which then are read by the JUnit functionality and shown in Jenkins. So this is probably not an issue in the NUnit plugin. As I dont have access to IE8, could you please do the same check with the tests at http://ci.jenkins-ci.org/view/Plugins/job/plugins_join/lastBuild/testReport/ ? Is it on only failing tests or passing tests as well? > Clicking test result links in IE8 when you have JavaScript debugging on > produces an error. > -- > > Key: JENKINS-1 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1 > Project: Jenkins > Issue Type: Bug > Components: nunit >Affects Versions: current > Environment: Running Jenkins as a Windows Service on a server. >Reporter: alexlombardi >Assignee: redsolo > Attachments: Error.doc > > > When you drill down to look at NUnit Test results for builds and JavaScript > debugging is enabled in IE8 it produces an object not found error (see > attached document). -- 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-9965) Nunit plugin does not display graph when fingerprinting is used on the xml report
[ https://issues.jenkins-ci.org/browse/JENKINS-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161067#comment-161067 ] redsolo commented on JENKINS-9965: -- I have not looked into this problem for a while and I assume that its still there. If anyone is willing to look into this that would be appreciated -- Posted from Bugbox for Android > Nunit plugin does not display graph when fingerprinting is used on the xml > report > - > > Key: JENKINS-9965 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9965 > Project: Jenkins > Issue Type: Bug > Components: nunit > Environment: XP, all latest software versions as of 6/13/11 >Reporter: mark lemay >Assignee: redsolo > > Nunit plug-in does not display graph when fingerprinting is used on the xml > report -- 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-13043) Test Results Trend graph missing intermittently
[ https://issues.jenkins-ci.org/browse/JENKINS-13043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] redsolo resolved JENKINS-13043. --- Resolution: Duplicate duplicate of Jenkins-9965, please add yourself as listener on that issue > Test Results Trend graph missing intermittently > --- > > Key: JENKINS-13043 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13043 > Project: Jenkins > Issue Type: Bug > Components: nunit >Affects Versions: current > Environment: Windows 2008R2 running Jenkins as a service. This isn't > an error, it's more of a bad state, so there's no stack trace to show. Here's > the /systemInfo dump: > Name Value > awt.toolkit sun.awt.windows.WToolkit > executable-war C:\Apps\Jenkins\jenkins.war > file.encoding Cp1252 > file.encoding.pkg sun.io > file.separator \ > hudson.diyChunking true > hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle > java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment > java.awt.headless true > java.awt.printerjob sun.awt.windows.WPrinterJob > java.class.path C:\Apps\Jenkins\jenkins.war > java.class.version 50.0 > java.endorsed.dirs C:\Apps\Jenkins\jre\lib\endorsed > java.ext.dirs C:\Apps\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext > java.home C:\Apps\Jenkins\jre > java.io.tmpdir C:\Windows\TEMP\ > java.library.path > C:\Apps\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\csvn\bin\;C:\csvn\Python25\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program > Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft > SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL > Server\100\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL > Server\100\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files (x86)\Microsoft > SQL Server\100\DTS\Binn\;C:\Program Files\NCover\;C:\Program Files\Microsoft > Windows Performance Toolkit\;c:\Program Files (x86)\Microsoft ASP.NET\ASP.NET > Web Pages\v1.0\;;. > java.runtime.name Java(TM) SE Runtime Environment > java.runtime.version 1.6.0_26-b03 > java.specification.name Java Platform API Specification > java.specification.vendor Sun Microsystems Inc. > java.specification.version 1.6 > java.vendor Sun Microsystems Inc. > java.vendor.url http://java.sun.com/ > java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi > java.version 1.6.0_26 > java.vm.info mixed mode > java.vm.name Java HotSpot(TM) Client VM > java.vm.specification.name Java Virtual Machine Specification > java.vm.specification.vendor Sun Microsystems Inc. > java.vm.specification.version 1.0 > java.vm.vendor Sun Microsystems Inc. > java.vm.version 20.1-b02 > line.separator > mail.smtp.sendpartial true > mail.smtps.sendpartial true > os.arch x86 > os.name Windows Server 2008 R2 > os.version 6.1 > path.separator ; > sun.arch.data.model 32 > sun.boot.class.path > C:\Apps\Jenkins\jre\lib\resources.jar;C:\Apps\Jenkins\jre\lib\rt.jar;C:\Apps\Jenkins\jre\lib\sunrsasign.jar;C:\Apps\Jenkins\jre\lib\jsse.jar;C:\Apps\Jenkins\jre\lib\jce.jar;C:\Apps\Jenkins\jre\lib\charsets.jar;C:\Apps\Jenkins\jre\lib\modules\jdk.boot.jar;C:\Apps\Jenkins\jre\classes > > sun.boot.library.path C:\Apps\Jenkins\jre\bin > sun.cpu.endian little > sun.cpu.isalist pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 > sun.desktop windows > sun.io.unicode.encoding UnicodeLittle > sun.java.command C:\Apps\Jenkins\jenkins.war --httpPort=8080 > sun.java.launcher SUN_STANDARD > sun.jnu.encoding Cp1252 > sun.management.compiler HotSpot Client Compiler > sun.os.patch.level Service Pack 1 > svnkit.http.methods Digest,Basic,NTLM,Negotiate > svnkit.ssh2.persistent false > user.country US > user.dir C:\Windows\system32 > user.home C:\ > user.language en > user.name $ > user.timezone America/Chicago > user.variant > Environment Variables > Name ↓ Value > ALLUSERSPROFILE C:\ProgramData > APPDATA C:\Windows\system32\config\systemprofile\AppData\Roaming > APR_ICONV1_PATH C:\csvn\bin\iconv\ > BASE C:\Apps\Jenkins > COMPUTERNAME 28SVMSVNCI051 > ComSpec C:\Windows\system32\cmd.exe > CommonProgramFiles C:\Program Files (x86)\Common Files > CommonProgramFiles(x86) C:\Program Files (x86)\Common Files > CommonProgramW6432 C:\Program Files\Common Files > FP_NO_HOST_CHECK NO > JAVA_HOME C:\Program Files (x86)\Java\jdk1.6.0_27 > JENKINS_HOME C:\Apps\Jenkins > LOCALAPPDATA C:\Windows\system32\config\systemprofile\AppData\Local > NUMBER_OF_PROCESSORS 2 > OS Windows_NT > PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC > PROCESSOR_ARCHITECTURE x86 > PROCESSOR_ARCHITEW6432 AMD64 > PROCESSOR_IDENTIFIER Intel64 Family 6 Model 23 Stepping 10, GenuineIntel > PROCESSOR_LEVEL 6 > PROCESSOR_REVISION 170a > P
[JIRA] (JENKINS-13043) Test Results Trend graph missing intermittently
[ https://issues.jenkins-ci.org/browse/JENKINS-13043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160421#comment-160421 ] redsolo commented on JENKINS-13043: --- Is this similar to the problem discussed in JENKINS-9965 ? > Test Results Trend graph missing intermittently > --- > > Key: JENKINS-13043 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13043 > Project: Jenkins > Issue Type: Bug > Components: nunit >Affects Versions: current > Environment: Windows 2008R2 running Jenkins as a service. This isn't > an error, it's more of a bad state, so there's no stack trace to show. Here's > the /systemInfo dump: > Name Value > awt.toolkit sun.awt.windows.WToolkit > executable-war C:\Apps\Jenkins\jenkins.war > file.encoding Cp1252 > file.encoding.pkg sun.io > file.separator \ > hudson.diyChunking true > hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle > java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment > java.awt.headless true > java.awt.printerjob sun.awt.windows.WPrinterJob > java.class.path C:\Apps\Jenkins\jenkins.war > java.class.version 50.0 > java.endorsed.dirs C:\Apps\Jenkins\jre\lib\endorsed > java.ext.dirs C:\Apps\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext > java.home C:\Apps\Jenkins\jre > java.io.tmpdir C:\Windows\TEMP\ > java.library.path > C:\Apps\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\csvn\bin\;C:\csvn\Python25\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program > Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft > SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL > Server\100\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL > Server\100\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files (x86)\Microsoft > SQL Server\100\DTS\Binn\;C:\Program Files\NCover\;C:\Program Files\Microsoft > Windows Performance Toolkit\;c:\Program Files (x86)\Microsoft ASP.NET\ASP.NET > Web Pages\v1.0\;;. > java.runtime.name Java(TM) SE Runtime Environment > java.runtime.version 1.6.0_26-b03 > java.specification.name Java Platform API Specification > java.specification.vendor Sun Microsystems Inc. > java.specification.version 1.6 > java.vendor Sun Microsystems Inc. > java.vendor.url http://java.sun.com/ > java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi > java.version 1.6.0_26 > java.vm.info mixed mode > java.vm.name Java HotSpot(TM) Client VM > java.vm.specification.name Java Virtual Machine Specification > java.vm.specification.vendor Sun Microsystems Inc. > java.vm.specification.version 1.0 > java.vm.vendor Sun Microsystems Inc. > java.vm.version 20.1-b02 > line.separator > mail.smtp.sendpartial true > mail.smtps.sendpartial true > os.arch x86 > os.name Windows Server 2008 R2 > os.version 6.1 > path.separator ; > sun.arch.data.model 32 > sun.boot.class.path > C:\Apps\Jenkins\jre\lib\resources.jar;C:\Apps\Jenkins\jre\lib\rt.jar;C:\Apps\Jenkins\jre\lib\sunrsasign.jar;C:\Apps\Jenkins\jre\lib\jsse.jar;C:\Apps\Jenkins\jre\lib\jce.jar;C:\Apps\Jenkins\jre\lib\charsets.jar;C:\Apps\Jenkins\jre\lib\modules\jdk.boot.jar;C:\Apps\Jenkins\jre\classes > > sun.boot.library.path C:\Apps\Jenkins\jre\bin > sun.cpu.endian little > sun.cpu.isalist pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 > sun.desktop windows > sun.io.unicode.encoding UnicodeLittle > sun.java.command C:\Apps\Jenkins\jenkins.war --httpPort=8080 > sun.java.launcher SUN_STANDARD > sun.jnu.encoding Cp1252 > sun.management.compiler HotSpot Client Compiler > sun.os.patch.level Service Pack 1 > svnkit.http.methods Digest,Basic,NTLM,Negotiate > svnkit.ssh2.persistent false > user.country US > user.dir C:\Windows\system32 > user.home C:\ > user.language en > user.name $ > user.timezone America/Chicago > user.variant > Environment Variables > Name ↓ Value > ALLUSERSPROFILE C:\ProgramData > APPDATA C:\Windows\system32\config\systemprofile\AppData\Roaming > APR_ICONV1_PATH C:\csvn\bin\iconv\ > BASE C:\Apps\Jenkins > COMPUTERNAME 28SVMSVNCI051 > ComSpec C:\Windows\system32\cmd.exe > CommonProgramFiles C:\Program Files (x86)\Common Files > CommonProgramFiles(x86) C:\Program Files (x86)\Common Files > CommonProgramW6432 C:\Program Files\Common Files > FP_NO_HOST_CHECK NO > JAVA_HOME C:\Program Files (x86)\Java\jdk1.6.0_27 > JENKINS_HOME C:\Apps\Jenkins > LOCALAPPDATA C:\Windows\system32\config\systemprofile\AppData\Local > NUMBER_OF_PROCESSORS 2 > OS Windows_NT > PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC > PROCESSOR_ARCHITECTURE x86 > PROCESSOR_ARCHITEW6432 AMD64 > PROCESSOR_IDENTIFIER Intel64 Family 6 Model 23 Stepping 10, GenuineIntel > PROCESSOR_LEVEL 6 > PROCESSOR_REVISION
[JIRA] (JENKINS-12079) Support master / slave usage
[ https://issues.jenkins-ci.org/browse/JENKINS-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158571#comment-158571 ] redsolo edited comment on JENKINS-12079 at 2/3/12 10:41 AM: I have tested it on slaves on my mac laptop and had no problems. But still it may be a problem that i havent seen yet. BTW, what version of Jenkins core are you using? was (Author: redsolo): I have tested it on slaves on my mac laptop and had no problems. But still it may be a problem that i havent seen yet. > Support master / slave usage > > > Key: JENKINS-12079 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12079 > Project: Jenkins > Issue Type: Bug > Components: locked-files-report >Affects Versions: current >Reporter: Thomas Fields >Assignee: redsolo > > Hi, > Does this plugin work in a master/slave setup? I've locked a file on my slave > but the build doesn't tell me that the file is locked, instead it just says: > 08:59:33 Building remotely on Build1 > 08:59:33 hudson.util.IOException2: remote file operation failed: > c:\JCI\workspace\Expat\COMPILER at hudson.remoting.Channel@64368400:Build1 > 08:59:33 at hudson.FilePath.act(FilePath.java:781) > 08:59:33 at hudson.FilePath.act(FilePath.java:767) > If the plugin doesn't tell me about locked files on slaves can that > functionality be added? > Cheers, > Tom. -- 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-12344) Support newer version of handle.exe output
[ https://issues.jenkins-ci.org/browse/JENKINS-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] redsolo resolved JENKINS-12344. --- Resolution: Fixed Merged a pull request by hokatichenci that has a fix for this, im rolling a release right now. > Support newer version of handle.exe output > -- > > Key: JENKINS-12344 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12344 > Project: Jenkins > Issue Type: Bug > Components: locked-files-report >Affects Versions: current > Environment: Linux master with Windows slave, Microsoft Handle v3.46 >Reporter: Mike Elkin >Assignee: redsolo > > The newer version of handle.exe has an additional column for file-type that > the current regular expression does not take into consideration. This causes > breakage and missed files even though it is in the console output. > Sample output: > Handle v3.46 > Copyright (C) 1997-2011 Mark Russinovich > Sysinternals - www.sysinternals.com > explorer.exe pid: 2848 type: File HQ\tester 4CC: > C:\jenkins\workspace\batchtest\otherdir > notepad.exepid: 4024 type: File HQ\tester C: > C:\jenkins\workspace\batchtest\somefile -- 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-8467) Run handle.exe with /accepteula switch to avoid headless hangs
[ https://issues.jenkins-ci.org/browse/JENKINS-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] redsolo resolved JENKINS-8467. -- Resolution: Fixed Merged a pull request by hokatichenci that has a fix for this, im rolling a release right now. > Run handle.exe with /accepteula switch to avoid headless hangs > -- > > Key: JENKINS-8467 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8467 > Project: Jenkins > Issue Type: Improvement > Components: locked-files-report >Affects Versions: current > Environment: Windows >Reporter: etomhel >Assignee: redsolo >Priority: Minor > > In an environment with many slaves it would be helpful if handle.exe was > executed with the /accepteula switch so that no window is opened. > If the license requires the EULA to be accepted, it can be a checkbox next to > the configuration of the path to the Handle executable. -- 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-11007) TFS plugin should allow multiple workspace folders (like TFS window allows in VS)
[ https://issues.jenkins-ci.org/browse/JENKINS-11007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158579#comment-158579 ] redsolo commented on JENKINS-11007: --- Is this a similar feature request to the JENKINS-4542? > TFS plugin should allow multiple workspace folders (like TFS window allows in > VS) > - > > Key: JENKINS-11007 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11007 > Project: Jenkins > Issue Type: Improvement > Components: plugin, tfs >Reporter: Kat Lim Ruiz >Priority: Critical > > The TFS plugin should allow to define multiple project folders for the > workspace. > This means that I should be allowed to say: > Project Path 1 = $/Proj/MyProduct/Application > Project Path 2 = $/Proj/MyProduct/Config > Project Path 3 = $/Proj/MyProduct/Database > I want to keep the Database folder out of the Application folder because of > better order. SO I can't do it right now, and I have to create three jobs in > Hudson to download each separately. -- 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-11950) TFS Plugin - Allow downloading the files with the repository date
[ https://issues.jenkins-ci.org/browse/JENKINS-11950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] redsolo resolved JENKINS-11950. --- Resolution: Won't Fix I cant find any option on the TFS/TEE command line tool to do this. As the plugin rely on the command line tool to do the actual job of checking out code, i cant see any way to implement this properly in the plugin. Also this seems to be common problem with the TFS implementation. Sorry Regards Erik > TFS Plugin - Allow downloading the files with the repository date > - > > Key: JENKINS-11950 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11950 > Project: Jenkins > Issue Type: Improvement > Components: tfs > Environment: Windows >Reporter: Kat Lim Ruiz >Assignee: redsolo >Priority: Minor > Labels: tfs > > Hi > I think a good improvement to the tfs plugin would be to add a checkbox to > say: download the files and set the modified date to be the repository's. If > deactivated, use the local date. This way if I do a download but only want to > use those files modified since XX date, I can do it. Today if I do a "Use > Update = false" or a new job using the same TFS workspace, then my build > scripts would give me ALL files. -- 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-12079) Support master / slave usage
[ https://issues.jenkins-ci.org/browse/JENKINS-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158571#comment-158571 ] redsolo commented on JENKINS-12079: --- I have tested it on slaves on my mac laptop and had no problems. But still it may be a problem that i havent seen yet. > Support master / slave usage > > > Key: JENKINS-12079 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12079 > Project: Jenkins > Issue Type: Bug > Components: locked-files-report >Affects Versions: current >Reporter: Thomas Fields >Assignee: redsolo > > Hi, > Does this plugin work in a master/slave setup? I've locked a file on my slave > but the build doesn't tell me that the file is locked, instead it just says: > 08:59:33 Building remotely on Build1 > 08:59:33 hudson.util.IOException2: remote file operation failed: > c:\JCI\workspace\Expat\COMPILER at hudson.remoting.Channel@64368400:Build1 > 08:59:33 at hudson.FilePath.act(FilePath.java:781) > 08:59:33 at hudson.FilePath.act(FilePath.java:767) > If the plugin doesn't tell me about locked files on slaves can that > functionality be added? > Cheers, > Tom. -- 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-12597) Make plug-in compatible with LTS version
[ https://issues.jenkins-ci.org/browse/JENKINS-12597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] redsolo resolved JENKINS-12597. --- Resolution: Won't Fix The internal framework in Jenkins core for showing avatars for users was added in 1.434. This should be fixed when the next LTS is released that should have this fix (depends on what version the next LTS is based). > Make plug-in compatible with LTS version > > > Key: JENKINS-12597 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12597 > Project: Jenkins > Issue Type: Improvement > Components: gravatar >Reporter: Ulli Hafner >Assignee: redsolo > > Is there a reason that this plug-in is not compatible with LTS version of > Jenkins? -- 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
