Re: [openssl-dev] Continuous Integration for OpenSSL
On Mon, 24 Aug 2015 at 19:35 Matt Caswell m...@openssl.org wrote: On 24/08/2015 10:08, Ben Laurie wrote: On Mon, 24 Aug 2015 at 03:56 Salz, Rich rs...@akamai.com mailto:rs...@akamai.com wrote: On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com mailto:rs...@akamai.com 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 has a login and is careful about failures. Seems to me they should be on the website. BTW I tracked it down: http://openssl-sanity.cisco.com:8080/ However, doesn't appear to be up. :-( It's up; link is wrong: https://openssl-sanity.cisco.com:8443/ Ah, thanks. So, should we link to this (and any other CI sites) from the website? Also, next stupid question, if I look there, I see for example: https://openssl-sanity.cisco.com:8443/job/1_0_1_mips/ How do I find out how that's being built? Matt ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
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 m...@openssl.org mailto:m...@openssl.org wrote: On 24/08/2015 10:08, Ben Laurie wrote: On Mon, 24 Aug 2015 at 03:56 Salz, Rich rs...@akamai.com mailto:rs...@akamai.com mailto:rs...@akamai.com mailto:rs...@akamai.com wrote: On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com mailto:rs...@akamai.com mailto:rs...@akamai.com mailto:rs...@akamai.com 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 has a login and is careful about failures. Seems to me they should be on the website. BTW I tracked it down: http://openssl-sanity.cisco.com:8080/ However, doesn't appear to be up. :-( It's up; link is wrong: https://openssl-sanity.cisco.com:8443/ Ah, thanks. So, should we link to this (and any other CI sites) from the website? Also, next stupid question, if I look there, I see for example: https://openssl-sanity.cisco.com:8443/job/1_0_1_mips/ How do I find out how that's being built? Matt ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
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 rs...@akamai.com mailto:rs...@akamai.com wrote: On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com mailto:rs...@akamai.com 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 has a login and is careful about failures. Seems to me they should be on the website. BTW I tracked it down: http://openssl-sanity.cisco.com:8080/ However, doesn't appear to be up. :-( I believe it also (at least when working) sends email on failures - would be nice if those went to a list... ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
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 rs...@akamai.com mailto:rs...@akamai.com wrote: On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com mailto:rs...@akamai.com 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 has a login and is careful about failures. Seems to me they should be on the website. BTW I tracked it down: http://openssl-sanity.cisco.com:8080/ However, doesn't appear to be up. :-( It's up; link is wrong: https://openssl-sanity.cisco.com:8443/ Matt ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
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 to catch the 25efcb44 build failure. Additionally Travis automatically builds pull requests submitted on GitHUb, in order to give immediate feedback to submitter and reviewer. So I think it still makes sense to have Travis alongside this Cisco buildfarm (as you said, the more the merrier), but if you don't agree then both #63 and #373 pull requests can be closed (if anything, two less open PRs...). Cheers signature.asc Description: Digital signature ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] Continuous Integration for OpenSSL
On Mon, 24 Aug 2015 at 03:56 Salz, Rich rs...@akamai.com wrote: On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com 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 has a login and is careful about failures. Seems to me they should be on the website. BTW I tracked it down: http://openssl-sanity.cisco.com:8080/ However, doesn't appear to be up. :-( I believe it also (at least when working) sends email on failures - would be nice if those went to a list... ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] Continuous Integration for OpenSSL
On Mon, 24 Aug 2015 at 09:53 Alessandro Ghedini alessan...@ghedini.me 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 not oging to enable Travis CI? If anything this buildfarm didn't seem to catch the 25efcb44 build failure. Additionally Travis automatically builds pull requests submitted on GitHUb, in order to give immediate feedback to submitter and reviewer. So I think it still makes sense to have Travis alongside this Cisco buildfarm (as you said, the more the merrier), but if you don't agree then both #63 and #373 pull requests can be closed (if anything, two less open PRs...). I've just +1'ed #373 - if another OpenSSL dev will also do that, I'll push it... ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
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 Ghedini alessan...@ghedini.memailto:alessan...@ghedini.me 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 not oging to enable Travis CI? If anything this buildfarm didn't seem to catch the 25efcb44 build failure. Additionally Travis automatically builds pull requests submitted on GitHUb, in order to give immediate feedback to submitter and reviewer. So I think it still makes sense to have Travis alongside this Cisco buildfarm (as you said, the more the merrier), but if you don't agree then both #63 and #373 pull requests can be closed (if anything, two less open PRs...). I've just +1'ed #373 - if another OpenSSL dev will also do that, I'll push it... ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] Continuous Integration for OpenSSL
On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com 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 has a login and is careful about failures. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] Continuous Integration for OpenSSL
On Sat, 22 Aug 2015 at 01:56 Salz, Rich rs...@akamai.com 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 mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] Continuous Integration for OpenSSL
Alessandro Ghedini alessan...@ghedini.me 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 built/tested using many versions of GCC and Clang. Recently Clang-3.7 stopped working on Travis but I think it will start working again soon. On Windows, you can use Appveyor; see appveyor.yml in the repo linked above. Cheers, Brian ___ 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 gcc - I run an out of the box build+test process - and also a special one : expand c code (gcc -E), regenerate the source code with source code injection (memory leak tests)+build+test process. The aim of this is to detect memory problems (cf heatblead vulnerability...), or souce code errors (switch error in particular, yes I did find one and alerted the team last year). The CI run uploading the daily snapshot from the source repo. I had proposed to run this CI, but I need from the openssl team some inputs : - what config must be tested - for each platform I might, in the future, install a publicly available Jenkins env for OpenSsl. How can we go one step forward ? Didier QualiteSys http://www.qualitesys.com/ [3] Le 21.08.2015 18:38, Brian Smith a écrit : Alessandro Ghedini alessan...@ghedini.me 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 [1], which allows a project to be built/tested using many versions of GCC and Clang. Recently Clang-3.7 stopped working on Travis but I think it will start working again soon. On Windows, you can use Appveyor; see appveyor.yml in the repo linked above. Cheers, Brian ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev [2] Links: -- [1] https://github.com/briansmith/ring [2] https://mta.openssl.org/mailman/listinfo/openssl-dev [3] http://www.qualitesys.com/ ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
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
