[Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 37 - Still Failing!
Waines, Greg
Greg.Waines at windriver.com
Thu May 25 16:53:26 UTC 2023
Scott Kamp ? (or anyone else)
Can you comment on whether you are building STX 7 that would require container builds ?
Greg.
From: Cervi, Thales Elero <ThalesElero.Cervi at windriver.com>
Sent: Wednesday, May 24, 2023 2:55 PM
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 37 - Still Failing!
Hi Scott,
>From my point of view, since we already have the official release images built and tagged, I don't see why not to discontinue container builds from r/stx.7.0.
This would only affect re-builds of our older branch and apparently to maintain that code base is starting to become a problematic task without any rewards if no one is needing those docker images to be re-build.
I would agree with discontinuing it.
Thales
________________________________
From: Scott Little <scott.little at windriver.com<mailto:scott.little at windriver.com>>
Sent: Wednesday, May 24, 2023 10:52 AM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io> <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Re: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 37 - Still Failing!
Branch r/stx.7.0 can build ISO's, but container builds remain broken on
stx-nova.
stx-nova's issues started with spice-html5. The first issue was
spice-html5's github repo, forcing a move to gitlab's copy of the
spice-html5. The move to gitlab went smoothly for debian (master and
r/stx.8.0), but is failing to clone from r/stx.7.0 centos. It appears
gitlab requires a newer version git. Centos is using version 1.8.x.
Debain is using a version 2.x.x.
r/stx.7.0 needs to find a way to inject a newer version of git into the
Loci CentOS container that stx-nova is based on.
The alternative is to discontinue contained builds from r/stx.7.0
Thoughts?
Scott
On 2023-05-21 06:41, starlingx.build at gmail.com<mailto:starlingx.build at gmail.com> wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Project: STX_7.0_build_layer_containers
> Build #: 37
> Status: Still Failing
> Timestamp: 20230521T051649Z
> Branch: r/stx.7.0
>
> Check logs at:
> http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20230521T051649Z/logs<https://urldefense.com/v3/__http:/mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20230521T051649Z/logs__;!!AjveYdw8EvQ!ftzUA8n1xWWbtn3QQJFR5OJKkoDXLFURJtptL6L_8rGfrwUjrYk3IT9-0edgdLCBIYmZvwyCqkoAPK4uHR5BQ30N9Bzydw_Bxg$>
> --------------------------------------------------------------------------------
> Parameters
>
> BUILD_CONTAINERS_DEV: false
> BUILD_CONTAINERS_STABLE: true
> FORCE_BUILD: true
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20230525/a18e4f64/attachment.htm>
More information about the Starlingx-discuss
mailing list