[libcamera-ci,v1,2/2] Save `build.ninja` as artifact

25838 diff mbox series

It is useful for debugging problems related to compilation or linking.

Signed-off-by: Barnabás Pőcze <barnabas.pocze@ideasonboard.com>
---
 gitlab-ci.yml | 4 ++++
 1 file changed, 4 insertions(+)

--
2.52.0

On Mon, Jan 19, 2026 at 10:26:17AM +0100, Barnabás Pőcze wrote:
> It is useful for debugging problems related to compilation or linking.

Slightly less convinced by this one compared to 1/2, but I assume you
have found it useful, so I don't object.

> Signed-off-by: Barnabás Pőcze <barnabas.pocze@ideasonboard.com>
> ---
>  gitlab-ci.yml | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/gitlab-ci.yml b/gitlab-ci.yml
> index 4edb6a7..249e3ef 100644
> --- a/gitlab-ci.yml
> +++ b/gitlab-ci.yml
> @@ -142,6 +142,7 @@ container-debian:13:
>      expire_in: 1 week
>      paths:
>        - build/meson-logs/
> +      - build/build.ninja
>    variables:
>      BUILD_TYPE: debug
>      MESON_OPTIONS: ${MESON_ALL_OPTIONS}
> @@ -282,6 +283,7 @@ build-package:debug:
>      expire_in: 1 week
>      paths:
>        - build/meson-logs/
> +      - build/build.ninja
>        - libcamera-${CI_COMMIT_SHA}.tar.xz
>    variables:
>      BUILD_TYPE: debug
> @@ -316,6 +318,7 @@ build-package:cros:
>      name: libcamera-cros-${CI_COMMIT_SHA}
>      paths:
>        - build/meson-logs/
> +      - build/build.ninja
>        - libcamera-upstream-9999.tbz2
> 
>  # ------------------------------------------------------------------------------
> @@ -381,6 +384,7 @@ test-unit:
>      expire_in: 1 week
>      paths:
>        - build/meson-logs/
> +      - build/build.ninja

Is it needed here though ? If the goal is to debug compilation,
shouldn't we limit it to the build jobs ?

>      reports:
>        junit: build/meson-logs/testlog.junit.xml
>    variables:

2026. 01. 19. 13:18 keltezéssel, Laurent Pinchart írta:
> On Mon, Jan 19, 2026 at 10:26:17AM +0100, Barnabás Pőcze wrote:
>> It is useful for debugging problems related to compilation or linking.
> 
> Slightly less convinced by this one compared to 1/2, but I assume you
> have found it useful, so I don't object.
> 
>> Signed-off-by: Barnabás Pőcze <barnabas.pocze@ideasonboard.com>
>> ---
>>   gitlab-ci.yml | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/gitlab-ci.yml b/gitlab-ci.yml
>> index 4edb6a7..249e3ef 100644
>> --- a/gitlab-ci.yml
>> +++ b/gitlab-ci.yml
>> @@ -142,6 +142,7 @@ container-debian:13:
>>       expire_in: 1 week
>>       paths:
>>         - build/meson-logs/
>> +      - build/build.ninja
>>     variables:
>>       BUILD_TYPE: debug
>>       MESON_OPTIONS: ${MESON_ALL_OPTIONS}
>> @@ -282,6 +283,7 @@ build-package:debug:
>>       expire_in: 1 week
>>       paths:
>>         - build/meson-logs/
>> +      - build/build.ninja
>>         - libcamera-${CI_COMMIT_SHA}.tar.xz
>>     variables:
>>       BUILD_TYPE: debug
>> @@ -316,6 +318,7 @@ build-package:cros:
>>       name: libcamera-cros-${CI_COMMIT_SHA}
>>       paths:
>>         - build/meson-logs/
>> +      - build/build.ninja
>>         - libcamera-upstream-9999.tbz2
>>
>>   # ------------------------------------------------------------------------------
>> @@ -381,6 +384,7 @@ test-unit:
>>       expire_in: 1 week
>>       paths:
>>         - build/meson-logs/
>> +      - build/build.ninja
> 
> Is it needed here though ? If the goal is to debug compilation,
> shouldn't we limit it to the build jobs ?

Maybe somewhat misleading, but `test-unit` builds libcamera.


> 
>>       reports:
>>         junit: build/meson-logs/testlog.junit.xml
>>     variables:
>