You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2016/02/26 11:08:18 UTC
[jira] [Commented] (SLING-3987) move from Subversion to Git
[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168760#comment-15168760 ]
Bertrand Delacretaz commented on SLING-3987:
--------------------------------------------
Another thing discussed on our dev list is the Jenkins setup - we seem to agree on having one Jenkins job per module, to make it easier to find what breaks. The https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin can be useful to create multiple jobs.
> move from Subversion to Git
> ---------------------------
>
> Key: SLING-3987
> URL: https://issues.apache.org/jira/browse/SLING-3987
> Project: Sling
> Issue Type: Task
> Components: Best practices
> Reporter: Oliver Lietz
>
> track work for moving to Git
> [Wiki: Move from Subversion to Git|https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to+Git]
> [discussion @dev|http://apache-sling.73963.n3.nabble.com/jira-Created-SLING-3987-move-from-Subversion-to-Git-td4040882.html#a4040901] with [~cziegeler], [~bdelacretaz], [~fmeschbe], [~justinedelson], [~rombert] and [~radu.cotescu]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)