[JIRA] (JENKINS-18866) Symlink prevens backup from ThinBackup

2019-10-31 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W commented on  JENKINS-18866  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Symlink prevens backup from ThinBackup
 

  
 
 
 
 

 
 Hi, I have the same issue that Piotr Krukowiecki described. All of our backups are corrupt due to errors like this: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'E:\JBackup'. java.io.IOException: Failed to list contents of E:\Jenkins\jobs\Experiments\jobs\Company\jobs\RollingBuildRerun\jobs\Rerun_Rolling_Build_param\lastSuccessful   This also causes that the moving of old backups to ZIP files is not performed.   I'm setting this bug to Blocker as the plugin is simply not usable if it does not create a backup.   System data: Windows Server 2008 R2 SP1 Jenkins version 2.195 ThinBackup Plugin version 1.9      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150313.1374492663000.6062.1572526140209%40Atlassian.JIRA.


[JIRA] (JENKINS-18866) Symlink prevens backup from ThinBackup

2019-10-31 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-18866  
 
 
  Symlink prevens backup from ThinBackup
 

  
 
 
 
 

 
Change By: 
 Helene W  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150313.1374492663000.6056.1572525780506%40Atlassian.JIRA.


[JIRA] (JENKINS-40143) Duplicate email with Extended E-mail Notification

2017-03-06 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W commented on  JENKINS-40143  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duplicate email with Extended E-mail Notification   
 

  
 
 
 
 

 
 Yes, they were configured the same way. In the job xml the post build action with the email stuff is exactly the same. Even when I delete the post build action from the (old) job, save it an add it again, emails are sent double.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40143) Duplicate email with Extended E-mail Notification

2017-03-06 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W commented on  JENKINS-40143  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duplicate email with Extended E-mail Notification   
 

  
 
 
 
 

 
 Hi, I have the same issue. I discovered, that it appears only on "old" jobs, which were created before I upgraded Jenkins and email-ext-plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-3207) Allow check out of specific revision from Subversion via REVISION parameter

2016-09-20 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W commented on  JENKINS-3207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow check out of specific revision from Subversion via REVISION parameter   
 

  
 
 
 
 

 
 I have the same problem as Sven Keller. When I add @$ {REVISION}  at the end of the SVN url, than I don't see the revisions ("/trunk@$REVISION doesn't exist in the repository")  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37411) "Cancel" job in "Project roles" does not take effect as supposed

2016-08-15 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37411  
 
 
  "Cancel" job in "Project roles" does not take effect as supposed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 role-strategy-plugin  
 
 
Created: 
 2016/Aug/15 1:43 PM  
 
 
Environment: 
 Win 7  Jenkins v. 2.13   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Helene W  
 

  
 
 
 
 

 
 Hi, I want to give the user the permission to start (build) jobs but not to cancel them. When the checkbox "build" is checked users are allowed to start and cancel jobs even when the checkbox "cancel" is not checked. Please separate the build/cancel functionality completely.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-35906) Exception saving jobs using ClearCase after update to Jenkins Core 2.9

2016-06-21 Thread weiss.hel...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Helene W updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35906  
 
 
  Exception saving jobs using ClearCase after update to Jenkins Core 2.9   
 

  
 
 
 
 

 
Change By: 
 Helene W  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] [email-ext-plugin] (JENKINS-33717) NullPointerException when submitting for watching a job

2016-03-22 Thread weiss.hel...@web.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Helene W updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33717 
 
 
 
  NullPointerException when submitting for watching a job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Helene W 
 
 
 
 
 
 
 
 
 
 I get an exception when I try to watch a job.It happens with email-ext-plugin version 2.41.2 and 2.41.3. When I install version 2. 41.0 40  it works fine.javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) 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:134) at org.jenkinsci.plugins.modernstatus.ModernStatusFilter.doFilter(ModernStatusFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:131) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:125) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 

[JIRA] [email-ext-plugin] (JENKINS-33717) NullPointerException when submitting for watching a job

2016-03-22 Thread weiss.hel...@web.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Helene W created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33717 
 
 
 
  NullPointerException when submitting for watching a job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Alex Earl 
 
 
 

Components:
 

 email-ext-plugin 
 
 
 

Created:
 

 2016/Mar/22 8:17 AM 
 
 
 

Environment:
 

 Jenkins version: 1.654  Windows 7 64bit SP1  Firefox 38.7.1  
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Helene W 
 
 
 
 
 
 
 
 
 
 
I get an exception when I try to watch a job. It happens with email-ext-plugin version 2.41.2 and 2.41.3.  When I install version 2.41.0 it works fine. 
javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at