Do you have multiple locations in your checkout?
On 7 February 2014 11:17, Stephen Connolly <[email protected]>wrote: > also can you take a peek at the job's config.xml and verify that the > credential's ID is being persisted... > > > On 7 February 2014 11:16, Stephen Connolly < > [email protected]> wrote: > >> do you have the full stack trace? (might be hidden in the show details >> link) >> >> >> On 7 February 2014 11:15, David Aldrich <[email protected]>wrote: >> >>> Hi Stephen >>> >>> >>> >>> I still have a problem with credentials. In the project configuration I >>> see: >>> >>> >>> >>> >>> >>> *Unable to access <my url>/trunk : svn: E200015: OPTIONS <my repo>/trunk >>> failed (show details) >>> <https://172.29.68.12/jenkins/job/TML_scheduler_regression_test_gcc/configure> >>> * >>> >>> *org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS <my >>> 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)* >>> >>> >>> >>> and credentials is set to none. I select the correct credential from >>> the drop down list, but the above error is still displayed. I save the >>> project and run it and it succeeds. Then I open the project configuration >>> again, and again I see the above error and credentials is set to none. >>> >>> >>> >>> Any thoughts please? >>> >>> >>> >>> David >>> >>> >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Stephen Connolly >>> *Sent:* 06 February 2014 16:30 >>> >>> *To:* [email protected] >>> *Subject:* Re: [ANN] Subversion Plugin 2.0 being released >>> >>> >>> >>> yeah I certainly was not expecting anything that esoteric ;-) >>> >>> >>> >>> On 6 February 2014 16:02, David Aldrich <[email protected]> >>> wrote: >>> >>> Hi Stephen >>> >>> >>> >>> Thanks, I am using the latest plugins. >>> >>> >>> >>> Our Jenkins instance uses 'user' 'hudsonuser' for svn access but we have >>> to have separate credentials for that user for linux and Windows slaves >>> (they have different passwords). The linux jobs got the correct >>> credentials but the Windows jobs lost their credentials settings. >>> Unfortunately it means we have to go through every Windows job and >>> reconfigure it. >>> >>> >>> >>> Best regards >>> >>> >>> >>> David >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Stephen Connolly >>> *Sent:* 06 February 2014 15:42 >>> >>> >>> *To:* [email protected] >>> *Subject:* Re: [ANN] Subversion Plugin 2.0 being released >>> >>> >>> >>> There was always the possibility that there was some crazy state that a >>> job could get itself into with regards to where it was sourcing its >>> credentials from (using the pre-2.0 credentials model). >>> >>> >>> >>> I was rather confident that I had covered all the crazy ways that the >>> credentials could be stashed. Your experience suggests that there are some >>> credentials that may not be being picked up. >>> >>> >>> >>> FYI I recommend using the absolute latest versions of the credentials >>> (1.9.4) and ssh-credentials (will probably be best to upgrade ssh-slaves >>> too if you upgrade ssh-credentials) plugins for the best UX. >>> >>> >>> >>> On 6 February 2014 15:08, David Aldrich <[email protected]> >>> wrote: >>> >>> Hi Stephen >>> >>> >>> >>> I upgraded to svn plugin 2.0 again. In the job configuration screen the >>> credentials drop-down read 'none' as you expected. I then selected the >>> correct credentials from the dropdown and was taken to: >>> >>> >>> >>> https://<my url>/jenkins/job/<my job>/configSubmit >>> >>> >>> >>> which was a blank screen. >>> >>> >>> >>> I then went to the Jenkins homepage and started the job. Now it's >>> checking out the working copy ok. >>> >>> >>> >>> So a bit painful, but seems to be ok now. >>> >>> >>> >>> Thanks for your help, >>> >>> >>> >>> David >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Stephen Connolly >>> *Sent:* 06 February 2014 14:26 >>> *To:* [email protected] >>> >>> >>> *Subject:* Re: [ANN] Subversion Plugin 2.0 being released >>> >>> >>> >>> If you go to the job configuration screen (when using subversion 2.0) >>> there should be a credentials drop-down under the SVN URL. if that is >>> empty, then likely the credentials for that specific job were not migrated. >>> You should be able to select the credentials, or worst case add them again. >>> >>> >>> >>> On 6 February 2014 14:08, David Aldrich <[email protected]> >>> wrote: >>> >>> How would I check that? >>> >>> >>> >>> I have just downgraded to 1.54. Now, on the configuration page of the >>> failing project, Jenkins is asking me for credentials: >>> >>> >>> >>> *[image: >>> https://172.29.68.12/jenkins/static/c1cdc5d7/images/none.gif]Unable to >>> access https://mytrunk <https://mytrunk> : svn: E200015: OPTIONS >>> /subversion/zodiac/trunk failed (show details) >>> <https://172.29.68.12/jenkins/job/Zodiac_MSVC/configure>* >>> >>> *org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS >>> /subversion/zodiac/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)* >>> >>> >>> >>> Best regards >>> >>> >>> >>> David >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Stephen Connolly >>> *Sent:* 06 February 2014 14:05 >>> *To:* [email protected] >>> *Cc:* [email protected] >>> *Subject:* Re: [ANN] Subversion Plugin 2.0 being released >>> >>> >>> >>> Did the credentials get migrated correctly? >>> >>> >>> >>> On 6 February 2014 13:55, David Aldrich <[email protected]> >>> wrote: >>> >>> Hi >>> >>> >>> >>> I have just upgraded from Subversion 1.54 plugin to v.2.00. Launching a >>> job that does a clean checkout on a Windows slave now repeatedly fails with >>> this exception: >>> >>> Checking out <https:// my trunk> at revision '2014-02-06T13:42:30.165 >>> +0000' >>> >>> ERROR: Failed to check out <https:// my trunk> >>> >>> org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS >>> /subversion/zodiac/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) >>> >>> >>> >>> Clean checkouts to a Linux slave work fine. >>> >>> >>> >>> I guess Stephen does not want to know ;-) I can raise a JIRA. >>> >>> >>> >>> Best regards >>> >>> >>> >>> David >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Stephen Connolly >>> *Sent:* 31 January 2014 12:25 >>> *To:* [email protected]; [email protected] >>> *Subject:* [ANN] Subversion Plugin 2.0 being released >>> >>> >>> >>> At the Jenkins Code Camp the issue of releasing version 2.0 of the >>> Subversion plugin came up. >>> >>> >>> >>> I would have liked to hear from some users who have tried to test the >>> 2.0-beta-1. After 3 months we have had no feedback, so: >>> >>> >>> >>> Kevin P Flemming >>> >>> Robert Sandell >>> >>> Nicolas de Loof >>> >>> Vincent Latombe >>> >>> >>> >>> all voted me down and suggest that we just go and release the 2.0 >>> version. >>> >>> >>> >>> If there are any issues with the 2.0 credential migration I suggest >>> taking it up with those who voted me down ;-) >>> >>> >>> >>> -Stephen >>> >>> -- >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> Click >>> here<https://www.mailcontrol.com/sr/g0ay+AqDqeHGX2PQPOmvUrxf8JpNKDSovBVwVYIfOz7Rtu9fPOHUjM5Vf2uwxhm53qqlWUh6KrEDs2jC!2iYuQ==>to >>> report this email as spam. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
<<image001.png>>
![https://172.29.68.12/jenkins/static/c1cdc5d7/images/none.gif]Unable](https://172.29.68.12/jenkins/static/c1cdc5d7/images/none.gif]Unable){kind=link}