[GenABEL-dev] Jenkins continuous integration server available
L.C. Karssen
lennart at karssen.org
Mon Dec 2 12:03:10 CET 2013
Dear all,
The Jenkins server can now be reached via jenkins.genabel.org (which
still points to the old URL on my home server). Note that there will be
an SSL certificate warning (since the certificate is signed for
*.karssen.org, not *.genabel.org). If I have time, I'll fix that in the
future.
As per Maksim's suggestion I also added a link in the Developer section
of www.genabel.org, as well as on http://genabel.r-forge.r-project.org/
Let me know if you notice any odd behaviour.
Lennart.
On 29-11-13 15:39, L.C. Karssen wrote:
> Good suggestion!
> I'll do that.
>
>
> Lennart.
>
> On 11/29/2013 02:04 PM, Maksim Struchalin wrote:
>> Hi Lennart,
>>
>> Is it possible to make a reference to http://www.karssen.org/jenkins/
>> from http://www.genabel.org/developers or from r-forge (or better from
>> both)? It would be more convinient to acess to it + future new
>> developres will know that such an instrument exists. Now, I have to look
>> for your email to figure out the ref to Jenkins.
>>
>> best,
>> Maksim
>>
>>
>> On 18/11/2013 20:20, L.C. Karssen wrote:
>>> Dear all,
>>>
>>> In order to keep an eye on the build stability of the various C/C++
>>> packages in the GenABEL suite, I've taken some time in the past weeks to
>>> set up a Jenkins server [1] at http://www.karssen.org/jenkins/
>>>
>>> Jenkins checks out the source code from R-forge, runs several static
>>> code analysis tools and tries to compile the code. Any errors or
>>> warnings that pop up are listed. This way we can make sure that the code
>>> is always in a proper (compilable) state and also provides hints on how
>>> to improve the code.
>>>
>>> Maarten Kooyman piloted the use of Jenkins at my previous employer. Many
>>> of the things we learned from that setup have been incorporated in this
>>> Jenkins install. Thanks a lot Maarten!
>>>
>>> The ProbABEL project is configured in most detail with checks of the
>>> C/C++ style, violations of the Google coding standards and Valgrind
>>> checks for memory leaks. More checks still need to be added for ProbABEL
>>> and other projects. Consider this a work in progress.
>>>
>>> Have a look around and let me know if you have any questions or
>>> suggestions.
>>>
>>>
>>> Best regards,
>>>
>>> Lennart.
>>>
>>>
>>> [1] http://jenkins-ci.org/
>>>
>>>
>>>
>>> _______________________________________________
>>> genabel-devel mailing list
>>> genabel-devel at lists.r-forge.r-project.org
>>> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>>
>>
>>
>> _______________________________________________
>> genabel-devel mailing list
>> genabel-devel at lists.r-forge.r-project.org
>> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>>
>
>
>
> _______________________________________________
> genabel-devel mailing list
> genabel-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
L.C. Karssen
Utrecht
The Netherlands
lennart at karssen.org
http://blog.karssen.org
GPG key ID: A88F554A
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: OpenPGP digital signature
URL: <http://lists.r-forge.r-project.org/pipermail/genabel-devel/attachments/20131202/686c7f34/attachment.sig>
More information about the genabel-devel
mailing list