gluon-cli
Version:
Gluon cli: the gitflow and CI tool
216 lines (104 loc) • 6.37 kB
HTML
<html>
<head>
<meta charset="utf-8">
<title>What is Gluon?</title>
<link rel="stylesheet" type="text/css" href="../css/main.css">
<script src="https://code.jquery.com/jquery-3.1.1.slim.min.js" integrity="sha256-/SIrNqv8h6QGKDuNoLGA4iret+kyesCkHGzVUUV0shc=" crossorigin="anonymous"></script>
</head>
<body>
<section class="docs">
<aside>
<div class="logoContainer">
<a href="../index.html">
<img src="../images/logo.svg" class="logo" />
Gluon
</a>
</div>
<ul class="main_menu">
<li>
<h4>General</h4>
<a href="../users/get_started.html">How to install</a>
<a href="../users/get_started010whatis.html">What is gluon?</a>
</li>
<li>
<h4>Tutorials</h4>
<ul>
<li>
<a href="../users/tutorials/000init.html">Start working with Gluon!</a>
</li>
<li>
<a href="../users/tutorials/010feature.html">Working with Features</a>
</li>
<li>
<a href="../users/tutorials/020release.html">The Release process</a>
</li>
<li>
<a href="../users/tutorials/030hotfix.html">Make a Hotfix</a>
</li>
<li>
<a href="../users/tutorials/040merger.html">Merging master to develop</a>
</li>
<li>
<a href="../users/tutorials/050conflicts.html">Resolving conflicts with git</a>
</li>
<li>
<a href="../users/tutorials/060consolidate.html">Consolidate dependencies of master</a>
</li>
</ul>
</li>
<li>
<h4>Guides</h4>
<ul>
<li>
<a href="../users/guides/001versioning.html">Versions between branches</a>
</li>
<li>
<a href="../users/guides/002readlogoutput.html">Reading log execution of Gluon</a>
</li>
<li>
<a href="../users/guides/003componentlifecycle.html">Component lifecycle using Gluon</a>
</li>
</ul>
</li>
<li>
<h4>API</h4>
<h5>FLOWS</h5>
<ul>
</ul>
<h5>STEPS</h5>
<ul>
</ul>
</li>
</ul>
</aside>
<article>
<h1 id="what-is-gluon-">What is <strong>Gluon</strong>?</h1>
<p>Taking GitFlow model (<a href="http://nvie.com/posts/a-successful-git-branching-model/">http://nvie.com/posts/a-successful-git-branching-model/</a>) for branch based release management. We have developed a release management methodology of code source, artifact generation and automate versioning. (LINK TO METHODOLOGY DOCUMENT)</p>
<p>These are the fundamentals principles of this methodology:</p>
<ul>
<li><strong>Direct push to master and develop are forbidden</strong></li>
<li><strong>Unify versions and tags:</strong> Code source version (bower.json, package.json, *.gradle, pom.xml ...), artifacts version and the tags has to be <strong>consistent and unique</strong></li>
</ul>
<p>A set of piscosour recipes have been developed in order to automate many of the tasks involved in <strong>Gluon</strong> methodology</p>
<p>These tasks are:</p>
<ul>
<li><strong>init</strong>: Converts any repository to a repository prepared for <strong>Gluon</strong></li>
<li><strong>start</strong>: Creates a new branch within <strong>Gluon</strong>.</li>
<li><strong>finish</strong>: Finish a <strong>Gluon</strong> branch</li>
<li><strong>merge</strong>: Merge <strong>master</strong> changes into <strong>develop</strong>.</li>
</ul>
<iframe src="https://docs.google.com/presentation/d/1KFIvjSqKuSgoYIAbgM6_jAI5YPSqvThVwpKTFfMU_CM/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
</article>
</section>
<script type="text/javascript" src="../js/highlight.pack.js"></script>
<script>
hljs.initHighlightingOnLoad();
$(function(){
$('.toggle_section').on('click', function(ev) {
$(ev.currentTarget).parent('li').toggleClass('open');
});
});
</script>
</body>
</html>