Re: [openssl-dev] Continuous Integration for OpenSSL

If you click on one of the individual builds (left side), then click on the "Console Output" link, it'll show the full build log. You can find the commands issued for the build in this log. On 08/25/2015 05:49 AM, Ben Laurie wrote: > > > On Mon, 24 Aug 2015 at 19:35 Matt Caswell

Re: [openssl-dev] Continuous Integration for OpenSSL

On Mon, 24 Aug 2015 at 19:35 Matt Caswell wrote: > On 24/08/2015 10:08, Ben Laurie wrote: > > > > > > On Mon, 24 Aug 2015 at 03:56 Salz, Rich > > wrote: > > > > > > >On Sat, 22 Aug 2015 at 01:56 Salz, Rich > > wrote: > > >>Thanks!

Re: [openssl-dev] Continuous Integration for OpenSSL

On 24/08/2015 10:08, Ben Laurie wrote: On Mon, 24 Aug 2015 at 03:56 Salz, Rich mailto:rs...@akamai.com>> wrote: >On Sat, 22 Aug 2015 at 01:56 Salz, Rich mailto:rs...@akamai.com>> wrote: >>Thanks! We have several cross-compile builds running on Cisco's build farm. The more the

Re: [openssl-dev] Continuous Integration for OpenSSL

The URL is https://openssl-sanity.cisco.com:8443/ On 08/24/2015 05:08 AM, Ben Laurie wrote: > > > On Mon, 24 Aug 2015 at 03:56 Salz, Rich > wrote: > > > >On Sat, 22 Aug 2015 at 01:56 Salz, Rich > wrote: > >>Thanks! We have several c

Re: [openssl-dev] Continuous Integration for OpenSSL

+1 -- Senior Architect, Akamai Technologies IM: richs...@jabber.at Twitter: RichSalz From: Ben Laurie [mailto:b...@links.org] Sent: Monday, August 24, 2015 5:15 AM To: openssl-dev@openssl.org Subject: Re: [openssl-dev] Continuous Integration for OpenSSL On Mon, 24 Aug 2015 at 09:53 Alessandro

Re: [openssl-dev] Continuous Integration for OpenSSL

On Mon, 24 Aug 2015 at 09:53 Alessandro Ghedini wrote: > On Sat, Aug 22, 2015 at 12:55:43am +, Salz, Rich wrote: > > Thanks! We have several cross-compile builds running on Cisco's build > farm. > > The more the merrier. I am sure ARM would be appreciated. > > Does this mean that you are no

Re: [openssl-dev] Continuous Integration for OpenSSL

On Mon, 24 Aug 2015 at 03:56 Salz, Rich wrote: > > >On Sat, 22 Aug 2015 at 01:56 Salz, Rich wrote: > >>Thanks! We have several cross-compile builds running on Cisco's build > farm. The more the merrier. I am sure ARM would be appreciated. > > >Are these linked from the website somewhere? > >

Re: [openssl-dev] Continuous Integration for OpenSSL

On Sat, Aug 22, 2015 at 12:55:43am +, Salz, Rich wrote: > Thanks! We have several cross-compile builds running on Cisco's build farm. > The more the merrier. I am sure ARM would be appreciated. Does this mean that you are not oging to enable Travis CI? If anything this buildfarm didn't seem

Re: [openssl-dev] Continuous Integration for OpenSSL

>On Sat, 22 Aug 2015 at 01:56 Salz, Rich wrote: >>Thanks!  We have several cross-compile builds running on Cisco's build farm.  >>The more the merrier.  I am sure ARM would be appreciated. >Are these linked from the website somewhere? No. John Foley @Cisco posted bout them, I think, and Matt

Re: [openssl-dev] Continuous Integration for OpenSSL

On Sat, 22 Aug 2015 at 01:56 Salz, Rich wrote: > Thanks! We have several cross-compile builds running on Cisco's build > farm. The more the merrier. I am sure ARM would be appreciated. > Are these linked from the website somewhere? ___ openssl-dev m

Re: [openssl-dev] Continuous Integration for OpenSSL

Thanks! We have several cross-compile builds running on Cisco's build farm. The more the merrier. I am sure ARM would be appreciated. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] Continuous Integration for OpenSSL

Hello the OpenSsl team I managed to setup a Jenkins CI engine with this configuration: - Jenkins engine run on Windows7 - Jenkins slaves run on Windows7 for Amd with Mingw/gcc - Jenkins slave run on Ubuntu Linux for Intel with gcc - Jenkins slave run on Raspberry PI Linux for Arm with

Re: [openssl-dev] Continuous Integration for OpenSSL

Alessandro Ghedini wrote: > Travis has some limitations though, like the fact that it only supports > Linux > and OS X, with fairly old compiler versions (e.g. gcc 4.6). > Take a look at .travis.yml and mk/update-travis-yml.py in https://github.com/briansmith/ring, which allows a project to be b

[openssl-dev] Continuous Integration for OpenSSL

Hello, given the recent incident with [0] I think it would make a lot of sense for the OpenSSL project to have some kind of continuous integration system in place, in order to catch similar problems more quickly. The easiest way would probably be to enable Travis CI [1] for the GitHub repository,