<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<big>JP: Thanks for the info re: Capistrano, Jenkins, Bamboo, Gandalf
(ending with "f" ).<br>
Per Wikipedia (and my library) Gandalf </big><span class="st"><big>is
a fictional character in J. R. R. Tolkien's novels The Hobbit and The
Lord of the Rings.<br>
<br>
I am replying to the KWLUG discussion group so that all can see your
suggestions. <br>
And comment, if so motivated.<br>
<br>
As for the complexity of my project, it is really rather modest as its
purpose is self-study and educational.<br>
First, for the website / software technologies used therein.<br>
Then, for the admin / dev / build management tools and techniques
involved, e.g. Git.<br>
<br>
Thanks<br>
John Johnson<br>
</big><br>
<br>
</span><br>
On 2014-04-17 17:06, Jonathan Poole wrote:
<blockquote
cite="mid:F9603CCD-6E2F-441B-A3A2-559EEE060D74@digitaljedi.ca"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
I’d look at capistrano for your deploys, it’s primarily for ruby, but
works pretty much for anything.
<div><br>
</div>
<div>As for CI, for php, I’d use jenkins/bamboo to run your unit
tests and parse the result giving you that automated way of showing
code coverage. Although I know nothing of the complexity of your
project, or how it works a CI server IMHO is great for some projects,
not so great for others.</div>
<div><br>
</div>
<div>bamboo also has a feature of automatically merging, and creating
branches. I haven’t dawned into this, but the idea is if your branch
builds, and it’s all green, it will merge it into the protected branch,
that none can commit to, only merged from bamboo. Forcing the idea of
your tests/builds must pass before gandalph (sp?) lets your through.</div>
<div><br>
<div>
<div>On Apr 17, 2014, at 2:10 PM, John Johnson <<a
moz-do-not-send="true" href="mailto:jvj@golden.net">jvj@golden.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div bgcolor="#ffffff" text="#000000">
On 2014-04-17 11:16, <a moz-do-not-send="true"
class="moz-txt-link-abbreviated" href="mailto:jpoole@digitaljedi.ca">jpoole@digitaljedi.ca</a>
wrote:
<blockquote
cite="mid:49857.24.137.221.230.1397747817.squirrel@74.117.141.19"
type="cite">
<pre wrap="">We also have a rule, if you break the build, you owe timbits for all, after you fix the build.
</pre>
</blockquote>
<big>I just came back from TH after buying myself a coffee and
timbits.
I am not quite sure if the timbits were a penalty for breaking the
build in the first place or if the timbits were a reward for fixing the
build in the end.<br>
<br>
As for CI, I once worked where builds took many hours, and were
scheduled to run overnight. Later, with improved compilers and servers
, the builds would take an hour or so and were scheduled to run over
the lunch hour. As this was a large embedded system, CI was impossible
in this environment, as the executable was an all or none integration.
No DLLs. No Scripts. Just one bit exe.<br>
<br>
In my current environment my dev PC (Windows XP) is also the dev server
(w/XAMPP). I have yet to deploy to the Linux target PC.<br>
<br>
Thanks<br>
JohnJ<br>
</big><br>
<br>
<br>
<br>
</div>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a moz-do-not-send="true" href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br>
<a class="moz-txt-link-freetext" href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
</blockquote>
</div>
<br>
</div>
<p class="" avgcert="" color="#000000" align="left"><br>
Checked by AVG - <a moz-do-not-send="true" href="http://www.avg.com">www.avg.com</a><br>
Version: 2014.0.4355 / Virus Database: 3882/7354 - Release Date:
04/16/14</p>
</blockquote>
<br>
</body>
</html>