[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-06-04 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-12615  
 
 
  Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 I request [~avollmer] to mark this issue as resolved, because PR has been merged.Thanks :)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.142981.1328107267000.21543.1559711400205%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-06-03 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-12615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
 I request Adam Vollmer to mark this issue as resolved, because PR has been merged. Thanks   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.142981.1328107267000.19661.1559577480192%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-06-01 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-12615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
 My Pull request : https://github.com/jenkinsci/discard-old-build-plugin/pull/10  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.142981.1328107267000.17935.1559388060179%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-05-26 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-12615  
 
 
  Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 [~jglick] In implementation, I have just added one if condition(type of flag) in LogRotator.java. Whenever value of numToKeep and daysToKeep are not blank, then according to flag(new variable declared) message will be displayed. Currently I have added only if condition and I got error. I have searched regarding this error, but I am not getting it clear. Error is of failure of JUnit tests. But I don't know why it failed.[ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in hudson.cli.PrivateKeyProviderTest[ERROR] loadKeyBroken(hudson.cli.PrivateKeyProviderTest) Time elapsed: 0.001 s <<< ERROR!java.lang.Exception: Unexpected exception, expected but was at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)Caused by: java.nio.file.NoSuchFileException: C:\Open%20Source\cli\target\test-classes\hudson\cli\openssh-broken at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.cli.PrivateKeyProvider.readPemFile(PrivateKeyProvider.java:132) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:128) at hudson.cli.PrivateKeyProviderTest.loadKeyBroken(PrivateKeyProviderTest.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 

[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-05-24 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-12615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
 Jesse Glick  In implementation, I have just added one if condition(type of flag) in LogRotator.java. Whenever value of numToKeep and daysToKeep are not blank, then according to flag(new variable declared) message will be displayed. Currently I have added only if condition and I got error. I have searched regarding this error, but I am not getting it clear. Error is of failure of JUnit tests. But I don't know why it failed. [ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in hudson.cli.PrivateKeyProviderTest [ERROR] loadKeyBroken(hudson.cli.PrivateKeyProviderTest) Time elapsed: 0.001 s <<< ERROR! java.lang.Exception: Unexpected exception, expected but was at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) Caused by: java.nio.file.NoSuchFileException: C:\Open%20Source\cli\target\test-classes\hudson\cli\openssh-broken at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.cli.PrivateKeyProvider.readPemFile(PrivateKeyProvider.java:132) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:128) at hudson.cli.PrivateKeyProviderTest.loadKeyBroken(PrivateKeyProviderTest.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at 

[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-05-15 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah assigned an issue to Nisarg Shah  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-12615  
 
 
  Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Assignee: 
 Nisarg Shah  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.142981.1328107267000.860.1557914460222%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-05-15 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-12615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
 I would like to work on this. I am assigning this issue to myself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.142981.1328107267000.857.1557914400600%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2013-01-31 Thread ever...@free.fr (JIRA)














































evernat
 commented on  JENKINS-12615


Discard Old Builds does not warn the user when no builds will be discarded















reproduced with Jenkins 1.500



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.