[JIRA] (JENKINS-1878) Ability to move job to top of queue

2020-04-22 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-1878  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to move job to top of queue   
 

  
 
 
 
 

 
 The plugin  this  is  not working  anymore  right after installation .  The  It is needed a restart of jenkins that the  menu entry is  missing  appearing .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.131951.1213683192000.15693.1587555361734%40Atlassian.JIRA.


[JIRA] (JENKINS-1878) Ability to move job to top of queue

2020-04-21 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-1878  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to move job to top of queue   
 

  
 
 
 
 

 
 The plugin this not working anymore. The menu entry is missing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.131951.1213683192000.15038.1587496141237%40Atlassian.JIRA.


[JIRA] (JENKINS-61804) = sign in path lead to bug in msbuild

2020-04-03 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61804  
 
 
  = sign in path lead to bug in msbuild   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 matrix-project-plugin  
 
 
Created: 
 2020-04-03 13:40  
 
 
Environment: 
 Windows  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 Caused by the matrix plugin the jobname:   
 

 
 
JOB_NAME 
xxx/CONFIGURATION=Release 
 

 
   is generated. We are tried to copy the source into this path and start build, This lead to error CS0006 in msbuild 4.0 for VS2010 or CS1679 for MSbuild shipped with VS2019. Report: https://github.com/dotnet/roslyn/issues/5623 It would be nice if this = sign could be configured.  
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-56759) Unexpected executor death prevents builds

2020-03-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-56759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected executor death prevents builds   
 

  
 
 
 
 

 
 I We  got this too  today. We are using several axis. We are using no slave. We are on Windows 2012 R2 and jenkins version is 2.225 ,  all plugins are up  but we was copying a project  to  date  wrong location .  How could I support?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.198402.1553603985000.6257.1584017640160%40Atlassian.JIRA.


[JIRA] (JENKINS-56759) Unexpected executor death prevents builds

2020-03-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-56759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected executor death prevents builds   
 

  
 
 
 
 

 
 I got this too today. We are using several axis. We are using no slave. We are on Windows 2012 R2  and jenkins version is 2 . 225, all plugins are up to date.  How could I support?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.198402.1553603985000.6224.1584016320191%40Atlassian.JIRA.


[JIRA] (JENKINS-56759) Unexpected executor death prevents builds

2020-03-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-56759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected executor death prevents builds   
 

  
 
 
 
 

 
 I got this too today. We are using several axis. We are using no slave. We are on Windows 2012 R2. How could I support?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.198402.1553603985000.6219.1584015780161%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-03-04 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-60240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: XML parser crash   
 

  
 
 
 
 

 
 java_mini.dmp I attached me with visual studio then I killed the job with xUnit. The exception was raised and I created a dump. Please find it attached.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.203222.157433927.6045.1583387040129%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-03-04 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60240  
 
 
  XML parser crash   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Attachment: 
 java_mini.dmp  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.203222.157433927.6043.1583386980149%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-02-25 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-60240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: XML parser crash   
 

  
 
 
 
 

 
 Today we had a stucking unit test. We have jobs with child jobs. The Xunit is in the child job. So I stopped the main job, but it look like the child job didn't. So I clicked on kill the child job too. Then it appears that jenkins was dead. Not sure if by killing main job or child job. No error in jenkins log file. In error log I see:   Child process [3988 - H:\Jenkins\jre\bin\java -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyy -Xrs -Xmx512m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "H:\Jenkins\jenkins.war" --httpPort=8080] finished with -1073741510   The error code is in hex: 0xC13A   So I guess 13A is 314 and from this page https://docs.microsoft.com/de-de/windows/win32/debug/system-error-codes--0-499- it is:   ERROR_DISK_RESOURCES_EXHAUSTED 314 (0x13A) The physical resources of this disk have been exhausted.        
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.6799.1582699080191%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-02-10 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-60240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: XML parser crash   
 

  
 
 
 
 

 
 Since the jenkins is killing itself. I cannot provide such dump.  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.5316.1581332880193%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-02-09 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-60240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: XML parser crash   
 

  
 
 
 
 

 
 I attached the configuration screen. Since it is labled as default in combo box, I believe it comes from plugin itself.  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.5191.1581317820461%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-02-09 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60240  
 
 
  XML parser crash   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Attachment: 
 plugin config.png  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.5189.1581317700142%40Atlassian.JIRA.


[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames

2020-01-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-51285  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active Directory plugin does not work with scandic usernames   
 

  
 
 
 
 

 
 With TFS plugin and latest of all version I got this too, seems a connection issue. Our Jenkins is running on Windows Server.  I ask our IT and told me that DC was down for this time. {noformat}FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203)Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2381) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at 

[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames

2020-01-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-51285  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active Directory plugin does not work with scandic usernames   
 

  
 
 
 
 

 
 With TFS plugin and latest of all version I got this too, seems a connection issue.  Our Jenkins is running on Windows Server. {noformat}FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203)Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2381) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at 

[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames

2020-01-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-51285  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active Directory plugin does not work with scandic usernames   
 

  
 
 
 
 

 
 With TFS plugin and latest of all version I got this too, seems a connection issue.{noformat}FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is   java. util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java. net.ConnectException: Connection timed out: connect ]java.net.ConnectException: Connection timed out: connect   at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)   at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)   at java.net.Socket.connect(Socket.java:589)   at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)   at java.lang.reflect.Method.invoke(Method.java:498)   at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350)   at com.sun.jndi.ldap.Connection.(Connection.java:203)  Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]   at com.sun.jndi.ldap.Connection.(Connection.java:216)   at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)   at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615)   at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)   at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319)   at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)   at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151)   at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668)   at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599)   at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370)   at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340)   at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)   at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)   at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)  Caused: java.util.concurrent.ExecutionException   at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)   at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)   at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)   at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132)   at 

[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames

2020-01-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-51285  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active Directory plugin does not work with scandic usernames   
 

  
 
 
 
 

 
 With TFS plugin and latest of all version I got this too, seems a connection issue. 

 
FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203)Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at 

[JIRA] (JENKINS-60240) XML parser crash

2020-01-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-60240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: XML parser crash   
 

  
 
 
 
 

 
 I am not sure how it comes to this version number  mix up , we used the latest from all plugins. At time of the plugin bug report creation it was XUnit in version 2.3.6.We use the weekly version and update nearly every week. In logs I see error caused by empty XUnit result file. I guess this lead to crash. The empty files got created by a crashing or canceled test run. edit:1.12.1 is the version of th Cpp Report Type used by the XUnit plugin, I am not sure if this is something predefined or created by colleague.  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.6910.1578893520123%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-01-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-60240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: XML parser crash   
 

  
 
 
 
 

 
 I am not sure how it comes to this version number, we used the latest from all plugins. At time of the plugin bug report creation it was XUnit in version 2.3.6. We use the weekly version and update nearly every week. In logs I see error caused by empty XUnit result file. I guess this lead to crash. The empty files got created by a crashing or canceled test run.  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.6908.1578893340230%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-01-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60240  
 
 
  XML parser crash   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Environment: 
 Windows Server 2016, Weekly jenkins , running as service  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.6906.1578893220284%40Atlassian.JIRA.


[JIRA] (JENKINS-60240) XML parser crash

2020-01-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60240  
 
 
  XML parser crash   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Environment: 
 latest Windows Server 2016, Weekly jenkins  
 

  
 
 
 
 

 
 
 

 
 
 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.203222.157433927.6904.1578893220257%40Atlassian.JIRA.


[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided

2020-01-05 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60641  
 
 
  IllegalArgumentException: No script is provided   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-01-06 07:18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 After updating jenkins.war from 2.210 to 2.212 jenkins is not booting up properly. It looks like that mainly user configs of users which are not in company anymore, but also a few users which are still here.   I didn't test 2.211! error from log:   2020-01-06 06:31:41.056+ [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up2020-01-06 06:31:41.056+ [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set upjava.lang.IllegalArgumentException: No script is provided at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:130) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.createSecurityComponents(ActiveDirectorySecurityRealm.java:340) at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:487) at hudson.security.HudsonFilter.reset(HudsonFilter.java:138) at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:2590) at jenkins.model.Jenkins$16.run(Jenkins.java:3287) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1142) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)2020-01-06 06:31:41.056+ [id=18] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkinsjava.lang.IllegalArgumentException: No script is provided at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:130) at 

[JIRA] (JENKINS-60385) TF10123: The path 'xxx' contains the character ';'. Remove the ';' and try again.

2019-12-05 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60385  
 
 
  TF10123: The path 'xxx' contains the character ';'. Remove the ';' and try again.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 redsolo  
 
 
Components: 
 tfs-plugin  
 
 
Created: 
 2019-12-06 05:41  
 
 
Environment: 
 tfs-plugin 5.157.0, Azure DevOps Server 2019 17.153.29207.5 (AzureDevOps2019.Update1)  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 We have the issue that a path with semicolon could not be get.   Getting version 'C417897' to 'H:\Jenkins\workspace\xxx'... FATAL: java.lang.RuntimeException: com.microsoft.tfs.core.clients.versioncontrol.exceptions.LocalPathFormatException: TF10123: The path 'xxx\aa\bb\cc\dd\ee\ff\gg\hh\iii7 ;LLL' contains the character ';'. Remove the ';' and try again. com.microsoft.tfs.core.clients.versioncontrol.exceptions.LocalPathFormatException: TF10123: The path 'xxx\aa\bb\cc\dd\ee\ff\gg\hh\iii7 ;LLL' contains the character ';'. Remove the ';' and try again. at com.microsoft.tfs.core.clients.versioncontrol.path.LocalPath.checkLocalItem(LocalPath.java:1376) at com.microsoft.tfs.core.clients.versioncontrol.engines.internal.GetEngine.processOperation(GetEngine.java:1594) at com.microsoft.tfs.core.clients.versioncontrol.engines.internal.GetEngine.processOperationsInternal(GetEngine.java:1147) at com.microsoft.tfs.core.clients.versioncontrol.engines.internal.GetEngine.processOperations(GetEngine.java:957) at com.microsoft.tfs.core.clients.versioncontrol.engines.internal.GetEngine.processGetOperations(GetEngine.java:808) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2459) Caused: java.lang.RuntimeException at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2470) at 

[JIRA] (JENKINS-60240) crash XML parser crash

2019-11-21 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60240  
 
 
  crash XML parser crash   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nikolas Falco  
 
 
Components: 
 xunit-plugin  
 
 
Created: 
 2019-11-21 12:27  
 
 
Environment: 
 latest  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 We tried today to cancel a unit test then jenkins crashed with error. Unit test is xUnit Cpp1.12.1 plugin.   2019-11-21 11:36:46.158+ [id=5247] INFO hudson.model.Run#execute: xxx_RunUnitTest #60 main build action completed: SUCCESS2019-11-21 11:36:46.158+ [id=5247] INFO hudson.model.Run#execute: SRPFwk_Dev_RunUnitTest #60 main build action completed: SUCCESSRecoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document is invalid: no grammar found.Recoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document root element "TestRun", must match  DOCTYPE root "null".Warning   The XML parser reported two validation errors. Processing continues, because recovery from  validation errors was requested  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  

[JIRA] (JENKINS-59218) NullPointerException in logparser buildDataSet(LogParserAction.java:147)

2019-09-04 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59218  
 
 
  NullPointerException in logparser buildDataSet(LogParserAction.java:147)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Martin Reinhardt  
 
 
Components: 
 log-parser-plugin  
 
 
Created: 
 2019-09-04 07:15  
 
 
Environment: 
 Jenkins 2.193  Log Parser 2.1  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 When access http://:/job//logparser/trendMap we got error page with attached stacktrace. Jenkins was maybe in following crashed, so I was looking into log file. But when accessing the page again is jenkins not crashing anymore, not sure how it comes to the crash.   

 

2019-09-03 09:49:19.521+ [id=8] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://:/job//logparser/trendMap2019-09-03 09:49:19.521+ [id=8] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://:/job//logparser/trendMapjava.lang.NullPointerException at hudson.plugins.logparser.LogParserAction.buildDataSet(LogParserAction.java:147) at hudson.plugins.logparser.LogParserAction.doGraphMap(LogParserAction.java:123) at hudson.plugins.logparser.action.LogParserProjectAction.doTrendMap(LogParserProjectAction.java:75) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at 

[JIRA] (JENKINS-46134) duplicate warnings and errors

2019-07-02 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 please find attached the configuration, if it is caused by this.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46134  
 
 
  duplicate warnings and errors   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Resolution: 
 Cannot Reproduce  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-46134) duplicate warnings and errors

2019-07-02 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46134  
 
 
  duplicate warnings and errors   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Attachment: 
 config.png  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-46134) duplicate warnings and errors

2019-07-02 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46134  
 
 
  duplicate warnings and errors   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Attachment: 
 2019_07_03_07_21_19_Jenkins.png  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins

2019-05-10 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-55945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Got IllegalStateException while restart Jenkins
 

  
 
 
 
 

 
 I got this too today. And reverted only in plugins folder the github-branch-source.bak. But now the plugin manager does not show up the new version, strange.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54712) after update ssh-slave plugin to 1.29.0 just stacktrace in browser

2018-11-19 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54712  
 
 
  after update ssh-slave plugin to 1.29.0 just stacktrace in browser   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 ssh-slaves-plugin  
 
 
Created: 
 2018-11-20 07:17  
 
 
Environment: 
 Windows Server 2016  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 After updating all plugins it comes up that a stacktrace appear on all pages of checkins, nothing really clickable, just access by sub url. After reverting plugin for plugin it comes out it is gone after revert ssh-slaves.plugin with version 1.28.1. org.apache.commons.jelly.JellyTagException: jar:file:/H:/Jenkins/war/WEB-INF/lib/jenkins-core-2.151.jar!/lib/layout/hasPermission.jelly:35:20:  com/trilead/ssh2/crypto/Base64org.apache.commons.jelly.JellyTagException: jar:file:/H:/Jenkins/war/WEB-INF/lib/jenkins-core-2.151.jar!/lib/layout/hasPermission.jelly:35:20:  com/trilead/ssh2/crypto/Base64 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at 

[JIRA] (JENKINS-54152) restart jenkins when not runned as service

2018-10-22 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-54152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: restart jenkins when not runned as service   
 

  
 
 
 
 

 
 Sorry, but somehow after a few day test, it comes out that some functions behave different. Means "interactive" is no solution.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54152) restart jenkins when not runned as service

2018-10-19 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-54152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: restart jenkins when not runned as service   
 

  
 
 
 
 

 
 Since the "interactive" was working is the other stuff optional. Still open the UX issue that text "Restart Jenkins when installation is complete and no jobs are running" is still shown in case jenkins is not running as service. Alternative is to provide a way to restart, then showing a checkbox would make sense. see example statements  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54152) restart jenkins when not runned as service

2018-10-18 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-54152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: restart jenkins when not runned as service   
 

  
 
 
 
 

 
 I tried the "interactive" and it seems to work. The PC has disabled UAC, just for future info.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54152) restart jenkins when not runned as service

2018-10-18 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54152  
 
 
  restart jenkins when not runned as service   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-10-19 05:00  
 
 
Environment: 
 Windows Server 2012  
 
 
Labels: 
 restart service  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 We have GUI tests running which are needed a logged in user and that the jenkins instance is running under this logged in instance. Because no service is running the checkbox "Restart Jenkins when installation is complete and no jobs are running" is not available. So please remove this useless text or provide an alternative text.   Is it possible to integrate an alternative way to restart jenkins? i.e. provide a path to a batch file which will be executed to start jenkins again, when checkbox "Restart Jenkins when installation is complete and no jobs are running" is checked or assign a job which do this, question is here how shutdown can be done or would it work when a child node runs as the logged in user and jenkins it self is running as a service?  
 

  
 
 
 
 

 
 
 
   

[JIRA] (JENKINS-26004) Priority option in multijob projects

2017-02-21 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-26004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Priority option in multijob projects   
 

  
 
 
 
 

 
 Today, I had this issue, too. I have 5 build processors. It would be nice if the job start algorithm would, prefer jobs which are not a multi job, this should solve this.  
 

  
 
 
 
 

 
 
 

 
 
 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-39207) "RSS for all" shows only a few builds

2017-02-21 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert edited a comment on  JENKINS-39207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "RSS for all" shows only a few builds   
 

  
 
 
 
 

 
 We have jobs with more than 1200 build executions. There is under the link http:// ro-soft3- srv. ger here . muehlbauer comp . de org :8080/job/JobName/rssAll more than in table viewed but not all. Same for failed builds. It seems there is somewhere a break, which prefents that really all builds are shown. I looks like just the last 5 or 7 days are shown.  Please find attached anonymouse generated rssAll file: [^rssAll.txt]   
 

  
 
 
 
 

 
 
 

 
 
 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-39207) "RSS for all" shows only a few builds

2017-02-17 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-39207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "RSS for all" shows only a few builds   
 

  
 
 
 
 

 
 We have jobs with more than 1200 build executions. There is under the link http://ro-soft3-srv.ger.muehlbauer.de:8080/job/JobName/rssAll more than in table viewed but not all. Same for failed builds. It seems there is somewhere a break, which prefents that really all builds are shown. I looks like just the last 5 or 7 days are shown. Please find attached anonymouse generated rssAll file: rssAll.txt   
 

  
 
 
 
 

 
 
 

 
 
 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-39207) "RSS for all" shows only a few builds

2017-02-17 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39207  
 
 
  "RSS for all" shows only a few builds   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Attachment: 
 rssAll.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-38166) Changes link in mail is upper case, but should lower

2017-02-14 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 since update to mail plugin 1.19 it works  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38166  
 
 
  Changes link in mail is upper case, but should lower   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-38166) Changes link in mail is upper case, but should lower

2017-02-14 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-38166  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Changes link in mail is upper case, but should lower   
 

  
 
 
 
 

 
 Yes it works now. It use a complete different link with redirect in it, but it works.  
 

  
 
 
 
 

 
 
 

 
 
 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-39349) plugin manager shows no last check time in IE11

2016-12-26 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert assigned an issue to Daniel Beck  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39349  
 
 
  plugin manager shows no last check time in IE11   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Assignee: 
 Daniel Beck  
 

  
 
 
 
 

 
 
 

 
 
 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-39349) plugin manager shows no last check time in IE11

2016-12-26 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-39349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: plugin manager shows no last check time in IE11   
 

  
 
 
 
 

 
 Mh, not sure if a translate it by the jenkins translation tool from the left corner of website. Anyway the translation is on my side wrong, and it seems in original repositiory complete missing: Here the translation: Letzte Aktualisierungsprüfung: vor  {0}
 

  
 
 
 
 

 
 
 

 
 
 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-39349) plugin manager shows no last check time in IE11

2016-12-26 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 provide translation for german text in case it is not yet translated, this should solve it  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39349  
 
 
  plugin manager shows no last check time in IE11   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Resolution: 
 Cannot Reproduce  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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.

[JIRA] (JENKINS-39349) plugin manager shows no last check time in IE11

2016-12-26 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39349  
 
 
  plugin manager shows no last check time in IE11   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Attachment: 
 jenkins_localisation_tool.png  
 

  
 
 
 
 

 
 
 

 
 
 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-38166) Changes link in mail is upper case, but should lower

2016-11-27 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-38166  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Changes link in mail is upper case, but should lower   
 

  
 
 
 
 

 
 Yes, in my mail is a colon after word "Changes". So it is the possible fault.  
 

  
 
 
 
 

 
 
 

 
 
 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-39434) failed to instanciate Key (callstack inside)

2016-11-20 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39434  
 
 
  failed to instanciate Key (callstack inside)   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 

  
 
 
 
 

 
 On Jenkins startup version  since version  2.28  until now (2.33)  I get this: log from 2.33:INFO: Prepared all plugins←[33mNov 21, 2016 6:23:37 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.nuget.NugetGlobalConfiguration, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) Tried proxying org.jenkinsci.plugins.nuget.NugetGlobalConfiguration to support a circular dependency, but it is not an interface.1 errorat com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424)at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386)at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377)at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:472)at hudson.ExtensionList.load(ExtensionList.java: 350 365 )at hudson.ExtensionList.ensureLoaded(ExtensionList.java: 288 303 )at hudson.ExtensionList.getComponents(ExtensionList.java:168)at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:191)at hudson.ExtensionList.ensureLoaded(ExtensionList.java: 288 303 )at hudson.ExtensionList.iterator(ExtensionList.java:157)at hudson.model.User.load(User.java:196)at hudson.model.User.(User.java:150)at hudson.model.User.getOrCreate(User.java:458)at hudson.model.User.getById(User.java:529)at hudson.model.User.get(User.java:513)at hudson.model.User.current(User.java:497)at hudson.plugins.jobConfigHistory.PluginUtils.isUserExcluded(PluginUtils.java:136)at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:52)at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81)at hudson.model.Descriptor.save(Descriptor.java:872)at org.jenkinsci.plugins.nuget.NugetGlobalConfiguration.(NugetGlobalConfiguration.java:32)at org.jenkinsci.plugins.nuget.NugetGlobalConfiguration$$FastClassByGuice$$731d9ecd.newInstance()at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)at 

[JIRA] (JENKINS-39258) EnvInject: NullPointerException in EnvInjectAction#writeReplace()

2016-11-08 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-39258  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EnvInject: NullPointerException in EnvInjectAction#writeReplace()   
 

  
 
 
 
 

 
 I checked also the content of the envinject.jpi, and the manifest shows the version I told: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: nenashev Build-Jdk: 1.7.0_75 Extension-Name: envinject Specification-Title: The Jenkins Plugins Parent POM Project Implementation-Title: envinject Implementation-Version: 1.93.1 Plugin-Class: org.jenkinsci.plugins.envinject.EnvInjectPlugin Group-Id: org.jenkins-ci.plugins Short-Name: envinject Long-Name: Environment Injector Plugin Url: https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin Compatible-Since-Version: 1.93 Plugin-Version: 1.93.1 Hudson-Version: 1.609.3 Jenkins-Version: 1.609.3 Plugin-Dependencies: ivy:1.21;resolution:=optional,matrix-project:1.7 Plugin-Developers: Gregory Boissinot:gbois:gregory.boissi...@gmail.com ,Oleg Nenashev:oleg_nenashev:o.v.nenas...@gmail.com,Manuel Recena:rec ena:rec...@gmail.com  
 

  
 
 
 
 

 
 
 

 
 
 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-38166) Changes link in mail is upper case, but should lower

2016-11-03 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-38166  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Changes link in mail is upper case, but should lower   
 

  
 
 
 
 

 
 I guess the link is returned by line: buf.append(DisplayURLProvider.get().getRunURL(build)); https://github.com/jenkinsci/mailer-plugin/blob/master/src/main/java/hudson/tasks/MailSender.java#L252 But I annot find the implementation for the "changes" url ,except in blue ocean code, where it looks right.  
 

  
 
 
 
 

 
 
 

 
 
 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-39297) mailer plugin sends for certain jobs no unstable/failed mail

2016-11-02 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-39297  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: mailer plugin sends for certain jobs no unstable/failed mail   
 

  
 
 
 
 

 
 I was a little bit confused by "Send separate e-mails to individuals who broke the build". With make check her it was working. I was guessing that "separate" means every guy get his own mail without knowing from each other. Maybe is is word a little bit confusing here! Since also the german language (my native language) didn't help me here.  
 

  
 
 
 
 

 
 
 

 
 
 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-39434) failed to instanciate Key (callstack inside)

2016-11-02 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39434  
 
 
  failed to instanciate Key (callstack inside)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Nov/02 10:04 AM  
 
 
Environment: 
 Windows Server 2008 R2 Datacenter  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 On Jenkins startup version 2.28 I get this: WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.nuget.NugetGlobalConfiguration, annotation=[none]]; skippi ng this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying org.jenkinsci.plugins.nuget.NugetGlobalConfiguration to support a circular dependency, but it is not a n interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:472) at hudson.ExtensionList.load(ExtensionList.java:350) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:288) at hudson.ExtensionList.getComponents(ExtensionList.java:168) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:191) at 

[JIRA] (JENKINS-39349) plugin manager shows no last check time in IE11

2016-10-28 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39349  
 
 
  plugin manager shows no last check time in IE11   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 2016_10_28_13_12_10_Update_Center_Jenkins_Internet_Explorer.png  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/28 11:17 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 Please see attached screenshot, where red marked is the missing time of last update check. I also marked another glitch of TFS plugin description.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 


[JIRA] (JENKINS-39297) mailer plugin sends for certain jobs no unstable/failed mail

2016-10-27 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39297  
 
 
  mailer plugin sends for certain jobs no unstable/failed mail   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 config_email_send_works.xml, config_no_mail_send.xml  
 
 
Components: 
 mailer-plugin  
 
 
Created: 
 2016/Oct/27 6:53 AM  
 
 
Environment: 
 Server 2008 R2 Datacenter  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 I detected that the mailer is for some multi jobs not sending unstable mails. Both multi jobs have the same configuration regarding mailer. I attached both build.xml files, where I replaced all internal names with xxx,yyy,zzz,aaa, Same replacement means same text. The multi job which does not send mail, is logging out: An attempt to send an e-mail to empty list of recipients, ignored. Jenkins version is 2.27 Mailer version is 1.18 Multijob plugin is 1.22 TFS plugin version 3.2.0, since it is last version which supports TFS2005 all other installed plugins are latest  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-39258) EnvInject: NullPointerException in EnvInjectAction#writeReplace()

2016-10-26 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-39258  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EnvInject: NullPointerException in EnvInjectAction#writeReplace()   
 

  
 
 
 
 

 
 I know its weird, but jenkins ui shows that version 1.93.1 is installed of EnvInject plugin. The thing is, that I have no issue detected, this nullReferenceException comes only to my view, as I must restart jenkins after update other plugins. Because we run jenkins from batch and not as a service. I am not sure which job it is, but today runs two similiar jobs, with different paths only. BTW it is a multi job. In Multijob is EnvInjectBuilderContributionAction serveral times:   1 xxx-MASTER . $/xxx http://xxx/ true   526924 $/xxx 
 

  
 
 
 
 

 
 
 

 
 
 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-39258) nullreferenceException

2016-10-25 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39258  
 
 
  nullreferenceException   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 envinject-plugin  
 
 
Created: 
 2016/Oct/26 5:55 AM  
 
 
Environment: 
 Windows Server 2008 R2 Datacenter  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 I use Jenkins 2.27 with latest plugin of EnvInject.  at hudson.model.Run.getRootDir(Run.java:1014) at org.jenkinsci.lib.envinject.EnvInjectAction.writeReplace(EnvInjectAction.java:98) at sun.reflect.GeneratedMethodAccessor369.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:141) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at 

[JIRA] (JENKINS-39207) "RSS for all" shows only a few builds

2016-10-24 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39207  
 
 
  "RSS for all" shows only a few builds   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/24 7:19 AM  
 
 
Environment: 
 Server 2008 R2 Datacenter  
 
 
Labels: 
 RSS all build history  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 The build history has the link "RSS for all" on bottom. When you click it it shows only the builds of the visible list. This is not "all". In case you scroll down in this list with the arrows buttons, it is the same list on "RSS for all" so it shows always the same.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-38770) "RSS for all" shows only a few builds

2016-10-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38770  
 
 
  "RSS for all" shows only a few builds   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Summary: 
 Not "RSS for  all " shows only a few  builds  show in the build history dashboard on job  
 

  
 
 
 
 

 
 
 

 
 
 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-38770) Not all builds show in the build history dashboard on job

2016-10-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-38770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not all builds show in the build history dashboard on job   
 

  
 
 
 
 

 
 Ok, this is new for me. And works. Anyway the link "RSS for all" on bottom is only show the first page! This is a bug.  
 

  
 
 
 
 

 
 
 

 
 
 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-38770) Not all builds show in the build history dashboard on job

2016-10-06 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38770  
 
 
  Not all builds show in the build history dashboard on job   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 build_history_goes_only_until_360_in_past.png, but_manual_url_edit_shows_that_older_builds_exists.png, installedplugs.txt  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/06 6:26 AM  
 
 
Environment: 
  Windows Server 2008 R2 Datacenter  
 
 
Labels: 
 build history hidden  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 All of the builds that are present on disk do not show up in the 'Build History' in the latest jenkins version 2.24. Also the RSS feeds have this problem too! Please see attached pictures, where manual is accessed an older build. In case you need some sort of logs, please describe where and how to get.  
 

  
 
 
 
 

 
 
 


[JIRA] (JENKINS-30478) "(updates available)" should to supressable

2016-09-30 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30478  
 
 
  "(updates available)" should to supressable   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 

  
 
 
 
 

 
 In case Jenkins find an update, you will get on "Manage Jenkins" overview a red text "(updates available)". In our case is since last TFS plugin update the case, which did not support our TFS Server 2005 anymore. This means for me we see all the time the red hint text. I wanna suppress this red update help for this TFS plugin. It should be enough to suppress only the version which was found by last plugin list update, this means in case the TFS plugin get an update you have to declare it again. Because maybe is in future a workaround for it there. Edit:A textbox for adding information why it was supressed would appreciated here too.  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-38130) JENKINS_HOME is set different on trigger manual build

2016-09-29 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-38130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JENKINS_HOME is set different on trigger manual build   
 

  
 
 
 
 

 
 Yes it is. Yesterday there was an update of it, maybe solved it.  
 

  
 
 
 
 

 
 
 

 
 
 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-38130) JENKINS_HOME is set different on trigger manual build

2016-09-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different on trigger manual build   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 

  
 
 
 
 

 
 I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0.On manual run is it:H:\JenkinsOn automatical run is it:H:\Jenkins\In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one.edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering.edit2: now I have 2.23 installed and found that a new created matrix job (previous was not a matrix job) was success first today and after a SCM change  notnow the correct one:for manual build:HUDSON_HOME=H:\JenkinsJENKINS_HOME=H:\Jenkins\for automatic build:HUDSON_HOME=H:\JenkinsJENKINS_HOME=H:\Jenkinsmy SCM trigger is tfs plugin version 3.2.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 

[JIRA] (JENKINS-38130) JENKINS_HOME is set different during jenkins run

2016-09-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different during jenkins run   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 

  
 
 
 
 

 
 I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0.On manual run is it:H:\JenkinsOn automatical run is it:H:\Jenkins\In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one.edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. edit2: now I have 2.23 installed and found that a new created matrix job (previous was not a matrix job) was success first today and after a SCM change  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-38130) JENKINS_HOME is set different on trigger manual build

2016-09-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different on trigger manual build   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Summary: 
 JENKINS_HOME is set different  during jenkins run  on trigger manual build  
 

  
 
 
 
 

 
 
 

 
 
 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-38130) JENKINS_HOME is set different during jenkins run

2016-09-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different during jenkins run   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Summary: 
 JENKINS_HOME is set different  for manual build  during jenkins run  
 

  
 
 
 
 

 
 
 

 
 
 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-38182) build cancel cross in build state is drawn outside of

2016-09-13 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38182  
 
 
  build cancel cross in build state is drawn outside of
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Build Executor Status.png  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/14 4:50 AM  
 
 
Environment: 
 internet explorer 11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 see attached picture from internet explorer 11. In Firefox is the text wrapped.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-38166) Changes link in mail is upper case, but should lower

2016-09-13 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38166  
 
 
  Changes link in mail is upper case, but should lower   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 mailer-plugin  
 
 
Created: 
 2016/Sep/13 1:02 PM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 Since Jenkins 2.22 or near of this version is the link in mail on job fail wrong wrong link: http://jenkinssrv/job/Dev_Build/526/Changes correct link: http://jenkinssrv/job/Dev_Build/526/changes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-38154) cpu load since 2.22

2016-09-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38154  
 
 
  cpu load since 2.22   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins_log.txt  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/13 5:02 AM  
 
 
Environment: 
 Windows Server 2008 R2  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 Since today ( yesterday was update), I see that java.exe is running with 100% cpu load. Maybe is it related to Jenkins version 2.22. I was currently updating the JENKINSHOME with a trailing backslash in every job. On save comes probably this:  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[JIRA] (JENKINS-38130) JENKINS_HOME is set different for manual build

2016-09-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different for manual build   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 

  
 
 
 
 

 
 I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0.On manual run is it:H:\JenkinsOn automatical run is it:H:\Jenkins\In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering.  
 

  
 
 
 
 

 
 
 

 
 
 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-38130) JENKINS_HOME is set different for manual build

2016-09-12 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38130  
 
 
  JENKINS_HOME is set different for manual build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/12 9:48 AM  
 
 
Environment: 
 Windows 2008 R2  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronny Borchert  
 

  
 
 
 
 

 
 I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
   

[JIRA] (JENKINS-30489) msbuild configuration need full path with including msbuild.exe but website shows warning

2016-08-08 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 update to latest version brings only different text, but warning persists: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some agents)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-30489  
 
 
  msbuild configuration need full path with including msbuild.exe but website shows warning   
 

  
 
 
 
 

 
Change By: 
 Ronny Borchert  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-30489) msbuild configuration need full path with including msbuild.exe but website shows warning

2016-08-08 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-30489  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: msbuild configuration need full path with including msbuild.exe but website shows warning   
 

  
 
 
 
 

 
 I update today to jenkins 2.17 and latest msbuild 2.16 version. Same error only little text change: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some agents)  
 

  
 
 
 
 

 
 
 

 
 
 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-28083) MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.

2016-08-08 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronny Borchert commented on  JENKINS-28083  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.   
 

  
 
 
 
 

 
 I have same problem and reported this to connect.microsoft.com, I got yet no solution. I provided them a pdb file of here msbuild. So maybe is it fixed in a later release/update.  
 

  
 
 
 
 

 
 
 

 
 
 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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2016-02-25 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 
 
A "compatibility matrix" would be fine. Because the "partial work" term in above the table is total confusing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2016-02-24 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 
 
Ok, then do please change the readme.md file that TFS 2005 Server is not working! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [mailer-plugin] (JENKINS-30838) follow up building doesn't send mails on fail to the email address of triggered job

2015-10-08 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30838 
 
 
 
  follow up building doesn't send mails on fail to the email address of triggered job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 mailer-plugin 
 
 
 

Created:
 

 08/Oct/15 8:03 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
We have splitted our project building into a build job and a test job. In case the build job is success, this job triggers the test job. Now is the problem, in case the test job fail, should be guy which breaks it in the build job get an email. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
   

[JIRA] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2015-09-29 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert edited a comment on  JENKINS-30479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 
 The support would be simple by using the old code as fallback strategy. I reported this only, be sure the author is knowing which impact the change in 4.0.0 has. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2015-09-29 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 
 
The support would be simple by using the old code as fallback strategy. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2015-09-29 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 
 
I would say if the TFS client install is missing you get an error, so I see not why. Which problems are solved by moving from tf.exe to TFS SDK? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [tfs-plugin] (JENKINS-30625) more SCM polling activities scheduled than handled

2015-09-23 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30625 
 
 
 
  more SCM polling activities scheduled than handled  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 redsolo 
 
 
 

Components:
 

 tfs-plugin 
 
 
 

Created:
 

 24/Sep/15 5:41 AM 
 
 
 

Environment:
 

 Windows Server 2008 R2 
 
 
 

Labels:
 

 tfs polling 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
We got today the first the the message of: There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands 
in "Manage Jenkins" overview. 
We use the tfs-plugin 3.2.0, because the latest 4.0.0 doesn't support our TFS Server 2005. 
Any suggestions? I cannot provide a jenkins log, because it hold only 30 minutes, maybe cause by regulary occuring DNS errors. Maybe anybody can give me a hint how I could improve logging on my side. 
 
 
 
 

[JIRA] [core] (JENKINS-30480) documentation of any change in build configuration

2015-09-22 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: documentation of any change in build configuration  
 
 
 
 
 
 
 
 
 
 
I installed the plugin, and will try it. thx for this information 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30480) documentation of any change in build configuration

2015-09-21 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: documentation of any change in build configuration  
 
 
 
 
 
 
 
 
 
 
I use now the line: copy %JENKINS_HOME%jobs%JOB_NAME%\config.xml %JENKINS_HOME%\jobs%JOB_NAME%\builds%BUILD_NUMBER%\ 
but you have no ability to reactivate or view it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [msbuild-plugin] (JENKINS-30489) msbuild configuration need full path with including msbuild.exe but website shows warning

2015-09-18 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30489 
 
 
 
  msbuild configuration need full path with including msbuild.exe but website shows warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ronny Borchert 
 
 
 

Summary:
 
 msbuild configuration need full  paht  path  with including msbuild.exe but website shows warning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [msbuild-plugin] (JENKINS-30489) msbuild configuration need full paht with including msbuild.exe but website shows warning

2015-09-16 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30489 
 
 
 
  msbuild configuration need full paht with including msbuild.exe but website shows warning  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 kdsweeney 
 
 
 

Attachments:
 

 2015-09-16 14_32_50-Configure System [Jenkins].png 
 
 
 

Components:
 

 msbuild-plugin 
 
 
 

Created:
 

 16/Sep/15 12:38 PM 
 
 
 

Environment:
 

 windows machine with build tools VS2013 or VS2015 
 
 
 

Labels:
 

 msbuild msbuild.exe 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
When you setup msbuild path on "Manage Jenkins" -> "Configure System" with only path. The build will fail, because msbuild.exe is missing in cmd line. When we configure it with complete path, like on screenshot, build works, but the configuration website shows a warning, that we must 

[JIRA] [core] (JENKINS-30478) "(updates available)" should to supressable

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30478 
 
 
 
  "(updates available)" should to supressable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 16/Sep/15 4:41 AM 
 
 
 

Environment:
 

 all 
 
 
 

Labels:
 

 supress update TFS updateCenter 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
In case Jenkins find an update, you will get on "Manage Jenkins" overview a red text "(updates available)". In our case is since last TFS plugin update the case, which did not support our TFS Server 2005 anymore. This means for me we see all the time the red hint text. I wanna suppress this red update help for this TFS plugin. It should be enough to suppress only the version which was found by last plugin list update, this means in case the TFS plugin get an update you have to declare it again. Because maybe is in future a workaround for it there. 
 
 
 
 
  

[JIRA] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30479 
 
 
 
  TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 redsolo 
 
 
 

Components:
 

 tfs-plugin 
 
 
 

Created:
 

 16/Sep/15 4:47 AM 
 
 
 

Environment:
 

 environments with TFS 2005 
 
 
 

Labels:
 

 TFS Server 2005 2008 release notes change log 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
Since version 4.0.0 is the TFS plugin not supporting TFS Server 2005 (and probably TFS Server 2008) anymore. It would be nice to say the drop of support in changelog on website https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin 
Also would it be good, to have support for it in the current plugin, to get improvments. This could be done by separate the logics into new and old TFS implementation. 
 
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-30481) jobs folder should be moveable for easy backup

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30481 
 
 
 
  jobs folder should be moveable for easy backup  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 16/Sep/15 5:03 AM 
 
 
 

Environment:
 

 all 
 
 
 

Labels:
 

 jobs backup 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
We had the problem that our server is splitted into 3 partitions. First one is Os, Second, the installed programs, Third. the data partitiion. This means that partition three is more often backuped than the other two. To reduce the amount to backup it would be good to separated jobs folder from the jenkins home folder. 
When I am right the change would be in: https://github.com/jenkinsci/jenkins/blob/5e9492d1229921d0c1701d880650671fddd6cbfd/core/src/main/java/jenkins/model/Jenkins.java 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-30480) documentation of any change in build configuration

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30480 
 
 
 
  documentation of any change in build configuration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 16/Sep/15 4:53 AM 
 
 
 

Environment:
 

 all 
 
 
 

Labels:
 

 build documentation EN ISO 9001 configuration 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ronny Borchert 
 
 
 
 
 
 
 
 
 
 
In our case, we want to know every change. Because if you change the build config, you can not back to an older version of build configuration. This would it make easier to understand why older build are failed. This would allow to move back to an older build configuration. I am not sure, but this could also be good for a "EN ISO 9001" certification. 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-30480) documentation of any change in build configuration

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30480 
 
 
 
  documentation of any change in build configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ronny Borchert 
 
 
 

Labels:
 
 9001  EN  ISO build configuration documentation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-30478) "(updates available)" should to supressable

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30478 
 
 
 
  "(updates available)" should to supressable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ronny Borchert 
 
 
 

Labels:
 
 TFS  supress  suppress  update updateCenter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2015-09-15 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30479 
 
 
 
  TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ronny Borchert 
 
 
 

Labels:
 
 2005 2008 Server TFS change log notes release  scm 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.