[PATCH] sb/set-builder: Fix staging and tar file generation with a single config build

[Chris Johns]

On 30/9/2022 4:08 pm, Christian MAUDERER wrote:
> Am 30.09.22 um 07:37 schrieb Chris Johns:
>> On 30/9/2022 3:33 pm, Christian MAUDERER wrote:
>>> Am 30.09.22 um 05:49 schrieb Chris Johns:
>>>> On 29/9/2022 9:50 pm, Chris Johns wrote:
>>>>> On 29/9/22 9:45 pm, Christian MAUDERER wrote:
>>>>>> Hello Chris,
>>>>>>
>>>>>> thanks for the quick patch. With this qemu and microblaze work again like
>>>>>> expected.
>>>>>>
>>>>>> I tested all tools starting with devel/* and from the ones that work only
>>>>>> devel/autotools-internal didn't generate a tar archive. But that one has a
>>>>>> comment "Do not use via the command line" in the bset file so that is most
>>>>>> likely fine.
>>>>>>
>>>>>> Some of other devel/* packages didn't build in my test setup, but I have
>>>>>> never
>>>>>> tested or used them before so that is probably a problem of my build
>>>>>> environment
>>>>>> or maybe a known bug.
>>>>>
>>>>> Thanks for the testing. I will push to the devel branch and 5.
>>>>>
>>>>
>>>> Tarfile creation is working however installing is not. I am working on fixing
>>>> this.
>>>>
>>>> Chris
>>>
>>> Sorry that I missed that. I only tried to generate the tar archives.
>>
>> Same. Testing a fix but it takes time to check properly.
>>
>> I am wondering if I can create a test mode in the deployment repo. The hard part
>> is how to automatically check the build has worked.
>>
>> Chris
> 
> I'm currently trying to create a basic CI/CD setup for testing our embedded
> brains patches using GitHub. At the moment it's still quite experimental and
> still a bit thrown together but it basically runs:
> 
> https://github.com/embedded-brains/rtems-source-builder/actions/runs/3151126889

Nice.

> It didn't catch that bug because it doesn't use installed tools for the
> simulator runs, but maybe I can change that.
> 
> If it works well enough, we maybe could re-use some scripts or work flows to set
> up an official RTEMS CI/CD with whatever community preferred CI system. It
> shouldn't be too big of a problem to port the logic to Gitlab CI, Cirrus CI or
> any other modern CI system.

I have started https://git.rtems.org/chrisj/rtems-deployment.git/. I would like
it to be the landing place for this type of stuff if it fits. The repo is being
actively worked on by me.

I can build RPMs on Rocky 8 and 9. These RPMs are the base for EPICS RPMs built
into docker containers used to build Gemini's EPICS based systems. All handled
via CI in gitlab.

To build an RPM you configure with the path to the RSB and then run `./waf
rpmspec`. A spec file is created you can use with `rpmbuild` to make an RPM. I
am keeping the generation and building of the RPM separate. By default the repo
builds a tarfile.

Once this repo stabilises I would like to see if it can move to the top level. I
am working on better documentation for it and with that some constraints about
what is offered.

Deployment is something varies and I hope this repo can grow to make common
solutions widely available. I am fine for organisation to send in specific
configurations if they are open to having them in the repo.

Chris