Step 1
Set the web directory as the working directory
"D:Program Files (x86)VisualSVN Serverbinsvn.exe" upgrade "D:yiyun_wwwtest" --quiet --username chiyj --password chiyj
Execute under DOS.
The second step is to modify the file
Create a new file under D:yiyun_codetesthooks
post-commit.bat content is as follows
@echo off
SET REPOS=%1
SET USER=%2
SET SVN="D:Program Files (x86)VisualSVN Serverbinsvn.exe"
SET DIR="D: yiyun_wwwtest"
(call %SVN% update %DIR% --username chiyj --password chiyj --non-interactive)
Reference http://www.cnblogs.com/xiezhengcai/archive/2013/11/27/3445457.html
Modify the hook program post-commit on the server and export the folder specifying the content to be published to the tomcat directory.
The hook program post-commit is automatically executed after the commit operation. Executed, so that an export operation is automatically performed after each commit, and the content of the tomcat folder is kept to be the content to be published
------------------- -------------------------------------------------- ------
Supplement:
For example, the svn access address of your repository is 10.30.11.12:8080/svn/project1, and you want to publish the /trunk/web folder under this repository to tomcat On, the folder address published to tomcat is d:/tomcat/opt/web, the svn administrator username is abc, and the password is 12345, then the hook program should be:
svn export 10.30.11.12:8080/ svn/project1/trunk/web d:/tomcat/opt/web --force --username abc --password 12345 --no-auth-cache
(I am not familiar with Linux, this line of instruction is as follows If there is any inconsistency with Linux syntax, please refer to the principle and modify it yourself)
Note:
1. --force means to force overwrite the d:/tomcat/opt/web folder to prevent this folder from being empty. An error is reported
2. --username abc --password 12345 automatically passes the username and password as parameters
3. --no-auth-cache means not to cache the username and password. This is for security reasons Consider
4. svn export exports the content of the specified url to the specified folder. The reason why we use export instead of update here is because update will generate a hidden .svn folder, which we don’t need
Of course, if there is a lot of content to publish, it is recommended to use it Update instead of export, because update only updates the changed parts, while export will re-export all content, and the network consumption is larger than update.
synchronous? The poster's description of the problem is not very clear. If you are uploading the entire project to the svn repository, go to the community and watch the relevant operation videos.
scmeye is currently the most active software configuration management community in China. Welcome to communicate in the community.
Skyline is a management tool developed by scmeye based on svn. Skyline is an open source software designed to help SCM quickly complete configuration work. Welcome to come and communicate
Search scmeye on Baidu