[JIRA] [git-plugin] (JENKINS-35356) Support for Stash Backup Client
Title: Message Title Pawel Grzegrzolka updated an issue Jenkins / JENKINS-35356 Support for Stash Backup Client Change By: Pawel Grzegrzolka Environment: Jenkins 1.625Git plugin 2.4.0Stash Notifier 1.9.0 REPO plugin 1.10.0 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] [git-plugin] (JENKINS-35356) Support for Stash Backup Client
Title: Message Title Pawel Grzegrzolka updated an issue Jenkins / JENKINS-35356 Support for Stash Backup Client Change By: Pawel Grzegrzolka Component/s: repo-plugin 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] [git-plugin] (JENKINS-35356) Support for Stash Backup Client
Title: Message Title Pawel Grzegrzolka created an issue Jenkins / JENKINS-35356 Support for Stash Backup Client Issue Type: Bug Assignee: Mark Waite Components: git-plugin, stashnotifier-plugin Created: 2016/Jun/05 8:30 AM Environment: Jenkins 1.625 Git plugin 2.4.0 Stash Notifier 1.9.0 Priority: Minor Reporter: Pawel Grzegrzolka When Stash Backup Client is running Jenkins fails with polling logs. Stash is currently unavailable: - The system is unavailable while maintenance is being performed. - Stash is unavailable while it is being backed up fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Stash is currently unavailable: - The system is unavailable while maintenance is being performed. - Stash is unavailable while it is being backed up fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. fatal: cannot obtain manifest ssh://path_to_geritt_manifest Done. Took 1 min 10 sec Changes found There is the same behavior in Bamboo:
[JIRA] [subversion-plugin] (JENKINS-28525) Subversion plugin doesn't do cleanup
Title: Message Title Pawel Grzegrzolka created an issue Jenkins / JENKINS-28525 Subversion plugin doesn't do cleanup Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 21/May/15 2:32 PM Environment: subversion-plugin: 2.5 Jenkins: 1.609 OS: Windows Server 2013 R2 Labels: plugin svn subversion Priority: Major Reporter: Pawel Grzegrzolka I had an issue quite a few time that checkout has been broken (interrupted during update, etc.) To fix it it's sufficient to do 'svn cleanup'. However subversion-plugin doesn't support it. In case of a broken checkout poll-scm triggers a new build https://repo/svn/project/trunk is at revision 3,211 (changed from 3,210) but SVN doesn't update this repository:
[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Pawel Grzegrzolka commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy It even worse, the same error occurs when subversion plugin tries to checkout in the clean workspace. org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy at 'D:\Jenkins\jobs\xxx\workspace\xxx' (format '100'). at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDbRoot.init(SVNWCDbRoot.java:104) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.parseDir(SVNWCDb.java:1967) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.parseDir(SVNWCDb.java:1829) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3360) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opReadTreeConflict(SVNWCDb.java:2775) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:72) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:51) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2485) at hudson.scm.subversion.UpdateUpdater$TaskImpl.parseSvnInfo(UpdateUpdater.java:125) at hudson.scm.subversion.UpdateUpdater$TaskImpl.getSvnCommandToUse(UpdateUpdater.java:87) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:130) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) at hudson.FilePath.act(FilePath.java:918) at hudson.FilePath.act(FilePath.java:896) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Creating a fresh checkout by svn command (1.8.10 client) directly on the host temporary solves the problem, since subversion plugin can update already created in the 1.8 sandbox. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-26880) 'Restrict where this promotion process can be run' doesn't work for new groovy process
Pawel Grzegrzolka
updated JENKINS-26880
Restrict where this promotion process can be run doesnt work for new groovy process
Change By:
Pawel Grzegrzolka
(10/Feb/15 3:09 PM)
Description:
ImusingRestrictwherethis
promotionprecess
process
canberunoptiontogetherwithExecutesystemgroovyscriptasanaction.Thescriptexecutesonthespecifichost,butwhenIcreateagroovyprocess:{noformat}cmd=(ipconfig/all).execute()cmd.consumeProcessOutput(out,err)cmd.waitFor()printlnoutprintlnerr{noformat}ThenewcreatedprocessisrunningontheJenkinshost,notontherequirednode.
Component/s:
groovy-plugin
Component/s:
promoted-builds-plugin
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-26880) 'Restrict where this promotion process can be run' doesn't work for new groovy process
Pawel Grzegrzolka updated JENKINS-26880 Restrict where this promotion process can be run doesnt work for new groovy process Change By: Pawel Grzegrzolka (10/Feb/15 3:11 PM) Environment: HudsonGroovybuilder:1.20 promotedbuildsplugin:2.17Jenkins:1.583Groovy:groovy-2.4.0-beta-2host:Windows2013R2Server This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-26880) 'Restrict where this promotion process can be run' doesn't work for new groovy process
Pawel Grzegrzolka
created JENKINS-26880
Restrict where this promotion process can be run doesnt work for new groovy process
Issue Type:
Bug
Assignee:
Unassigned
Components:
promoted-builds-plugin
Created:
10/Feb/15 2:54 PM
Description:
I'm using 'Restrict where this promotion precess can be run' option together with 'Execute system groovy script' as an action.
The script executes on the specific host, but when I create a groovy process:
cmd = ("ipconfig /all").execute()
cmd.consumeProcessOutput(out, err)
cmd.waitFor()
println out
println err
The new created process is running on the Jenkins host, not on the required node.
Environment:
promoted builds plugin: 2.17
Jenkins: 1.583
Groovy: groovy-2.4.0-beta-2
host: Windows 2013R2 Server
Project:
Jenkins
Priority:
Minor
Reporter:
Pawel Grzegrzolka
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL
Pawel Grzegrzolka created JENKINS-25619 The connection was interrupted - issue with TSL Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Nov/14 1:56 PM Description: I'm running Jenkins directly (via jetty) and have some problem with a SSL connection. I have signed Jenkins.crt certificate. I've imported it to keystore with a following command: keytool -keystore keystore -import -alias jetty -file Jenkins.crt -trustcacerts In jenkins.xml I use created keystore: --httpsKeyStore="keystore" --httpsKeyStorePassword="xxx" --httpPort=8080 --httpsPort=443 Unfortunately SSL connection doesn't work, since it works fine with http. IE shows error message 'This page can't be displayed' and Firefox complains as well 'The connection was interrupted'. Jenkins doesn't show valuable information in the jenkins.err.log file: INFO: Loaded all jobs Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac: display name [Root WebApplicationContext]; startup date [Fri Nov 14 14:36:29 CET 2014]; root of context hierarchy Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]: org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f Nov 14, 2014 2:36:29 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f: defining beans [authenticationManager]; root of factory hierarchy Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@7f02e185: display name [Root WebApplicationContext]; startup date [Fri Nov 14 14:36:29 CET 2014]; root of context hierarchy Nov 14, 2014 2:36:29 PM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba Nov 14, 2014 2:36:29 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba: defining beans [filter,legacy]; root of factory hierarchy It looks like some error with SSL in Jenkins. I've tried to investigate it a little bit, so I saw that connection is OK with TLS1: openssl s_client -connect 1.2.3.4:443 -prexit Loading 'screen' into random state - done CONNECTED(0154) 10120:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:./ssl/s23_lib.c:188: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 124 bytes --- New, (NONE), Cipher is (NONE) Compression: NONE Expansion: NONE With a DTLS1 it works fine: openssl s_client -connect 1.2.3.4:443 -dtls1 -prexit Loading 'screen' into random state - done CONNECTED(01DC) write:errno=10054 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 0 bytes --- New, (NONE), Cipher is (NONE) Compression: NONE Expansion: NONE SSL-Session: Protocol : unknown Cipher: Session-ID: Session-ID-ctx: Master-Key: Key-Arg : None Start Time: 1415973203 Timeout : 7200 (sec) Verify return code: 0 (ok) --- Environment: Jenkins: 1.583 Server: Windows Server 2013 R2 container: jetty Installed: as a service Web browser: IE10, Firefox 32.0 JAVA: Oracle JRE 1.7.0_60
[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL
Pawel Grzegrzolka
updated JENKINS-25619
The connection was interrupted - issue with TSL
Change By:
Pawel Grzegrzolka
(14/Nov/14 2:26 PM)
Description:
ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnectionisOKwithTLS1:{noformat}openssls_client-connect
1
165
.
2
114
.
3
164
.
4
100
:443-
prexit
state-bugs-debug
Loadingscreenintorandomstate-doneCONNECTED(0154)
10120
SSL_connect
:
before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:
error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:
---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten124bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE
{noformat}WithaDTLS1
itworksfine
differenterroroccurs
:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}
This message is
[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL
Pawel Grzegrzolka
updated JENKINS-25619
The connection was interrupted - issue with TSL
Change By:
Pawel Grzegrzolka
(14/Nov/14 2:27 PM)
Description:
ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnectionisOKwithTLS1:{noformat}openssls_client-connect165.114.164.100:443-state-
bugs-
debug
-prexit
Loadingscreenintorandomstate-doneCONNECTED(0154)SSL_connect:before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:
---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten108bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE
{noformat}WithaDTLS1differenterroroccurs:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}
This message is automatically generated by JIRA.
[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL
Pawel Grzegrzolka
updated JENKINS-25619
The connection was interrupted - issue with TSL
Change By:
Pawel Grzegrzolka
(14/Nov/14 2:31 PM)
Description:
ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnection
isOK
doesntwork
withTLS1:{noformat}openssls_client-connect165.114.164.100:443-state-debug-prexitLoadingscreenintorandomstate-doneCONNECTED(0154)SSL_connect:before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten108bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE{noformat}WithaDTLS1differenterroroccurs:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}
This message is automatically generated by JIRA.
[JIRA] [core] (JENKINS-25619) The connection was interrupted - issue with TSL
Pawel Grzegrzolka
updated JENKINS-25619
The connection was interrupted - issue with TSL
Change By:
Pawel Grzegrzolka
(14/Nov/14 2:32 PM)
Description:
ImrunningJenkinsdirectly(viajetty)andhavesomeproblemwithaSSLconnection.IhavesignedJenkins.crtcertificate.Iveimportedittokeystorewithafollowingcommand:{noformat}keytool-keystorekeystore-import-aliasjetty-fileJenkins.crt-trustcacerts{noformat}Injenkins.xmlIusecreatedkeystore:{noformat}--httpsKeyStore=keystore--httpsKeyStorePassword=xxx--httpPort=8080--httpsPort=443{noformat}UnfortunatelySSLconnectiondoesntwork,sinceitworksfinewithhttp.IEshowserrormessageThispagecantbedisplayedandFirefoxcomplainsaswellTheconnectionwasinterrupted.Jenkinsdoesntshowvaluableinformationinthejenkins.err.logfile:{noformat}INFO:LoadedalljobsNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@5962f7ac:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@5962f7ac]:org.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24fNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@7123f24f:definingbeans[authenticationManager];rootoffactoryhierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextprepareRefreshINFO:Refreshingorg.springframework.web.context.support.StaticWebApplicationContext@7f02e185:displayname[RootWebApplicationContext];startupdate[FriNov1414:36:29CET2014];rootofcontexthierarchyNov14,20142:36:29PMorg.springframework.web.context.support.StaticWebApplicationContextobtainFreshBeanFactoryINFO:Beanfactoryforapplicationcontext[org.springframework.web.context.support.StaticWebApplicationContext@7f02e185]:org.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0baNov14,20142:36:29PMorg.springframework.beans.factory.support.DefaultListableBeanFactorypreInstantiateSingletonsINFO:Pre-instantiatingsingletonsinorg.springframework.beans.factory.support.DefaultListableBeanFactory@1ffbb0ba:definingbeans[filter,legacy];rootoffactoryhierarchy{noformat}ItlookslikesomeerrorwithSSLinJenkins.Ivetriedtoinvestigateitalittlebit,soIsawthatconnectiondoesntworkwithTLS1:{noformat}openssls_client-connect
165
1
.
114
2
.
164
3
.
100
4
:443-state-debug-prexitLoadingscreenintorandomstate-doneCONNECTED(0154)SSL_connect:before/connectinitializationwriteto0x1f21d90[0x1f21dd8](108bytes=108(0x6C))-806a010301005100-1039.jQ..9..0010-38351600-00130a0700c08..50020-3332-2f0705008003..3..2../...0030-00800504-010080150040-120906004000-00141108..@.0050-06040080-0302008051bc7a43Q.zC0060-2310484d7a4f2172-9c4ba830#.HMzO!r.K.0SSL_connect:SSLv2/v3writeclienthelloAreadfrom0x1f21d90[0x1f27338](7bytes=0(0x0))7944:error:140790E5:SSLroutines:SSL23_WRITE:sslhandshakefailure:./ssl/s23_lib.c:188:---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten108bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONE{noformat}WithaDTLS1differenterroroccurs:{noformat}openssls_client-connect1.2.3.4:443-dtls1-prexitLoadingscreenintorandomstate-doneCONNECTED(01DC)write:errno=10054---nopeercertificateavailable---NoclientcertificateCAnamessent---SSLhandshakehasread0bytesandwritten0bytes---New,(NONE),Cipheris(NONE)Compression:NONEExpansion:NONESSL-Session:Protocol:unknownCipher:Session-ID:Session-ID-ctx:Master-Key:Key-Arg:NoneStartTime:1415973203Timeout:7200(sec)Verifyreturncode:0(ok)---{noformat}
This message is automatically generated by JIRA.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Jenkins version 1.583 OS and version Windows Server 2013 How was Jenkins installed? as a service Container and version, if not using the native installer native one What's the context path (e.g. / or /jenkins), and what's the URL that fails? http://hostname:8080/ What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Which client OS and web browser (+ versions of each)? Win 7 (IE 10 and Firefox (32)) + Windows 2013; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka edited a comment on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Jenkins version 1.583 OS and version Windows Server 2013 How was Jenkins installed? as a service Container and version, if not using the native installer native one What's the context path (e.g. / or /jenkins), and what's the URL that fails? http://hostname:8080/ What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Matrix Authorization Strategy Plugin Which client OS and web browser (+ versions of each)? Win 7 (IE 10 and Firefox (32)) + Windows 2013; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka reopened JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found I have the same issue with Jenkins 1.583. Tried with IE 10 and Firefox (32). Both have the same issue. Network setup doesn't matter since the same issue occurs on the localhost. I'm using RoleBasedAuthorizationStrategy. Change By: Pawel Grzegrzolka (03/Oct/14 9:06 AM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found I've just noticed that secured connection (SSL) doesn't have this issue. Jetty complains only when trying to connect via http. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka updated JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Change By: Pawel Grzegrzolka (03/Oct/14 11:14 AM) Attachment: system_info.docx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka updated JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Change By: Pawel Grzegrzolka (03/Oct/14 11:14 AM) Attachment: system_info.docx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found What do you mean by a container? Please find attached systeminfo. URL points to the http://hostname:8080/;jsessionid=jxe4566niq5m10476zliw7ge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka edited a comment on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found I'm using pure Jenkins service - which uses Jetty by default. Please find attached systeminfo. URL points to the http://hostname:8080/;jsessionid=jxe4566niq5m10476zliw7ge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka edited a comment on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found I'm using pure Jenkins service - which uses Jetty by default. Please find attached systeminfo. Login page is http://hostname:8080/login?from=%F, since 'log in' button points to the http://hostname:8080/;jsessionid=jxe4566niq5m10476zliw7ge (with a random crap at the end). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Pawel Grzegrzolka commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Sorry for posting in already closed issue, but it looks for me, that it hasn't been solved. I updated to the latest 2.5-beta-2 subversion plugin (and Jenkins v 1.583) but still have "-1" issue. Strange that only one external repository is affected. As you can see in the polling log, it's trigger to build a job cause plugin reads -1 revision. Started on Oct 2, 2014 10:10:00 AM Received SCM poll call on master for ProjectX on Oct 2, 2014 10:10:00 AM https://host1/svn/repo1/tags/latest is at revision 136 https://host2/svn/repo2/trunk is at revision 44 https://host2/svn/repo2/trunk/tests is at revision 974 (changed from -1) https://host1/repo3/trunk/path is at revision 83 Done. Took 1.7 sec Changes found This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Pawel Grzegrzolka edited a comment on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Sorry for posting in already closed issue, but it looks for me, that it hasn't been solved. I updated to the latest 2.5-beta-2 subversion plugin (and Jenkins v 1.583) but still have "-1" issue. Strange that only one external repository is affected. As you can see in the polling log, it's trigger to build a job cause plugin reads -1 revision. Started on Oct 2, 2014 10:10:00 AM Received SCM poll call on master for ProjectX on Oct 2, 2014 10:10:00 AM https://host1/svn/repo1/tags/latest is at revision 136 https://host2/svn/repo2/trunk is at revision 44 https://host2/svn/repo2/trunk/tests is at revision 974 (changed from -1) https://host1/repo3/trunk/path is at revision 83 Done. Took 1.7 sec Changes found All listed repositories are svn:externals. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Pawel Grzegrzolka commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Doesn't it? Tracker says something different. My issue is the same as mentioned in the JENKINS-22158, which is a duplicated of JENKINS-22199, where you asked to forward to this Jira Slightly complicated, but I hope tracker doesn't outsmart us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Pawel Grzegrzolka commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Thanks for clarification. I'm going to reopen JENKINS-22158 than. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds
Pawel Grzegrzolka reopened JENKINS-22158 Wrong parsing of revision for externals causes infinite builds It looks for me, that it hasn't been solved. I updated to the latest 2.5-beta-2 subversion plugin (and Jenkins v 1.583) but still have "-1" issue. As you can see in the polling log, it's trigger to build a job cause plugin reads -1 revision. Started on Oct 2, 2014 10:10:00 AM Received SCM poll call on master for ProjectX on Oct 2, 2014 10:10:00 AM https://host1/svn/repo1/tags/latest is at revision 136 https://host2/svn/repo2/trunk is at revision 44 https://host2/svn/repo2/trunk/tests is at revision 974 (changed from -1) https://host1/repo3/trunk/path is at revision 83 Done. Took 1.7 sec Changes found All listed repositories are svn:externals. Strange that only one external repository is affected. Change By: Pawel Grzegrzolka (02/Oct/14 9:26 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Pawel Grzegrzolka commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Here you go: hudson.util.IOException2: revision check failed on https://host/svn/repo/trunk at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1684) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/id_scpsw_bootloader/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:179) ... 11 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 29 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Pawel Grzegrzolka edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Here you go: hudson.util.IOException2: revision check failed on https://host/svn/repo/trunk at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1684) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/repo/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:179) ... 11 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 29 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Pawel Grzegrzolka commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I'm using externals. Few of them point to one host others to a different host. For each host I have separated creditation. Unfortunately mentioned workaround doesn't work for me, I still have an error: hudson.util.IOException2: revision check failed on https://host2/svn/repo/trunk at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) My job config.xml looks like that: scm class="hudson.scm.SubversionSCM" plugin="subversion@2.4" locations hudson.scm.SubversionSCM_-ModuleLocation remotehttps://hostname1/svn/repo/trunk/remote credentialsIdxxx/credentialsId local./local depthOptioninfinity/depthOption ignoreExternalsOptionfalse/ignoreExternalsOption /hudson.scm.SubversionSCM_-ModuleLocation /locations additionalCredentials hudson.scm.SubversionSCM_-AdditionalCredentials realmlt;https://hostname2:443gt; Authorization Realm/realm credentialsIdyyy/credentialsId /hudson.scm.SubversionSCM_-AdditionalCredentials hudson.scm.SubversionSCM_-AdditionalCredentials realmlt;https://hostname1:443gt; Authorization Realm/realm credentialsIdxxx/credentialsId /hudson.scm.SubversionSCM_-AdditionalCredentials /additionalCredentials ... Is it something wrong with my configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
