[buildbot-admin] [fips-sponsors] Buildbot workers
Matt Caswell
matt at openssl.org
Thu May 20 18:11:51 UTC 2021
Great news! Are you able to run the test suite?
Matt
On 20/05/2021 17:48, Connor Kelley wrote:
> Hi Matt,
> After pulling in the fixes for the broken assembly fixes I was able to
> successfully build without any of the .conf changes so I was able to
> cancel the PR.
> Using top of tree I was able to successfully build and arm64 target with
> ./Configure ios64-xcrun enable-fips enable-fips-securitychecks
> -mios-version-min=11.0 && make
>
> Thanks,
> -Connor
>> On May 19, 2021, at 10:59 AM, Matt Caswell <matt at openssl.org
>> <mailto:matt at openssl.org>> wrote:
>>
>> Thanks Connor...lets continue the conversation in the PR itself.
>>
>> Matt
>>
>> On 19/05/2021 15:43, Connor Kelley wrote:
>>> Hi Matt,
>>> I think the PR is trivial based on what you’re talking about but I’ll
>>> be happy to fill out one of those forms if you need it.
>>> The PR for the changes is here:
>>> https://github.com/openssl/openssl/pull/15352
>>> <https://github.com/openssl/openssl/pull/15352>
>>> <https://github.com/openssl/openssl/pull/15352
>>> <https://github.com/openssl/openssl/pull/15352>>
>>> Thanks,
>>> -Connor
>>>> On May 19, 2021, at 3:57 AM, Matt Caswell <matt at openssl.org
>>>> <mailto:matt at openssl.org> <mailto:matt at openssl.org
>>>> <mailto:matt at openssl.org>>> wrote:
>>>>
>>>> Hi Connor,
>>>>
>>>> Please submit them as a pull request on our public github site:
>>>>
>>>> https://github.com/openssl/openssl/pulls
>>>> <https://github.com/openssl/openssl/pulls>
>>>> <https://github.com/openssl/openssl/pulls
>>>> <https://github.com/openssl/openssl/pulls>>
>>>>
>>>> If you email the PR number here once created then we will know to
>>>> give it the attention it deserves.
>>>>
>>>> If the changes are anything other than very trivial then we will
>>>> also need an ICLA from you individually, as well as a CCLA from Blue
>>>> Cedar. See:
>>>>
>>>> https://www.openssl.org/policies/cla.html
>>>> <https://www.openssl.org/policies/cla.html>
>>>>
>>>> Matt
>>>>
>>>>
>>>> On 19/05/2021 01:54, Connor Kelley wrote:
>>>>> Hi Richard,
>>>>> I’ve got a working build that required a couple of updates to the
>>>>> 15-iOS.conf file to get it current. With those changes plus the
>>>>> configure invocation the build seemingly completes successfully.
>>>>> What is the process for submitting a PR to get those changes in and
>>>>> usable?
>>>>> Thanks,
>>>>> -Connor
>>>>> Get Outlook for iOS <https://aka.ms/o0ukef>
>>>>> ------------------------------------------------------------------------
>>>>> *From:* Richard Levitte <levitte at openssl.org>
>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM
>>>>> *To:* Nivedita Chevvakula <nchevvakula at bluecedar.com>
>>>>> *Cc:* Richard Levitte <levitte at openssl.org>; Tim Champagne
>>>>> <tchampagnejr at bluecedar.com>; Connor Kelley
>>>>> <ckelley at bluecedar.com>; buildbot-admin at openssl.org
>>>>> <buildbot-admin at openssl.org>
>>>>> *Subject:* Re: [fips-sponsors] Buildbot workers
>>>>> [ Also adding buildbot-admin at openssl.org (I should have done that
>>>>> long ago) ]
>>>>> Yes, some technical details is what I'm trying to get.
>>>>> Right now, that worker is building, sure, but that's a MacOS build,
>>>>> which wasn't what you wanted.
>>>>> So Tim, Connor, if you have something to share, I can hopefully do
>>>>> better progress on our end.
>>>>> Cheers,
>>>>> Richard
>>>>> On Mon, 17 May 2021 15:28:50 +0200,
>>>>> Nivedita Chevvakula wrote:
>>>>>> On this buildbot slave we don't run any our projects, we have set
>>>>>> this slave only for buildbot worker. Please let me know if I give
>>>>>> ssh creds it will expedite the process.
>>>>>> Also adding Connor and Timmy, hopefully they can clarify on how we
>>>>>> build OpenSSL project.
>>>>>> Best,
>>>>>> Niv
>>>>>> On 5/13/21, 4:24 AM, "Richard Levitte" <levitte at openssl.org> wrote:
>>>>>> What we expect to do is this at a minimum:
>>>>>> perl Configure {args...}
>>>>>> make
>>>>>> In the form that you filled in, there was the option to specify
>>>>>> necessary environment variables (which can affect the
>>>>>> configuration
>>>>>> step) and configuration options. I was hoping that would be
>>>>>> enough to
>>>>>> get something going.
>>>>>> I do not know what you're talking about regarding a .conf
>>>>>> file created
>>>>>> by the Configure step. I understand that you have some sort
>>>>>> of super
>>>>>> project that involves building OpenSSL as a component,
>>>>>> though, so I
>>>>>> can only assume that somewhere in there, it should be
>>>>>> possible to find
>>>>>> how the OpenSSL part is configured, i.e. I assume that there
>>>>>> is a run
>>>>>> of Configure hiding in there somewhere, and that it should be
>>>>>> possible
>>>>>> to see what arguments are used, as well as any relevant
>>>>>> environment
>>>>>> variables.
>>>>>> Does this answer your question?
>>>>>> Cheers,
>>>>>> Richard
>>>>>> On Fri, 07 May 2021 15:12:11 +0200,
>>>>>> Nivedita Chevvakula wrote:
>>>>>> > > We generate a project using cmake that gets built as
>>>>>> a dependency of other components in our project. If you are trying
>>>>>> to do - build everything using make, which requires a .conf file
>>>>>> created with ./Configure step. If so should have one of those
>>>>>> somewhere that satisfies what you are looking to produce for iOS,
>>>>>> as well as a
>>>>> different one for Android, please provide that we can put it in
>>>>> place on the build bot and just use that?
>>>>>> > > Please advise.
>>>>>> > > Best,
>>>>>> > Niv
>>>>>> > > On 5/4/21, 2:56 AM, "Richard Levitte"
>>>>>> <levitte at openssl.org> wrote:
>>>>>> > > Hi,
>>>>>> > > The worker is connecting fine, so far so good.
>>>>>> > > However, I realised that there are things
>>>>>> missing, where we need
>>>>>> > information from you!
>>>>>> > > This worker is meant to build for iOS, is it
>>>>>> not? That should require
>>>>>> > extra OpenSSL configuration options. So let me ask you
>>>>>> this, when you
>>>>>> > usually build OpenSSL for iOS, exactly how do you
>>>>>> usually configure
>>>>>> > OpenSSL?
>>>>>> > > Cheers,
>>>>>> > Richard
>>>>>> > > On Tue, 04 May 2021 03:46:17 +0200,
>>>>>> > Nivedita Chevvakula wrote:
>>>>>> > > > > Richard,
>>>>>> > > > > You can ignore my last mail with error
>>>>>> starting buildbot. It is seems to work now after editing
>>>>>> > > syntax for python2.7. Also we have created user
>>>>>> “buildbot” for this mac as recommended. Please let
>>>>>> > > me know if we need to pass those credentials or need
>>>>>> to setup anything else for the build bot.
>>>>>> > > > > Best,
>>>>>> > > > > Niv
>>>>>> > > > > From: Nivedita Chevvakula
>>>>>> <nchevvakula at bluecedar.com>
>>>>>> > > Date: Monday, May 3, 2021 at 6:44 PM
>>>>>> > > To: Richard Levitte <levitte at openssl.org>
>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers
>>>>>> > > > > Richard,
>>>>>> > > > > Buildbot has now installed with linker,
>>>>>> make, c compilers.
>>>>>> > > > > While starting the worker to connect to
>>>>>> master after editing tac file as you mentioned getting
>>>>>> > > syntax error . not able to pin point why. Attaching
>>>>>> the error log and the tac file here. Could you
>>>>>> > > please help.
>>>>>> > > > > Best,
>>>>>> > > > > Niv
>>>>>> > > > > From: Nivedita Chevvakula
>>>>>> <nchevvakula at bluecedar.com>
>>>>>> > > Date: Monday, May 3, 2021 at 9:22 AM
>>>>>> > > To: Richard Levitte <levitte at openssl.org>
>>>>>> > > Cc: "levitte at openssl.org" <levitte at openssl.org>, Tim
>>>>>> Champagne <tchampagne at bluecedar.com>, Kevin
>>>>>> > > Fox <kfox at bluecedar.com>
>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers
>>>>>> > > > > Hi Richard,
>>>>>> > > > > Thank you for sending the worker bot
>>>>>> setup requirements, I will go thru and will set up the
>>>>>> > > workerbot and will install the rest. Do you have any
>>>>>> deadline for this setup please share so that
>>>>>> > > it will help me prioritize.
>>>>>> > > > > So far these tools are installed over
>>>>>> the mac :
>>>>>> > > > > 1. Android Studio 4.1.3
>>>>>> > > 2. Xcode 12.5
>>>>>> > > 3. clang version 12.0.5 > > 4. Gcc
>>>>>> > > 5. Visual Studio Community 2019 for Mac
>>>>>> > > > > === Visual Studio Community 2019 for Mac ===
>>>>>> > > > > Version 8.9.7 (build 8)
>>>>>> > > > > Installation UUID:
>>>>>> f1ca8dad-7314-419a-8a39-880ba8a71230
>>>>>> > > > > GTK+ 2.24.23 (Raleigh theme)
>>>>>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638)
>>>>>> > > > > Package version: 612000125
>>>>>> > > > > === Mono Framework MDK ===
>>>>>> > > > > Runtime:
>>>>>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6)
>>>>>> (64-bit)
>>>>>> > > > > Package version: 612000125
>>>>>> > > > > === Roslyn (Language Service) ===
>>>>>> > > > >
>>>>>> 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210
>>>>>> > > > > === NuGet ===
>>>>>> > > > > Version: 5.8.0.6860
>>>>>> > > > > === .NET Core SDK ===
>>>>>> > > > > SDK:
>>>>>> /usr/local/share/dotnet/sdk/5.0.202/Sdks
>>>>>> > > > > SDK Versions:
>>>>>> > > > > 5.0.202
>>>>>> > > > > 3.1.408
>>>>>> > > > > 2.1.4
>>>>>> > > > > MSBuild SDKs: /Applications/Visual
>>>>>> Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/
>>>>>> > > Current/bin/Sdks
>>>>>> > > > > === .NET Core Runtime ===
>>>>>> > > > > Runtime: /usr/local/share/dotnet/dotnet
>>>>>> > > > > Runtime Versions:
>>>>>> > > > > 5.0.5
>>>>>> > > > > 3.1.14
>>>>>> > > > > 2.0.5
>>>>>> > > > > === .NET Core 3.1 SDK ===
>>>>>> > > > > SDK: 3.1.408
>>>>>> > > > > === Xamarin.Profiler ===
>>>>>> > > > > Version: 1.6.15.68
>>>>>> > > > > Location: /Applications/Xamarin
>>>>>> Profiler.app/Contents/MacOS/Xamarin Profiler
>>>>>> > > > > === Updater ===
>>>>>> > > > > Version: 11
>>>>>> > > > > === Apple Developer Tools ===
>>>>>> > > > > Xcode 12.5 (18205)
>>>>>> > > > > Build 12E262
>>>>>> > > > > === Xamarin.Mac ===
>>>>>> > > > > Xamarin.Mac not installed. Can't find
>>>>>> /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/
>>>>>> > > Version.
>>>>>> > > > > === Xamarin.iOS ===
>>>>>> > > > > Xamarin.iOS not installed.
>>>>>> > > > > Can't find mtouch or the Version file at
>>>>>> /Library/Frameworks/Xamarin.iOS.framework/Versions/
>>>>>> > > Current.
>>>>>> > > > > === Xamarin Designer ===
>>>>>> > > > > Version: 16.9.0.324
>>>>>> > > > > Hash: b1e216c75
>>>>>> > > > > Branch: remotes/origin/d16-9
>>>>>> > > > > Build date: 2021-04-16 00:02:50 UTC
>>>>>> > > > > === Xamarin.Android ===
>>>>>> > > > > Version: 11.2.2.1 (Visual Studio Community)
>>>>>> > > > > Commit: xamarin-android/d16-9/877f572
>>>>>> > > > > Android SDK:
>>>>>> /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx
>>>>>> > > > > Supported Android versions:
>>>>>> > > > > None installed
>>>>>> > > > > SDK Tools Version: 26.1.1
>>>>>> > > > > SDK Platform Tools Version: 30.0.4
>>>>>> > > > > SDK Build Tools Version: 30.0.2
>>>>>> > > > > Build Information:
>>>>>> > > > > Mono: 5e9cb6d
>>>>>> > > > > Java.Interop:
>>>>>> xamarin/java.interop/d16-9 at 54f8c24
>>>>>> > > > > ProGuard:
>>>>>> Guardsquare/proguard/v7.0.1 at 912d149
>>>>>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4
>>>>>> > > > > Xamarin.Android Tools:
>>>>>> xamarin/xamarin-android-tools/d16-9 at d210f11
>>>>>> > > > > === Microsoft OpenJDK for Mobile ===
>>>>>> > > > > Java SDK:
>>>>>> /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25
>>>>>> > > > > 1.8.0-25
>>>>>> > > > > Android Designer EPL code available here:
>>>>>> > > > >
>>>>>> https://github.com/xamarin/AndroidDesigner.EPL
>>>>> <https://github.com/xamarin/AndroidDesigner.EPL>
>>>>>> > > > > === Android SDK Manager ===
>>>>>> > > > > Version: 16.9.0.22
>>>>>> > > > > Hash: a391de2
>>>>>> > > > > Branch: remotes/origin/d16-9~2
>>>>>> > > > > Build date: 2021-03-24 08:30:26 UTC
>>>>>> > > > > === Android Device Manager ===
>>>>>> > > > > Version: 16.9.0.17
>>>>>> > > > > Hash: fc2b3db
>>>>>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1
>>>>>> > > > > Build date: 2021-03-24 08:30:44 UTC
>>>>>> > > > > === Build Information ===
>>>>>> > > > > Release ID: 809070008
>>>>>> > > > > Git revision:
>>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26
>>>>>> > > > > Build date: 2021-04-16 07:38:03-04
>>>>>> > > > > Build branch: release-8.9
>>>>>> > > > > Xamarin extensions:
>>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26
>>>>>> > > > > === Operating System ===
>>>>>> > > > > Mac OS X 10.16.0
>>>>>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0
>>>>>> > > > > Thu Jan 21 00:07:06 PST 2021
>>>>>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64
>>>>>> > > > > Best,
>>>>>> > > > > Niv
>>>>>> > > > > From: Richard Levitte <levitte at openssl.org>
>>>>>> > > Date: Monday, May 3, 2021 at 4:54 AM
>>>>>> > > To: Nivedita Chevvakula <nchevvakula at bluecedar.com>
>>>>>> > > Cc: levitte at openssl.org <levitte at openssl.org>, Tim
>>>>>> Champagne <tchampagne at bluecedar.com>, Kevin Fox
>>>>>> > > <kfox at bluecedar.com>
>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers
>>>>>> > > > > Hi,
>>>>>> > > > > Thank you for offering workers to us!
>>>>>> > > > > To be able to set up your worker, you
>>>>>> must use version 2.6.0 or
>>>>>> > > higher. Older version do not support TLS-protected
>>>>>> connections.
>>>>>> > > > > Please see these instructions for
>>>>>> installing the buildbot worker
>>>>>> > > software:
>>>>>> > > > >
>>>>>> http://docs.buildbot.net/latest/manual/installation/worker.html
>>>>> <http://docs.buildbot.net/latest/manual/installation/worker.html>
>>>>>> > > > > When buildbot has been installed on the
>>>>>> platform where the buildbot
>>>>>> > > worker is to be run, this is how a worker is created:
>>>>>> > > > > $ buildbot-worker create-worker
>>>>>> --use-tls BASEDIR \
>>>>>> > > buildbot.openssl.org:9989 'bluecedar-01'
>>>>>> 'Rak;osErfabOn5'
>>>>>> > > > > where BASEDIR is determined by you. See
>>>>>> further down for a few notes
>>>>>> > > on TLS.
>>>>>> > > > > To run a buildbot worker, you do this:
>>>>>> > > > > $ buildbot-worker start BASEDIR
>>>>>> > > > > Apart from the software needed to run a
>>>>>> buildbot worker, and the
>>>>>> > > utilities that are the normal part of the operating
>>>>>> system, you also
>>>>>> > > need to ensure that the following components are
>>>>>> available:
>>>>>> > > > > - toolchains, i.e. C compiler, linker,
>>>>>> make. If you have specified
>>>>>> > > toolchains in the worker request form, you need
>>>>>> to ensure that all
>>>>>> > > of them are installed.
>>>>>> > > > > - git
>>>>>> > > > > Regarding TLS, it may be that the
>>>>>> buildbot worker platform doesn't
>>>>>> > > have the appropriate certification verification roots
>>>>>> set up. In that
>>>>>> > > case, you may need to apply the attached buildbot.tac
>>>>>> patch, and store
>>>>>> > > the attached PEM files in a directory of your choice.
>>>>>> Finish up by
>>>>>> > > find the string '/PATH/TO/ssl-roots-dir' and replace
>>>>>> its contents with
>>>>>> > > the path of directory where you stored the PEM files.
>>>>>> > > > > > -- > Richard
>>>>>> Levitte levitte at openssl.org
>>>>>> > OpenSSL Project
>>>>>> http://www.openssl.org/~levitte/
>>>>>> <http://www.openssl.org/~levitte/>
>>>>>> -- Richard Levitte levitte at openssl.org
>>>>>> OpenSSL Project http://www.openssl.org/~levitte/
>>>>>> <http://www.openssl.org/~levitte/>
>>>>> --
>>>>> Richard Levitte levitte at openssl.org
>>>>> OpenSSL Project http://www.openssl.org/~levitte/
>>>>> <http://www.openssl.org/~levitte/>
>>>>> _______________________________________________
>>>>> buildbot-admin mailing list
>>>>> buildbot-admin at openssl.org
>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin
>
More information about the buildbot-admin
mailing list