Jenkins credentials mysteries (always "unable to access repository" even though URL provided)

[jack]

Hello guys,

Strange mystery here... I configured a jenkins master instance on my Windows machine to fetch SVN repo codes, got all recommanded plugins installed, all system and global security configs are good, provided a couple of credentials (used another user account's name, so it's not 'admin' for the credential name), set a post-commit hook, all windows and linux slaves are operational, so far so good, everything works fine.

But since last friday I needed to setup another Jenkins master instance on our server (Linux this time), I installed jenkins remotely with command lines and installed all plugins too, when I connect to that URL:8080, I saw a new jenkins dashboard, so I thought it was all good. Istarted to add a new job, but unable to make it: when it comes to adding credentials for my SVN repo, it always gives me a "Unable to access the repository" error with no further info, even though I have created a credential as admin.

First I thought I must miss some step, so I go back to my old functionning jenkins on my Windows PC, I created a new credential as admin but this time, it also gives me "unable to access the repo" error. If I switch to previously created credentials, it will work.

Then I thought credential name may need to be the same as the current user, so I created a credential named 'admin' as admin, and another named 'user' as user, but none of those works.

I'm really confused: why would this happen???? why would it not suffice to just simply create a credential ad provide it for the repo ???? And I now have no clue how I created the first few credentials on my Windows machine for the first time...  What does these credentials even mean when creating new jobs????? They are not the same as the credentials for using SSH to connect to a linux slave as per my understanding, but why would none work ?

PS: this is the ENTIRE console log when I tried to build the new job on my new server side linux jenkins anyways:

Started by user admin
Building in workspace /var/lib/jenkins/workspace/JavaTestJob
Checking out a fresh workspace because there's no workspace at /var/lib/jenkins/workspace/JavaTestJob
Cleaning local Directory .
Checking out http://my.svn.server.url/myProjName at revision '2018-06-04T10:17:55.093 +0000' --quiet
Using sole credentials ricky/****** in realm ‘<http://my.svn.server.url:80> Subversion Repository’
Using sole credentials ricky/****** in realm ‘<http://my.svn.server.url:80> Subversion Repository’
ERROR: Subversion checkout has been canceled
Build was aborted
Finished: ABORTED

If anybody knows about credentials ... thanks a lot :'(

[jack]

Ok never mind actually I was giving wrong passwords for latest credentials XD I totally forgot the SVN repo is protected by a password lol sorry for the bother :P

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/maoxDRrcIF0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/33b25e5c-0119-4034-9f7b-847023813940%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.