[JIRA] (JENKINS-15029) Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail.
Gregory Boissinot commented on JENKINS-15029 Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail. For summary, it doesn't work for only Windows Server 2003? 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-15307) Trigger badge images broken when Jenkins is installed at non-root context
Baptiste Mathus commented on JENKINS-15307 Trigger badge images broken when Jenkins is installed at non-root context Hi Keith, I guess you're deploying Jenkins inside an appserver. For the record, could you tell us which one? That way we might be able to check with your very server version. Sorry about that. We'll fix it very soon. Cheers 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-15311) Email-ext can't recover after a failed smtp delivery
Robert Nordan created JENKINS-15311 Email-ext cant recover after a failed smtp delivery Issue Type: Bug Affects Versions: current Assignee: Slide-O-Mix Components: email-ext Created: 26/Sep/12 7:16 AM Description: I used the email-ext to set up notifications for build success, but had Jenkins set up to use an smtp server that was company-internal. This worked fine when I only had company internal mail recipients, but when I added an outside recipient, the build failed because email-ext returned an SMTPException: Could not deliver. All this is fine and expected in a PEBKAC situation. However, when I had set up a new, proper smtp server in Jenkins and sent successful test emails through the Jenkins configuration page, I figured everything would be fine. But the next time a build finished, no emails were sent out even though the build finished as normal. Checking the logs I found that it said: " Email was triggered for: Success Sending email for trigger: Success " The two usual last lines with "Sending email to: blah@blah, Finished: SUCCESS" were missing. Obviously email-ext was unable to recover from the previous error even though the settings had been corrected. I worked around the problem by restarting Jenkins, and everything started working as expected with the new configuration. Project: Jenkins Labels: email-ext Priority: Minor Reporter: Robert Nordan 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-15166) Gradle plugin fails to save selected Gradle Version in Project configuration
Johannes Rost commented on JENKINS-15166 Gradle plugin fails to save selected Gradle Version in Project configuration Since the Problem seems to be fixed, I would like to know when the fix is available. Can someone tell me? 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-12861) klocwork - update to recognize 9.5.x xml schema
Waldek M commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema Hello, It doesn't seem to work fine with 1.12 I'm using KW 9.5.3, and that's what I got in build log: == Starting the klocwork analysis. Version 9.6 or later of Klocwork detected. Only Klocwork review is available. Parse_errors.log and build.log can be accessed on the review ERROR: Publisher com.thalesgroup.hudson.plugins.klocwork.KloPublisher aborted due to exception java.lang.NullPointerException at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.perform(KloPublisher.java:186) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) xUnit INFO - Starting to record. 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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD created JENKINS-15313 Trigger on Updated Change does not fetch the last commit Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 26/Sep/12 9:14 AM Description: I made a job with the following config : parameters : GERRIT_REFSPEC default value refs/heads/release GERRIT_BRANCH default value $GERRIT_REFNAME Git plugin config : Url of repo : a right url Refspec : $GERRIT_REFSPEC Name or Repository : origin Branch specifier : origin/$GERRIT_BRANCH Gerrit Trigger config : Trigger on Change Merged , Ref Updated Dynamic config (..) (should be right) My issue is on Ref Updated trigger, the log prints it fetches the origin/release (if I pushed directly on release) but in facts it does not get the checkout the last version. eg : I updated an artifact version in a pom.xml, I push it by-passing gerrit, the refs updated triggers works and trigger my job but it does not take in account my pom.xml modification . 26/09/2012 11:08:48 Last Built Revision: Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:48 Fetching changes from 1 remote Git repository 26/09/2012 11:08:48 Fetching upstream changes from ssh://gerrit.it.int/it-lang 26/09/2012 11:08:49 Commencing build of Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:49 Checking out Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) and the git history : 26/09/2012 11:08:48 Last Built Revision: Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:48 Fetching changes from 1 remote Git repository 26/09/2012 11:08:48 Fetching upstream changes from ssh://gerrit.it.int/it-lang 26/09/2012 11:08:49 Commencing build of Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:49 Checking out Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) Environment: jenkins 1.482 Gerrit Trigger 2.6.0 Project: Jenkins Priority: Major Reporter: Greg BOUGEARD 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-15314) Static methods are not logged
Mads Nielsen created JENKINS-15314 Static methods are not logged Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: logging Created: 26/Sep/12 9:19 AM Description: There seems to be some issues with the logger and static method calls. I'm not seeing the logging statements inside static methods in my log. Project: Jenkins Priority: Minor Reporter: Mads Nielsen 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-15315) Slave polling hungup
Alexey Larsky created JENKINS-15315 Slave polling hungup Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: perforce Created: 26/Sep/12 9:23 AM Description: Project on slave builders with perforce SCM are hanging after several hours. Perforces workspaces configered as permanent with only one checkbox "Don't update client workspace". Main log: Sep 26, 2012 1:16:28 PM hudson.plugins.perforce.PerforceSCM getEffectiveClientName WARNING: Could not get hostname for slave SlaveName Polling log: Started on Sep 26, 2012 1:19:27 PM Looking for changes... Using node: Builder Using remote perforce client: ws_name terminate here Environment: Windows 7 SP1 x64 master Windows 7 SP1 x64 slave connection over JNLP agent Project: Jenkins Priority: Major Reporter: Alexey Larsky 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-15314) Static methods are not logged
Mads Nielsen resolved JENKINS-15314 as Not A Defect Static methods are not logged Change By: Mads Nielsen (26/Sep/12 9:26 AM) Status: Open Resolved Resolution: NotADefect 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-15313) Trigger on Updated Change does not fetch the last commit
rsandell commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit The refUpdated event that gerrit sends does not contain a ref spec, since it is not tied to a change. So there is no parameter added to the build named GERRIT_REFSPEC when it is triggered bu a ref updated event. This makes it hard to easily configure a job to trigger on both "change based" events and ref updated events. unless you use a bash script or something to check out the code. I missed to add that to the help text. 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-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe updated JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Change By: James Howe (26/Sep/12 9:35 AM) Environment: DebianSqueezeonLinuxqa012.6.26-2-vserver-amd64#1SMPTueJan2506:09:17UTC2011x86_64GNU/Linux MacOSX 10.7.3x86_64 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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit When I saw the 2.6.0 announcement I was happy because I was going to refactor some jobs into in a single one. But if I well understand you, I still have to have : 1 job triggered on Refs Updated (without any params) 1 job triggerd on Change Merged (without any params) 1 job manually triggerd (with REFSPEC and BRANCH params) The three jobs will do the same thing (mvn deploy), but because the trigger is different, I have to keep three jobs. (Maybe I can merge the two first ones?) 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-15313) Trigger on Updated Change does not fetch the last commit
rsandell commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit Change Merged is a "change based" event so I think that the refspec should be there, it is only the ref updated that is special. So I think that the two last jobs could be merged into one. But I haven't tested it my self 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Alex Klein commented on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation I also have a lot of problems on getting this up and running. I managed to get jenkins to start up the VM, but still haven't managed for the second part of the connect where it is actually supposed to do something. A completed guide (not just the VirtualBox part) would be very helpful... One problem I ran into was to get the vboxwebsrv to find the VMs when starting as a scheduled windows task. The solution to this was creating a link as described here: http://code.google.com/p/phpvirtualbox/wiki/Windows2008Service But all the documentation of actually getting the Jenkins Slave Agent to run inside the VM seems to be obsolete/incorrect. Still haven't managed to figure this one out. 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-15316) Jenkins tries to create symbolic links on Windows system
Karsten Günther created JENKINS-15316 Jenkins tries to create symbolic links on Windows system Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow, build-pipeline Created: 26/Sep/12 10:45 AM Description: Not sure if the assigned components are correct. Please correct them if necessary. After update to jenkins 1.483 I get an error message at the beginning of each build: Build wurde durch eine SCM-Änderung ausgelöst. ln 2012-09-26_12-23-54 f:\Jenkins\jobs\xxx\builds\1 failed java.nio.file.FileSystemException: f:\Jenkins\jobs\xxx\builds\1: Dem Client fehlt ein erforderliches Recht. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(Unknown Source) at java.nio.file.Files.createSymbolicLink(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.createSymlinkJava7(Util.java:1065) at hudson.Util.createSymlink(Util.java:1009) at hudson.model.Run.execute(Run.java:1500) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: Windows 7 64bit Project: Jenkins Labels: build scm Priority: Major Reporter: Karsten Günther 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-13790) Subversion externals fail
rattapon sattayarat commented on JENKINS-13790 Subversion externals fail I'm using 1.4.3, see this error still. 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-15318) Launch Slave Agent test does not shutdown VM on failure
Alex Klein created JENKINS-15318 Launch Slave Agent test does not shutdown VM on failure Issue Type: Bug Assignee: godin Components: virtualbox Created: 26/Sep/12 11:22 AM Description: I currently haven't set up the jenkins slave agent, so creating a new node and doing the launch test succeeds in starting the VM but fails to connect. At some point "VirtualBox Maximum number of attempts reached" happens but the VirtualBox seems to stay running (at least the windows process VirtualBox.exe is still there). I also just noticed that the log of the launch test shows "maximum number..." but still keeps the progress indicator spinning. Maybe for the plug-in the launch is still stuck? Environment: Jenkins 1.480 running on a Windows Server 2003, VirtualBox 4.2, Virtual Box Plugin 0.5.0, FireFox 15.0.1 Project: Jenkins Priority: Major Reporter: Alex Klein 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-15130) BuildTrigger ambiguous
Per Arnold Blaasmo commented on JENKINS-15130 BuildTrigger ambiguous If it helps, I got this stacktrace on 1.482: Exception: java.lang.IllegalArgumentException: BuildTrigger is ambiguous; matches both hudson.plugins.parameterizedtrigger.BuildTrigger and hudson.tasks.BuildTrigger Stacktrace: javax.servlet.ServletException: java.lang.IllegalArgumentException: BuildTrigger is ambiguous; matches both hudson.plugins.parameterizedtrigger.BuildTrigger and hudson.tasks.BuildTrigger at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
[JIRA] (JENKINS-15308) + in the Page name not supported
David Ehrenberger commented on JENKINS-15308 + in the Page name not supported Your questions led me to try this combination and it worked: Confluence page name is "Release Notes Test Page" URL shows "Release+Notes+Test+Page" Jenkins configuration for Page is "Release Notes Test Page" (says OK: Release Notes Test Page) If I change the Jenkins configuration for Page to be "Release+Notes+Test+Page" I'll still get the "OK: Release Notes Test Page" but at runtime I get the error mentioned in the description. Running Confluence v3.4.3 for what its worth. 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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit I made some tests : First job : Triggered on Change Merged Git config : Refspec = $GERRIT_REFSPEC , Branch to build = $GERRIT_BRANCH Second job : Triggered on Update Refs Git config : Refspec = null, branch to build = $GERRIT_REFNAME 1 test : git push bypassing code review. Second job is well triggered. It checks out the right code (I checked it on the jenkins job workspace with a git log). = Test success, that it is exactly what I expected 2 test : git push to code review then submit First job is well triggered. It DOES NOT check out the right code. (I checked it on the jenkins job workspace with a git log) In my case it's 3 commits late. Second job is triggered too (NOT EXPECTED!) but it checks out the right code. = Test failed. First job is well triggered but does not checks out the right code, second job is triggered but I did not want to. Was I wrong on some config? I can give you the parameters for each test job if it can help 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-10295) project name not updated in join plugin after renaming of involved project
evernat resolved JENKINS-10295 as Incomplete project name not updated in join plugin after renaming of involved project No response from the reporter so closing this issue as incomplete. Change By: evernat (26/Sep/12 1:24 PM) Status: Open Resolved Resolution: Incomplete 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-1777) Canceling a batch task in the queue results in 404 error page
evernat commented on JENKINS-1777 Canceling a batch task in the queue results in 404 error page Hi Alexander, The issue JENKINS-14813 is about 404 when canceling queue item. And it is now fixed in Jenkins v1.479. Is it still a 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-15319) Error startign slave nodes
John Dyer created JENKINS-15319 Error startign slave nodes Issue Type: Bug Assignee: Francis Upton Components: ec2 Created: 26/Sep/12 1:34 PM Description: Every day or so I get errors like this when starting a slave: ERROR: The instance ID 'i-6fdc2512' does not exist Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: 195aae09-8d42-4f24-9a30-2d31b7447818, AWS Error Code: InvalidInstanceID.NotFound, AWS Error Message: The instance ID 'i-6fdc2512' does not exist at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:547) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:284) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:169) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:5684) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:2543) at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:97) at hudson.plugins.ec2.EC2Computer.getState(EC2Computer.java:76) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:33) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) 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) and I have to manually delete them to unblock jobs. The odd part is that this instance actually does exists on the EC2 Mgmnt console. Any idea what this is about and how I can resolve it ? -John Environment: Jenkins 1.481 Project: Jenkins Priority: Critical Reporter: John Dyer 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-15320) Add 'Ignore missing file' option.
Verbitan created JENKINS-15320 Add Ignore missing file option. Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: cppcheck Created: 26/Sep/12 1:42 PM Description: Currently I have a matrix job which builds on both Linux and Solaris. As my cppcheck binary is only compiled for Linux, I surround the command to run cppcheck in an if Linux block. Now the plugin has an option to ignore a blank file, but it doesn't have an option to ignore a missing file. Because of this my Solaris build always fails. Project: Jenkins Priority: Minor Reporter: Verbitan 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-15321) Campfire proxy support doesn't allow for basic auth with the proxy server
Justin Harringa created JENKINS-15321 Campfire proxy support doesnt allow for basic auth with the proxy server Issue Type: Improvement Assignee: jenslukowski Components: campfire Created: 26/Sep/12 3:04 PM Description: In Campfire.java, HttpClient is being used to set the proxy host and port but there isn't currently support for passing credentials to the proxy. I may try to work on this if I get some time but thought I would get this out there in case others can work on it and test. Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Justin Harringa 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-15169) Warning Plugin - Graph Configuration Error
Chris Engler commented on JENKINS-15169 Warning Plugin - Graph Configuration Error I checked the URL provided, I could change the graphs. I went back to my server. Starting in Local Host, the graph information does get saved, but it does take me to the 404 page still. Going to my sever from the Jenkins URL, configuring the graphs displays and there is no 404 error after save. 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-15169) Warning Plugin - Graph Configuration Error
Chris Engler edited a comment on JENKINS-15169 Warning Plugin - Graph Configuration Error I checked the URL provided, I could change the graphs. I went back to my server. Starting in Local Host, the graph information does get saved, but it does take me to the 404 page still. Going to my sever from the Jenkins URL, configuring the graphs displays and there is no 404 error after save. Is it possible to have the same behavior when going throught the localhost address? 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-15304) Drop list broken, does nothing
wernight commented on JENKINS-15304 Drop list broken, does nothing Chrome 22 fixed it after a full cache cookies reset. Strangely I had to clear those else I couldn't log in Jenkins. 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-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham created JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 26/Sep/12 4:34 PM Description: A .tap file containing a NOTESTS result (from eg a skip_all declaration in a .t file) such as /opt/performance/scripts/t/dbcoststest1.t .. skipped: No Relevant Tests as No DB Costs for GetSmoidTrackV11New Files=1, Tests=0, 1 wallclock secs ( 0.01 usr 0.02 sys + 0.54 cusr 0.04 csys = 0.61 CPU) Result: NOTESTS results in the following errors when running a plan from Jenkins: Parsing TAP test result [/var/lib/jenkins/jobs/Performance-Server-Trunk/builds/2012-09-26_16-06-21/tap/dbcostsGetSmoidTrackV11New.tap]. org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan. at org.tap4j.parser.Tap13YamlParser.parseFile(Tap13YamlParser.java:587) at org.tap4j.plugin.TapParser.parse(TapParser.java:94) at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:240) at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:182) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:996) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627) at hudson.model.Run.run(Run.java:1438) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:479) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: org.tap4j.parser.ParserException: Missing TAP Plan. at org.tap4j.parser.Tap13YamlParser.checkTAPPlanIsSet(Tap13YamlParser.java:353) at org.tap4j.parser.Tap13YamlParser.postProcess(Tap13YamlParser.java:736) at org.tap4j.parser.Tap13YamlParser.parseFile(Tap13YamlParser.java:585) ... 12 more Environment: centos 6 Project: Jenkins Labels: tap Priority: Major Reporter: Alex Newnham 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-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin One course of action would be to mark the file as skipped with no associated FAIL, given that No Tests are being explicitly requested. 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-13790) Subversion externals fail
dlavelle commented on JENKINS-13790 Subversion externals fail Rattapon, You may have to revert your plugin back to the previous version and also make sure you are using Subversion 1.6 working copy format(main settings). then you also must start with a fresh workspace for the Jenkins job so a fresh checkout is made. Have you done this? -Dewayne 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-15323) Allow user to define X and Y axis
bbonn created JENKINS-15323 Allow user to define X and Y axis Issue Type: New Feature Assignee: nidaley Components: plot Created: 26/Sep/12 5:26 PM Description: It would be great if the plot plugin accepted both axis if fed a file. I would like to produce reports form a file where I provide both data points and the plugin just produces the chart of my choice. Kind of like you could do with Excel. Environment: Windows Server 2008 Project: Jenkins Labels: reporting plot Priority: Minor Reporter: bbonn 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-15307) Trigger badge images broken when Jenkins is installed at non-root context
Baptiste Mathus started work on JENKINS-15307 Trigger badge images broken when Jenkins is installed at non-root context Change By: Baptiste Mathus (26/Sep/12 6:05 PM) Status: Open InProgress 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-15307) Trigger badge images broken when Jenkins is installed at non-root context
SCM/JIRA link daemon
commented on JENKINS-15307
Trigger badge images broken when Jenkins is installed at non-root context
Code changed in jenkins
User: Baptiste Mathus
Path:
src/main/resources/org/jenkinsci/plugins/buildtriggerbadge/BuildTriggerBadgeAction/badge.jelly
http://jenkins-ci.org/commit/buildtriggerbadge-plugin/d0b35b17643a1e6f4da0c4fe3c06dcaa4b748e51
Log:
Fix JENKINS-15307 : support jenkins when installed as a non-root context.
Now the ${rootURL} is prepended to the icon path,
as it should have been from the start...
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-15307) Trigger badge images broken when Jenkins is installed at non-root context
Baptiste Mathus stopped work on JENKINS-15307 Trigger badge images broken when Jenkins is installed at non-root context Change By: Baptiste Mathus (26/Sep/12 6:55 PM) Status: InProgress Open 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-15311) Email-ext can't recover after a failed smtp delivery
nalin_makar updated JENKINS-15311 Email-ext cant recover after a failed smtp delivery Change By: nalin_makar (26/Sep/12 7:36 PM) Priority: Minor Major 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-15311) Email-ext can't recover after a failed smtp delivery
nalin_makar commented on JENKINS-15311 Email-ext cant recover after a failed smtp delivery We ran into this issue with our deployment as well. We are running v2.24.1. Email-Ext stops sending out any emails until Jenkins is restarted once it reaches this state. 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh created JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Issue Type: Bug Assignee: Slide-O-Mix Attachments: stat.png Components: email-ext Created: 26/Sep/12 7:53 PM Description: email-ext 2.24.1, jenkins 1.483 I use static-analysis for a Maven project and all the warnings data come up empty (see attachment) If I switch it to Freestyle project, then the data shows up. Project: Jenkins Priority: Major Reporter: hhuynh 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (26/Sep/12 7:54 PM) Description: email-ext2.24.1,jenkins1.483Iusestatic-analysis template foraMavenprojectandallthewarningsdatacomeupempty(seeattachment)IfIswitchittoFreestyleproject,thenthedatashowsup. 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-15045) Support Github commit status API
Matt Sweeney commented on JENKINS-15045 Support Github commit status API I'd also love to see this feature! 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-15045) Support Github commit status API
Juan Muller commented on JENKINS-15045 Support Github commit status API Have been looking forward for its implementation! 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (26/Sep/12 8:16 PM) Description: email-ext2.24.1,jenkins1.483 ,findbugsplugin4.44,StaticAnalysisUtilities1.47 Iusestatic-analysistemplateforaMavenprojectandallthewarningsdatacomeupempty(seeattachment)IfIswitchittoFreestyleproject,thenthedatashowsup. 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Slide-O-Mix commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project This is not an issue with email-ext, external plugins used in templates are not the realm of the email-ext 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Thanks for the clarification. Please direct the bug to its appropriate component. My guess is the Findbugs plugin in this case 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: hhuynh (26/Sep/12 8:25 PM) Component/s: findbugs 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-14829) svn tagging pluggin doesnt delete old tag
kalpesh soni commented on JENKINS-14829 svn tagging pluggin doesnt delete old tag bump 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Slide-O-Mix updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: Slide-O-Mix (26/Sep/12 8:25 PM) Component/s: email-ext 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: Ulli Hafner (26/Sep/12 8:46 PM) Assignee: Slide-O-Mix UlliHafner Component/s: email-ext 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
Ulli Hafner updated JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project Change By: Ulli Hafner (26/Sep/12 8:46 PM) Priority: Major Minor 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-15045) Support Github commit status API
Kohsuke Kawaguchi commented on JENKINS-15045 Support Github commit status API The github-api library has this implemented. The next step is someone to take advantages of it in the github 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-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-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-15325) Create Job api broken on java7
Konstantin Shabanov created JENKINS-15325 Create Job api broken on java7 Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Sep/12 9:28 PM Description: Steps to reproduce: run jenkins using java7 $ curl "http://host/createItem?name=test" -X POST -H "Content-Type:application/xml" (Submitting "-d "@config.xml"" is optional) log - https://gist.github.com/ae939b8c79961ad4ff41 I tried several setups with different java7 versions on different platforms and got same behavior everywhere. The problem disappeared when I switched to java6. Project: Jenkins Priority: Critical Reporter: Konstantin Shabanov 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-12861) klocwork - update to recognize 9.5.x xml schema
Gregory Boissinot reopened JENKINS-12861 klocwork - update to recognize 9.5.x xml schema The issue persists in another code part. Change By: Gregory Boissinot (26/Sep/12 9:38 PM) Resolution: Fixed Status: Resolved Reopened 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-15311) Email-ext can't recover after a failed smtp delivery
Slide-O-Mix commented on JENKINS-15311 Email-ext cant recover after a failed smtp delivery I will try and reproduce this locally. 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-12861) klocwork - update to recognize 9.5.x xml schema
Gregory Boissinot resolved JENKINS-12861 as Fixed klocwork - update to recognize 9.5.x xml schema Change By: Gregory Boissinot (26/Sep/12 9:41 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15166) Gradle plugin fails to save selected Gradle Version in Project configuration
Gregory Boissinot commented on JENKINS-15166 Gradle plugin fails to save selected Gradle Version in Project configuration The fix is available in version 1.20, available since Sept.19. Wiki page is updated https://wiki.jenkins-ci.org/display/JENKINS/Gradle+Plugin Manual download here http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/gradle/1.20/ If you any further problems, please let me know. 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-15320) Add 'Ignore missing file' option.
Gregory Boissinot started work on JENKINS-15320 Add Ignore missing file option. Change By: Gregory Boissinot (26/Sep/12 9:59 PM) Status: Open InProgress 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-15320) Add 'Ignore missing file' option.
Gregory Boissinot commented on JENKINS-15320 Add Ignore missing file option. I'm not sure it is the best way to solve this issue. If I add this feature into the CppCheck plugin, I should add it in other plugins too. In my opinion, a better solution could be to use the Run Condition plugin https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin Please look at it and let me know. 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-11466) reenable ability to let maven decide the versioning
teilo commented on JENKINS-11466 reenable ability to let maven decide the versioning it is needed for the current integration with Nexus - so you can find the version that has been deployed. It's also for some stuff that's in the pipeline If you have not changed versions / added any modules since the last build then the "specify for every module" (which will be re-instated) will give you exactly the same result at the expense of a larger UI screen. 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-15326) Error running ant with matrix build
Roger Lopez created JENKINS-15326 Error running ant with matrix build Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 26/Sep/12 9:59 PM Description: I have set up a matrix job with the same configuration as a working non-matrix job. I have a single build step that invokes a simple ant target. On the Sauce axis, I have chosen two browser configs and on the Slaves axis, I have chosen a single slave. This yields two jobs. When the two jobs run, there is an ant error which seems to be failing because of the way that the SELENIUM_DRIVER argument is passed to ant. [rh2vagrant] $ ant -DSELENIUM_DRIVER=sauce-ondemand:?os=Linuxbrowser=googlechromebrowser-version= -Darguments="-DSELENIUM_DRIVER=sauce-ondemand:?os=Linuxbrowser=googlechromebrowser-version=" -Dlabel=rh2vagrant -Dbehat.profile="" ci /usr/bin/ant: line 326: browser-version=: command not found Buildfile: build.xml [rh2vagrant] $ ant "-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows 2008browser=iexploreproxybrowser-version=9" '-Darguments="-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows 2008browser=iexploreproxybrowser-version=9"' -Dlabel=rh2vagrant -Dbehat.profile="" ci /usr/bin/ant: line 326: browser-version=9: command not found Buildfile: build.xml BUILD FAILED Target "2008" does not exist in the project "behat". In the first output, the SELENIUM_DRIVER argument is completely unquoted, while in the second output, the entire thing, including the -D is in quotes. Could I be doing something wrong? Any help is greatly appreciated. Project: Jenkins Priority: Major Reporter: Roger Lopez 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-15326) Error running ant with matrix build
Roger Lopez
updated JENKINS-15326
Error running ant with matrix build
Change By:
Roger Lopez
(26/Sep/12 10:02 PM)
Description:
Ihavesetupamatrixjobwiththesameconfigurationasaworkingnon-matrixjob.Ihaveasinglebuildstepthatinvokesasimpleanttarget.OntheSauceaxis,IhavechosentwobrowserconfigsandontheSlavesaxis,Ihavechosenasingleslave.Thisyieldstwojobs.Whenthetwojobsrun,thereisananterrorwhichseemstobefailingbecauseofthewaythattheSELENIUM_DRIVERargumentispassedtoant.{code}[rh2vagrant]$ant-DSELENIUM_DRIVER=sauce-ondemand:?os=Linuxbrowser=googlechromebrowser-version=-Darguments=-DSELENIUM_DRIVER=sauce-ondemand:?os=Linuxbrowser=googlechromebrowser-version=-Dlabel=rh2vagrant-Dbehat.profile="">/usr/bin/ant:line326:browser-version=:commandnotfoundBuildfile:build.xml{code}{code}[rh2vagrant]$ant-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows2008browser=iexploreproxybrowser-version=9-Darguments=-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows2008browser=iexploreproxybrowser-version=9-Dlabel=rh2vagrant-Dbehat.profile="">/usr/bin/ant:line326:browser-version=9:commandnotfoundBuildfile:build.xmlBUILDFAILEDTarget2008doesnotexistintheprojectbehat.{code}Inthefirstoutput,theSELENIUM_DRIVERargumentiscompletelyunquoted,whileinthesecondoutput,theentirething,includingthe-Disinquotes.CouldIbedoingsomethingwrong?Anyhelpisgreatlyappreciated.
IamrunningJenkinsver.1.476withSauceOnDemandpluginver.1.21.
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-12875) No valid crumb was included in the request errors all around
windyroad commented on JENKINS-12875 No valid crumb was included in the request errors all around I've offered USD100.00 at FreedomSponsors to have this fixed (http://www.freedomsponsors.org/core/issue/31/no-valid-crumb-was-included-in-the-request-errors-all-around). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay. 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-15326) Error running ant with matrix build
Roger Lopez commented on JENKINS-15326 Error running ant with matrix build Upon further inspection, it looks like this may actually be a problem with the -Darguments argument. Line 326 of /usr/bin/ant is eval $ant_exec_command Adding an echo of $ant_exec_command before the eval gives me this: exec "/usr/lib/jvm/java/bin/java" -classpath "/usr/share/java/ant.jar:/usr/share/java/ant-launcher.jar:/usr/share/java/jaxp_parser_impl.jar:/usr/share/java/xml-commons-apis.jar:/usr/lib/jvm/java/lib/tools.jar" -Dant.home="/usr/share/ant" -Dant.library.dir="/usr/share/ant/lib" org.apache.tools.ant.launch.Launcher -cp "" "-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows 2008browser=iexploreproxybrowser-version=9" "-Darguments="-DSELENIUM_DRIVER=sauce-ondemand:?os=Windows 2008browser=iexploreproxybrowser-version=9"" "-Dlabel=rh2vagrant" "-Dbehat.profile="" class="code-quote">" "ci" So it looks like the quotes in -Darguments are to blame. 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
cowwoc commented on JENKINS-15305 Job-level configuration is missing Confirmed. Is there a way to fix this (convert it to a top-level configuration option)? There is a similar plugin by the name "buildcoin" and it provides top-level configuration. Alternatively (less desirable), please document where to find the configuration option in the Wiki 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
[JIRA] (JENKINS-15315) Slave polling hungup
Rob Petti assigned JENKINS-15315 to Rob Petti Slave polling hungup Change By: Rob Petti (27/Sep/12 2:23 AM) Assignee: RobPetti 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-15327) Publish Robot Framework test results not support chinese character
wing king
created JENKINS-15327
Publish Robot Framework test results not support chinese character
Issue Type:
Bug
Affects Versions:
current
Assignee:
jpiironen
Components:
robot-plugin
Created:
27/Sep/12 2:44 AM
Description:
Testcase:
Set Alert
Set Global Variable${alert_empty_user}用户名不能为空
Set Global Variable${alert_empty_pwd}密码不能为空
it runs success in robot ride,
and in jekins,the log.html display correctly.
but the "Robot Results" doesn't work.
the console output:
Robot results publisher started...
-Parsing output xml:
Failed!
java.io.IOException: Parsing of output xml failed!
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:90)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:50)
at hudson.FilePath.act(FilePath.java:852)
at hudson.FilePath.act(FilePath.java:825)
at hudson.plugins.robot.RobotParser.parse(RobotParser.java:45)
at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:235)
at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:257)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
at hudson.model.Run.execute(Run.java:1527)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: com.ctc.wstx.exc.WstxParsingException: Unexpected close tag /arguments; expected /arg.
at row,col {unknown-source}: 19,11
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:630)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
at com.ctc.wstx.sr.BasicStreamReader.reportWrongEndElem(BasicStreamReader.java:3258)
at com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3218)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2832)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at hudson.plugins.robot.RobotParser$RobotParserCallable.processTest(RobotParser.java:190)
at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:158)
at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:114)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:88)
... 15 more
Build step 'Publish Robot Framework test results' changed build result to FAILURE
Finished: FAILURE
the output.xml 19,11:
arguments
arg${alert_empty_user}/arg
arg用户名不能为空/arg
/arguments
if i add "" ,it works:
Set Alert
Set Global Variable${alert_empty_user}'用户名不能为空'
Set Global Variable${alert_empty_pwd}'密码不能为空'
Environment:
pybot 2.7.4,Jenkins ver. 1.483
xp sp3 ,chinese
Project:
Jenkins
Priority:
Major
Reporter:
wing king
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-15305) Job-level configuration is missing
cowwoc commented on JENKINS-15305 Job-level configuration is missing No. I mean it should show up in a job's configuration at the same level as "Source Code Management" (meaning, one level higher than it is currently). That being said, I am beginning to see the logic of listing it as a post-build step. I think it's going to be hard for users to find it unless you document it in a prominent location. Also, take a look at the way Buildcoin works. They're doing a lot of things right, from a usability point of view (they do a lot more to entice users to fix builds and earn points/money, such as sending out emails). 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
