on jenkins server, have project checks source code out of svn , runs build script called makeinstaller.ps1 got checked out along source code. it's pretty straight-forward , part working great.
what's not working great part of makeinstaller.ps1 attempts svn export of specific revision of other source code, doesn't have credentials connect svn. when run build-scripts on pc totally fine, because tortoise svn has credentials cached.
jenkins has svn credentials already, that's used when jenkins checks out source code, not when build script attempts check out source code.
i've tried:
- installing tortoise svn command-line tools on machine that's running jenkins. fixed initial "svn.exe not found" error, has no way of knowing credentials server
- i logged svn server using tortoise svn on machine attempt cache credentials, it's still not working. i'm guessing it's because jenkins service not run under same user logged in as.
i feel i'm getting off on wrong path though. seems bit odd have tortoise svn installed on machine along side whatever svn client jenkins svn plug-in using.
my question: there way svn export inside build-script in jenkins , have use credentials jenkins knows about? can use same svn.exe jenkins svn plug-in using? don't want include credentials in build script itself.
most of similar questions found involved initial check-out failing due bad credentials, not check-out happens part of build script.
in end, ended doing jenkins: access global passwords in powershell
i had use envinject because credentials binding plugin giving me error when tried save project. involved adding instance of svn password jenkins, , hardcoding jenkins user name build script, it's working.
now build script attempts authenticate dummy svn info command. if i'm running script on local machine, works , proceeds without user-name or password. if dummy svn info command fails, attempts log in --username jenkins , --password $env:svnpassword svnpassword environment variable provided envinject.
