Are there any plugins available which will commit the build artifact back to SVN?
相关问题
- How can I set the SVN password with Emacs 23.1 bui
- If statements in .htaccess files, to enable passwo
- 2 instances of Sonar on same machine
- SVN+SSH checkout over VPN using tortoise SVN, Smar
- Mercurial compared to private branches in SVN
相关文章
- Best way to manage docker containers with supervis
- Build errors of missing packages in Visual Studio
- Is there a version control system abstraction for
- Intermittent “SVNException: svn: E175002: Connecti
- IntelliJ Subversion Authentication Required Dialog
- Jenkins Pipeline having “Multiple candidate revisi
- TortoiseHG and hgsubversion (Windows): “no module
- Incompatible JavaHl library loaded
Unfortunately Svn Publisher is not really finished and requires quite a bit more work before I can use it in anger.
I've found I can do what I need with a shell/cmd script executed as a build action (or of course post-build would work), although it's not really ideal. The script just uses standard svn command line functions and looks something like:
So, we create the new folder for the build artifacts in Subversion, check it out to a local (in-workspace) folder, copy what we want in,
svn add
those items then commit everything back.Personally, I am still not sold on the benefit of having build reports in Subversion, but we need to have persistent storage of this information -- the Jenkins server isn't a good repository for it.
Writing a custom plugin or actually fixing Svn Publisher would be a better solution long term.
I believe the svn publisher will meet your needs.