You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a continuous integration standpoint, it would be beneficial to have the username and password be configurable for when the SVN commit occurs. If SVN credential caching is turned on and a Jenkins job encounters the svn bump step, it will fail or stall while it asks the user for a password (which, of course, they'll never know of).
It looks like grunt-svn-tag has a configuration option for username and password. So something similar with this project would be great.
The text was updated successfully, but these errors were encountered:
From a continuous integration standpoint, it would be beneficial to have the username and password be configurable for when the SVN commit occurs. If SVN credential caching is turned on and a Jenkins job encounters the svn bump step, it will fail or stall while it asks the user for a password (which, of course, they'll never know of).
It looks like grunt-svn-tag has a configuration option for username and password. So something similar with this project would be great.
The text was updated successfully, but these errors were encountered: