<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FranGarcia.me (Posts about git)</title><link>https://www.frangarcia.me/</link><description></description><atom:link href="https://www.frangarcia.me/categories/git.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Mon, 06 Jun 2022 06:29:15 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Gerrit for dummies and Software Factory</title><link>https://www.frangarcia.me/posts/gerrit-for-dummies-and-software-factory/</link><dc:creator>Fran Garcia</dc:creator><description>&lt;p&gt;Last Thursday I attended a great presentation by &lt;a href="https://www.frangarcia.me/posts/gerrit-for-dummies-and-software-factory/www.jpena.net"&gt;Javier Peña&lt;/a&gt;, 
an introduction to &lt;a href="https://www.gerritcodereview.com/"&gt;Gerrit&lt;/a&gt;. In no particular
order, this are the things that catched my eye:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Gerrit is a code review system. It sits between your source code repository
  (Git) and your developers, so any proposed change can be better discussed and 
  reviewed. In parallel, Gerrit can be instructed to launch integration tests
  to ensure the proposed change doesn't break anything. If the CI integration 
  tests are successfull, the patch can be merged with the code. Otherwise, further 
  changes can be done by the submitter with &lt;code&gt;git commit --amend&lt;/code&gt; until the patch
  is succesfully merged (or discarded).&lt;/li&gt;
&lt;li&gt;It is better than Github's review workflow because:&lt;ul&gt;
&lt;li&gt;It's not propietary ;-)&lt;/li&gt;
&lt;li&gt;Can work in a disconnected fashion with &lt;a href="https://github.com/openstack/gertty"&gt;Gertty&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewing dozens of commits for a single PR can get confusing fast, 
  specially with large patches.&lt;/li&gt;
&lt;li&gt;As mentioned earlier, Gerrit can be easily integrated with several CI systems.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Important opensource projects such as &lt;a href="https://review.openstack.org/"&gt;Openstack&lt;/a&gt; 
  and &lt;a href="https://gerrit.ovirt.org"&gt;oVirt&lt;/a&gt; are using it, although it started at Google.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There is project that is integrating Git, Gerrit, Zuul, Nodepool and a bunch of
other tools to make development easier. It's called 
&lt;a href="https://softwarefactory-project.io/"&gt;Software Factory&lt;/a&gt; and you can find 
additional info in their documentation: 
&lt;a href="https://softwarefactory-project.io/docs/"&gt;https://softwarefactory-project.io/docs/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Software Factory logo" src="https://softwarefactory-project.io/docs/_images/logo.svg"&gt;&lt;/p&gt;
&lt;p&gt;Happy hacking!&lt;/p&gt;</description><category>gerrit</category><category>git</category><category>softwarefactory</category><guid>https://www.frangarcia.me/posts/gerrit-for-dummies-and-software-factory/</guid><pubDate>Sun, 05 Nov 2017 10:39:45 GMT</pubDate></item></channel></rss>