Re: workspace cleanup plugin 0.2.1: Cannot delete workspace
Sort of a work around: 1.Uncheck the workspace cleanup 2.Save the changes 3.Check the workspace cleanup back 4.Save the changes On Monday, July 7, 2014 9:47:53 AM UTC+3, jv wrote: So I filed an issue: https://issues.jenkins-ci.org/browse/JENKINS-23693 Am 06.07.2014 23:31, schrieb felix: I have exactly the same problem On 2014-07-01 14:25, jv wrote: *Hi, since I updated Jenkins from 1.567 to 1.570 and Workspace Cleanup Plugin from 0.20 to 0.21, all jobs using workspace cleanup are failing: 00:00:06.943* Cannot delete workspace: java.io.IOException: Cannot run program /home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts: java.io.IOException: error=13, Permission denied*00:00:06.945* ERROR: Cannot delete workspace: java.io.IOException: Cannot run program /home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts: java.io.IOException: error=13, Permission denied I have checked the workspace, everything looks ok, file permissions are all correct. Downgrade the plugin back to 0.20 fixed the problem. Is anyone facing the same problem? Thanks jv -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Multyjob build hanging everytime
Hello, Do you happen to run concurrent builds of this multijob or use the email plugin ? Because it reminds me of a bug that is driving me crazy JENKINS-9913 https://issues.jenkins-ci.org/browse/JENKINS-9913 . AAA. On Friday, November 1, 2013 10:43:40 AM UTC+2, Adrian Mitev wrote: Hi all! I setup a multyjob project and i have created a few steps. When starting a build the first step gets started but the entire build hangs on the first job (even if i see that it has ended when opening the job itself). Is there a way to fix that? Is this a known issue? Jenkins ver. 1.485 Multyjob plugin 1.9 -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Read only Configuration plugin
Hello, You are not the only one. I have submitted the issue to JIRA yesterday. Here is the link : https://issues.jenkins-ci.org/browse/JENKINS-18623 Meanwhile i have switched to using the Extended Read Permision pluggin : https://wiki.jenkins-ci.org/display/JENKINS/Extended+Read+Permission+Plugin It does prety much the same thing except that all the input fields and controls are not disabled. It might be confusing but it is still safe to use since you cannot actually save the changes. Regards, AAA. On Friday, July 5, 2013 8:25:50 PM UTC+3, Rahul k a wrote: Hello, We are using Jenkins Read only configuration plugin in Jenkins v1.518 and seems to be working fine. But when upgraded to v1.519 and v1.521, the plugin seems to be giving below error. Could anyone please help with this issue. Thanks, Rahul java.lang.NullPointerException at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.jenkinsci.plugins.readonly.JobConfiguration.transformToReadOnly(JobConfiguration.java:113) at org.jenkinsci.plugins.readonly.JobConfiguration.doIndex(JobConfiguration.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:156) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) 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:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) 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.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:124) 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
Re: Upgrade to Latest Jenkins - WSOD after running job
Hello, I found a kind of workaround. If I use the rebuild option offered by the rebuilder plugin https://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin it works just fine. AAA. On Thursday, June 20, 2013 12:10:06 PM UTC+3, Garry Welding wrote: Yeah, I'm having exactly the same issue. I have Jenkins running on Ubuntu 12.04, any kind of parameterised build job starts running fine, but I get a white screen rather than a redirect to the job. Annoying but ignorable, for now. On Tuesday, June 18, 2013 10:49:58 PM UTC+1, Jared Griffith wrote: I recently upgraded to the latest Jenkins. When I go to build any job, instead of directing me to the normal page output page, it just WSOD (white screen of death). Is anyone else experiencing this? There is also no information in the logs as to what is happening. This is happening both when going directly to the application and going via the apache proxy connection. -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 http://www.picsauditing.com 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! https://twitter.com/PICSAuditingLLC -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Perforce plugin- What is te log entry mean
Hello, First a little bit of context on perforce tickets: once a user does a p4 loginhttp://www.perforce.com/perforce/doc.current/manuals/cmdref/login.html a ticket is issued to his machine that allows him to run perforce commands without logging in again. The tickets have a lifespan of 12h hours by default (the value can be changed by a perforce admin). Once the ticket expires the user will need to run p4 loginhttp://www.perforce.com/perforce/doc.current/manuals/cmdref/login.html again in order to be able to issue perforce commands. The tickets that exist on a machine can be displayed by using p4 ticketshttp://www.perforce.com/perforce/doc.current/manuals/cmdref/tickets.html. The tickets can be deleted by using p4 logouthttp://www.perforce.com/perforce/doc.current/manuals/cmdref/logout.html Back to your warning, it can be explained as: the perforce plugin tried to run p4 login when a valid ticket was already available on the machine. There is nothing wrong in doing that. It's just that it is not actually necessary. Personally I would just ignore the warning. To get rid of them you could play around a bit with a couple of things: 1. Issue a p4 logout command at the end of your job so that when the job runs again there will be no ticket on the machine 2. Ask your perforce administrator to change the ticket lifetime of the user to something very low (1 second) Good luck, AAA. PS: you can use p4 login -s to see if you have a valid ticket or the ticket has expired. On Wednesday, June 12, 2013 10:52:24 PM UTC+3, Richard J wrote: Hi Using Jenkins 1.509.1 with Perforce plugin 1.3.19 I've seen this for a long time, but now seems like a good time to ask... My Jenkins log is full of entries like this: Jun 12, 2013 12:39:21 PM com.tek42.perforce.parse.AbstractPerforceTemplate login WARNING: Using p4 issued ticket. What does it mean, why is it a warning, and most importantly, Is there any way to suppress them? By the way, in the screen- Manage Jenkins = System Log = All Jenkins Logs click the RSS link WARNING at the bottom right corner. The page displayed is labeled Hudson log. Shall I notify Larry?:) Richard Otter -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
