Continuous Integration Workflow for SVN
I am trying to set up a continuous integration workflow for SVN, just like for a GIT project. Can anyone suggest a good code review tool that integrates with Jenkins for +1 functionality and also allows users to view code (+2 functionality) like Gerrit.
I have seen several questions related to this here, but not in the same way as mine. I want to integrate svn with Jenkins viewer tool on windows environment. I see that the ReviewBoard installation does not work with windows and phabricator is not supported on windows. Can anyone suggest any alternatives?
Also you can share your experience about what kind of workflow you set up for svn (linux or windows) ..
source to share
Gerrit is specially designed for this. As described here :
Gerrit is a free web-based team collaboration tool. Software developers in a team can revise each other in their source code using a web browser and approve or reject these changes. It integrates tightly with Git, a distributed version control system.
I highly recommend you take a look at this and this for details on Gerrit integration. For an in-depth workflow using Gerrit, check here .
As mentioned above, to make your life easier, I definitely used the Gerrit Trigger plugin .
This plugin combines Jenkins with Gerrit's code overview to trigger builds when a "patchset" is created.
EDIT: For a code review tool that integrates with SVN, I would recommend Atlaian Crucible . It's not free, but for small teams, it has a one-time cost of $ 10, which is very reasonable in my opinion.
Additionally, there are ways in which you can initiate Jenkins actions (i.e.: start a build) based on Crucible events (i.e.: code has been successfully reviewed without the issues listed by the reviewer). Try the link for more details on this.
The only drawback with Crucible I have problems storing SVN credentials in clear text. Atlassian has stated here that they do not want to fix this and are instead encouraging teams to use a read-only "system account". This can be a problem for development teams that do not have a system account (like mine). It is also a great tool.
source to share