[Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing!

[Liu, ZhipengS]

Hi Scott, 

Could you please help trigger the build again after changing the script, thanks!

For your optimization proposal,  could you help to create a story to track it?
I'd like to take it then.

Thanks!
Zhipeng

-----Original Message-----
From: Scott Little <scott.little at windriver.com> 
Sent: 2020年7月1日 13:36
To: Liu, ZhipengS <zhipengs.liu at intel.com>; starlingx-discuss at lists.starlingx.io; Panech, Davlet <Davlet.Panech at windriver.com>
Subject: Re: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing!

Sorry, I missed this email earlier.

The build script does have the extra --repo args, but it was wrapped in a conditional clause looking for ussuri in the tag

if [ "$BASE_LATEST_TAG" == "ussuri-stable-latest" ] || [ "$BASE_LATEST_TAG" == "master-ussuri-stable-latest" ]; then
     EXTRA_ARGS+="
    --repo
ussuri-ceph,http://${HOST}:${HOST_PORT}/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/
\
    --repo
ussuri-wsgi,http://${HOST}:${HOST_PORT}/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/
     "
fi

I can remove the conditional statement for now.

However we need a better solution in the long term.  We shouldn't need to modify cengn build scripts, or the build docs, every time we upgrade something.

I propose the following:
- build-stx-base.sh and build-stx-images.sh need to accept a new argument (--config-file <path>) specifying a path to a config file.  We can establish a well known location within the code repository for such config files.  If the cengn scripts see that file, it will add a single EXTRA_ARGS+="--config-file <path>"

- Alternatively these commands automatically look for the config files at the predetermined location, and apply them if found. If not found, continue without error. Perhaps add an optional new argument to suppress this behavior, or substitute an alternate config file.

- The config file needs to be able to specify additional arguments to be passed into the the command. e.g.
    --repo
ussuri-ceph,http://mirror.starlingx.cengn.ca/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/
\
    --repo
ussuri-wsgi,http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/

Can you work toward implementing this please?

Scott



On 2020-06-30 10:00 p.m., Liu, ZhipengS wrote:
> +Devlet,
>
> Hi Scott and Devlet,
>
> Master build has already been blocked for 2 days since ussuri patches merged.
> I have found the root cause as I mentioned in my previous email. But I 
> could not Modify cengn script to add these 2 repos to unblock the master build.
> Could you have chance to add them and retrigger the master build today?
> I would like to do that if possible. Unfortunately, I have no access 
> to do that now☹
>
> Thanks!
> Zhipeng
>
> -----Original Message-----
> From: Liu, ZhipengS <zhipengs.liu at intel.com>
> Sent: 2020年7月1日 9:46
> To: Scott Little <scott.little at windriver.com>; 
> starlingx-discuss at lists.starlingx.io
> Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure!
>
> Hi Scott,
>
> Yes, I agree, ussuri builds are no need anymore.
>
> However, for master branch build, still below 2 additional repos that you added for ussuri build,  you did not added for base image build which causes master build still failed to build out all openstack images.
>
> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monoli
> thic/20200630T211517Z/logs/jenkins-STX_build_docker_base_image-265.log
> .html
>
> + EXTRA_ARGS+='
> --repo 
> ussuri-ceph,http://build.starlingx.cengn.ca:80/mirror/centos/download.
> ceph.com/rpm-mimic/el7/x86_64/ --repo 
> ussuri-wsgi,http://build.starlingx.cengn.ca:80/mirror/centos/centos/mi
> rror.centos.org/centos/7/sclo/x86_64/rh/
> '
>
> Thanks!
> Zhipeng
>
> -----Original Message-----
> From: Scott Little <scott.little at windriver.com>
> Sent: 2020年7月1日 4:58
> To: Liu, ZhipengS <zhipengs.liu at intel.com>; 
> starlingx-discuss at lists.starlingx.io
> Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure!
>
> I have disabled all the ussuri builds. In theory we don't need them.  Do you agree?
>
> Scott
>
>
> On 2020-06-28 10:00 p.m., Liu, ZhipengS wrote:
>> Scott,
>> It seems caused by patch already merge.
>> You may need update build info setting and retrigger it again.
>>
>> Thanks!
>> Zhipeng
>>
>> -----Original Message-----
>> From: build.starlingx at gmail.com <build.starlingx at gmail.com>
>> Sent: 2020年6月28日 20:01
>> To: starlingx-discuss at lists.starlingx.io
>> Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure!
>>
>> Project: STX_build_layer_compiler_master_ussuri
>> Build #: 8
>> Status: Failure
>> Timestamp: 20200628T120017Z
>>
>> Check logs at:
>> http://mirror.starlingx.cengn.ca/mirror/starlingx/ussuri/centos/compi
>> l
>> er/20200628T120017Z/logs
>> ---------------------------------------------------------------------
>> -
>> ----------
>> Parameters
>>
>> FULL_BUILD: false
>> FORCE_BUILD: false
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss