[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-25579) On remote host config: add option to ignore cert
Brantone created JENKINS-25579 On remote host config: add option to ignore cert Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 12/Nov/14 9:12 PM Description: In some cases a remote host has a self-signed cert. Would be nice to have checkbox option to ignore the cert. Akin to `--no-check-certificate` that wget has. Project: Jenkins Priority: Minor Reporter: Brantone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Sam Xiao
reopened JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Change By:
Sam Xiao
(12/Nov/14 9:39 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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Sam Xiao
updated JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Can we port this back to LTS?
Change By:
Sam Xiao
(12/Nov/14 9:39 PM)
Labels:
1.532.3-fixedlazy-loading
lts-candidate
performance
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Jesse Glick
resolved JENKINS-20892 as Fixed
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Change By:
Jesse Glick
(12/Nov/14 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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Jesse Glick
updated JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Change By:
Jesse Glick
(12/Nov/14 9:42 PM)
Labels:
1.532.3-fixed
lts
lazy
-
candidate
loading
performance
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Jesse Glick
updated JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Change By:
Jesse Glick
(12/Nov/14 9:41 PM)
Labels:
1.532.3-fixed
lazy-loading
lts-candidateperformance
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-23795) error connecting jenkins to artifactory
Suraj Biyani commented on JENKINS-23795 error connecting jenkins to artifactory @sunil Thanks. The solution provided by you worked for 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
T.-C. B. commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Hi, don't know if this may help, but we had other issues after upgrading svn-plugin. (handled somewhere here in another solved issue) we solved our problems this way (don't remember details at the moment, but that's the direction we went): svn-plugin 2.3 reworked jenkins configuration: added credentials in jenkins configuration for matching svn location (not that intuitive...) finally we added svn-credentials for native svn (svn simple!) in home of user running jenkins, on master and slave machines this solved our issues, don't know if this might help you solving yours, but I hope it gives you some point to start with This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25580) Git plugin polls incorrect branch
Nathan Gray created JENKINS-25580 Git plugin polls incorrect branch Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 12/Nov/14 10:18 PM Description: I have a job configured with "branches to build" as "origin/release/flow". The polling log shows that the git plugin is erroneously only using the last component of the branch name to poll: git ls-remote -h g...@github.mycompany.lan:org/Repo.git flow # timeout=10 This matches six branches on the server. The plugin uses the first one, which is "refs/heads/appstore/flow". The hashes never match, so the plugin triggers the build every time. As a workaround I've changed "branches to build" to "refs/heads/release/flow", but this should be fixed. Environment: Git Plugin 2.2.7, Jenkins 1.509.2 Project: Jenkins Labels: polling Priority: Major Reporter: Nathan Gray This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-25581) Fail to connect Bitbucket after a first build with Websphere Deployer Plugin, throws PKIX error.
Chun Ko
created JENKINS-25581
Fail to connect Bitbucket after a first build with Websphere Deployer Plugin, throws PKIX error.
Issue Type:
Bug
Assignee:
Unassigned
Components:
websphere-deployer-plugin
Created:
12/Nov/14 10:32 PM
Description:
Hi Gerg,
First, thanks for the plugin, it is very useful.
And just to report an issue that I am experiencing, hope you can improve this area.
I am currently using Bitbucket as my SCM, and in post-build, using your plugin to deploy the WAR to WAS.
When it runs for the first time, everything is fine.
However, after that all our jobs fail to connect to the Bitbucket, which is using HTTPS.
After some investigations from the source and the Jenkins system, the System properties (via System.getProperty()) javax.net.ssl.trustStore, javax.net.ssl.keyStore, javax.net.ssl.trustStorePassword and javax.net.ssl.keyStorePassword are set with the value that I define in the job.
These values was originally as "null" (obtains via Jenkins Script Console).
I understand from your code that you only assigned this value into a Properties instance. However, I believe the IBM library use your instance and define those values into the System level.
Workarounds:
Currently, I am applying a "Post-Build Groovy Script" after running the deployer plugin. In the script, I define the following
System.clearProperty("javax.net.ssl.trustStore");
System.clearProperty("javax.net.ssl.keyStore");
System.clearProperty("javax.net.ssl.trustStorePassword");
System.clearProperty("javax.net.ssl.keyStorePassword");
and it is working for the time being.
Hope above information can help you to define the root cause and improve the plugin.
Again, Thanks for your great work.
Project:
Jenkins
Priority:
Minor
Reporter:
Chun Ko
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25582) Installing Jenkins service the slave cannot re-connect after first system restart
Henrik Skupin created JENKINS-25582 Installing Jenkins service the slave cannot re-connect after first system restart Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Nov/14 11:01 PM Description: I tried to use the Windows Service, which can be installed via a JLNP connection, to let the slave nodes automatically connect to the master. The installation seems to have a problem with shutting down the initial connection to master. So after a system restart of the slave it is no longer able to re-connect to the master because the slave is still marked as connected. It looks like that when the initial JLNP connection was killed the slave has not properly disconnected itself. Further restarts do not show this behavior. As of now you are forced to restart Jenkins on the master machine to let the client connect again. Steps: 1. Setup Jenkins and a slave node via Java Web Start 2. Connect a Windows slave 3. Select 'File | Install as a service' 4. Wait for the service to be installed 5. Restart the slave Once the slave has been restarted, the service will try to re-connect to the master, but the connection is not allowed: Nov 12, 2014 11:11:05 PM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted connection #618 from /192.168.123.3:60703 Nov 12, 2014 11:11:05 PM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #618 with /192.168.123.3:60703 is aborted: dummy-windows is already connected to this master. Rejecting this connection. Nov 12, 2014 11:11:05 PM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #618 with /192.168.123.3:60703 is aborted: Unrecognized name: dummy-windows I see hundreds of those messages in a really quick sequence. Environment: Jenkins master (1.580.1) on Ubuntu 14.04 and Jenkins slave on Windows 7 64bit. Project: Jenkins Priority: Critical Reporter: Henrik Skupin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Jesse Glick commented on JENKINS-19728 Much needed dependency management between jobs Where it gets complicated is if you want your pipeline to behave so that if someone commits to module K, then of course K gets rebuilt retested, but also L–Z get rebuilt and retested. Or just some of those, in the transitive downstream dependencies of K. Presuming you do not want to manually code these dependencies, you need some kind of tool which can inspect your sources and figure them out. Traditionally this was make, but if you want to spread builds across multiple Jenkins slaves, then you would need to reimplement that kind of analysis in a Workflow script using some library built for the purpose (say, by scanning Maven POMs). It is a potentially large topic. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22247) Provide an extension point to define user id case sensitivity contract
Jesse Glick commented on JENKINS-22247 Provide an extension point to define user id case sensitivity contract CreativeAdmin CreativeAdmin the AD plugin does not yet use this API as far as I know. Separate issue for that 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25554) Latest P4 plugin dies with IndexOutOfBoundsException
Glen Gibb updated JENKINS-25554 Latest P4 plugin dies with IndexOutOfBoundsException Change By: Glen Gibb (12/Nov/14 11:43 PM) Priority: Critical 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25554) Latest P4 plugin dies with IndexOutOfBoundsException
Glen Gibb reopened JENKINS-25554 Latest P4 plugin dies with IndexOutOfBoundsException The problem keeps reproducing itself. I've had the problem occur at least twice since I marked the bug as Can't Reproduce. Each time telling Jenkins to reload the configuration from disk fixes the issue. I'll report back when I have more data. Change By: Glen Gibb (12/Nov/14 11:43 PM) Resolution: CannotReproduce 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Neal Storey created JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. Issue Type: Bug Assignee: Richard Lavoie Attachments: jenkinsbug.txt Components: selenium-plugin, slave-utilization Created: 13/Nov/14 1:01 AM Description: upgraded Jenkins from 1.585 to 1.589 and now I can't connect to one slave machine. I have another that is a Windows machine and it connects fine. Environment: Ubuntu server 64 bit 14.04 (master) Jenkins 1.589 Selenium 2.41 Ubuntu 14.04 (slave) selenium node Project: Jenkins Labels: jenkins selenium Priority: Minor Reporter: Neal Storey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Neal Storey commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I also updated a few plugins like Credentials and enabled Slave to Master Access Control but this made no difference This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25584) change descriptor leads to RuntimeException
robsimon created JENKINS-25584 change descriptor leads to RuntimeException Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Nov/14 1:30 AM Description: 1) be on main page of Jenkins 2) click on "edit description" 3) enter HTML code such as h2, li and a tags 4) press Submit Stack trace javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#myViewsTabBar for class hudson.model.Hudson at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:97) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at
[JIRA] [core] (JENKINS-25584) change descriptor leads to RuntimeException
robsimon commented on JENKINS-25584 change descriptor leads to RuntimeException it seems that this happens when there is not enough disk space left. clearing up the hard drive solved the issue. and the same html description worked. nevertheless, i think there should be a more graceful message stating disk is full rather than failing with a Runtime Exception This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-reviewbot] (JENKINS-25585) patching fails if the patch contains changes from more than 1 file
Sherrie Ma created JENKINS-25585 patching fails if the patch contains changes from more than 1 file Issue Type: Bug Assignee: Unassigned Components: jenkins-reviewbot, patch-parameter-plugin Created: 13/Nov/14 3:52 AM Description: We use the RBTools from Reviewboard to generate patches. When trying to integrate with Jenkins-reviewbot plugin, I found that the patching always works when the patch only contains changes from one single file; when the patch contains changes from more than one file, it throws exceptions. This is an critical issue, as majority of our patches contain changes from multiple files. Please assist. Thanks, Sherrie === Started by user mas1 EnvInject - Loading node environment variables. Building remotely on blinwv58h (BMEG_58) in workspace /space/jenkins/linux86w/dev_pc_linux86w Cleared workspace. Note: .repository direcotry in workspace (if exists) is skipped ... Using remote perforce client: dev_pc_linux86w_jks-169356631 dev_pc_linux86w $ /usr/local/bin/p4 workspace -o dev_pc_linux86w_jks-169356631 Last build changeset: 532769 dev_pc_linux86w $ /usr/local/bin/p4 counter change dev_pc_linux86w $ /usr/local/bin/p4 -s changes //dev_pc_linux86w_jks-169356631/...@532770,@532799 Sync'ing workspace to changelist 532799 (forcing sync of unchanged files). dev_pc_linux86w $ /usr/local/bin/p4 -s sync -f //dev_pc_linux86w_jks-169356631/...@532799 Sync complete, took 11030 ms Applying the diff Failed to apply patch due to: java.io.IOException: remote file operation failed: /space/jenkins/linux86w/dev_pc_linux86w/patch.diff at hudson.remoting.Channel@40453292:blinwv58h at hudson.FilePath.act(FilePath.java:913) at hudson.FilePath.act(FilePath.java:895) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue.applyPatch(ReviewboardParameterValue.java:183) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue.access$200(ReviewboardParameterValue.java:51) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ReviewboardBuildWrapper.setUp(ReviewboardParameterValue.java:227) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1740) 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: java.io.IOException: Failed to patch /space/jenkins/linux86w/dev_pc_linux86w/NW/dev/main/nsr/mm/mm_mux.c at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:250) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:240) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2483) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: com.cloudbees.diff.PatchException: Cannot apply hunk @@ 8 at com.cloudbees.diff.ContextualPatch.applyHunk(ContextualPatch.java:228) at com.cloudbees.diff.ContextualPatch.applyPatch(ContextualPatch.java:155) at com.cloudbees.diff.ContextualPatch.patch(ContextualPatch.java:108) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:246) ... 10 more FATAL: remote file operation failed: /space/jenkins/linux86w/dev_pc_linux86w/patch.diff at hudson.remoting.Channel@40453292:blinwv58h java.io.IOException: remote file operation failed: /space/jenkins/linux86w/dev_pc_linux86w/patch.diff at
[JIRA] [tfs-plugin] (JENKINS-25586) Build Failed when triggered from VisualStudio.com Web Hooks
Abe Diaz created JENKINS-25586 Build Failed when triggered from VisualStudio.com Web Hooks Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 13/Nov/14 4:14 AM Description: We have one project hosted in visualstudio.com we also have a web hook to fire a build every time a code check-in happens. When this triggers a build, the build fails with the below error. When the build is triggered manually from Jenkins it succeeds. Webhook used: HTTP POST http://ec2-IP.us-west-2.compute.amazonaws.com:8080/job/ProjectDashboard_CI/build?token= C:\Program Files (x86)\Jenkins\tfs\ServiceConnector\Properties: Getting AssemblyInfo.cs tfs $ "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\TF.exe" history $/Project/ProjectDashboard -recursive -stopafter:1 -noprompt -version2014-11-13T03:33:11Z -format:brief -server:https://user:p...@account.visualstudio.com/DefaultCollection Changeset User Date Comment - - -- 407 Abe Diaz 11/12/2014 testing jenkins FATAL: getAffectedFiles() is not implemented by this SCM java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by this SCM at hudson.scm.ChangeLogSet$Entry.getAffectedFiles(ChangeLogSet.java:242) at jenkins.plugins.slack.ActiveNotifier.getChanges(ActiveNotifier.java:87) at jenkins.plugins.slack.ActiveNotifier.started(ActiveNotifier.java:38) at jenkins.plugins.slack.SlackNotifier$SlackJobProperty.prebuild(SlackNotifier.java:203) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:799) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:795) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1.589 Windows Project: Jenkins Labels: plugin Priority: Major Reporter: Abe Diaz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25343) Dropdown Add parameter not working
Semen Pom commented on JENKINS-25343 Dropdown Add parameter not working In 1.589 it seems resolved... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes Got help on jenkins-dev: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-git-plugin] (JENKINS-25587) Work items not included in build if work item number is not mentioned in the first line of a git commit
Krishna Kishore created JENKINS-25587 Work items not included in build if work item number is not mentioned in the first line of a git commit Issue Type: Bug Assignee: Krishna Kishore Components: teamconcert-git-plugin Created: 13/Nov/14 6:26 AM Description: What steps will reproduce the problem? 1. Create a git commit with multi line comment. Mention the work item number on the second line (eg, task num) 2. Start a Jenkins job. 3. View the corresponding RTC Build Result What is the expected output? The work item section shows task num as included in build What do you see instead? Please provide screen shots if possible. There are no work items included in the build Please provide any additional relevant information below (server logs, custom project area template, etc...). Environment: Any Project: Jenkins Priority: Minor Reporter: Krishna Kishore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-git-plugin] (JENKINS-25587) Work items not included in build if work item number is not mentioned in the first line of a git commit
Krishna Kishore commented on JENKINS-25587 Work items not included in build if work item number is not mentioned in the first line of a git commit RTC workitem link: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/337573 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli resolved JENKINS-25424 as Fixed Exception when editing nodes Fixed in version 1.20 Change By: Levon Saldamli (13/Nov/14 7:16 AM) Status: InProgress 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Jennifer Hofmeister commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Thanks a lot! Actually, I upgraded Jenkins to 1.580 two days ago (because of the SVN trouble, I preferred to stick with the stable versions). And it seems that the problem is now "gone" ... or at least, in the state as described above, meaning it does occur but not recur, which seems heavenly after many many weeks of pain. Welp. Seems there is no explanation, but at least a solution! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
