search

stackabletech / issues

This repository is only for issues that concern multiple repositories or don't fit into any specific repository
2 stars 0 forks source link

Renovate and similar only update if binary or dependency is available for arm64 AND amd64 #487

Closed Maleware closed 1 month ago

Maleware commented 11 months ago

ToDo's:

Maleware commented 2 months ago

moved to development as Refinement was done already. Started with doing it.

Maleware commented 2 months ago

By the looks of https://github.com/stackabletech/docker-images, I can find some things for renovate to do.

Precisely:

# renovate: datasource=github-releases packageName=rust-lang/rust
ENV RUST_DEFAULT_TOOLCHAIN_VERSION=1.80.1

# renovate: datasource=crate packageName=cargo-cyclonedx
ENV CARGO_CYCLONEDX_CRATE_VERSION=0.5.5

# renovate: datasource=crate packageName=cargo-auditable
ENV CARGO_AUDITABLE_CRATE_VERSION=0.6.4

# renovate: datasource=github-releases packageName=protocolbuffers/protobuf
ENV PROTOC_VERSION=27.3

Those are, as far as I understand all build from source during the process of building ubi-rust-builders and stackable-base up to protoc. However, protoc is uploaded and thus controlled by our update process by executing the upload-script.

Thus nothing to do in docker-images.

Maleware commented 1 month ago

Operators look good. Both pipeline and images are well reviewed.

I've didn't change anything on renovate, just ensured that the actual dependencies are on arm64 and x86.

Maleware commented 1 month ago

One thing:

In docker-images we have a few pipelines. It appears that none of them are watched by renovate at this moment. It seems this is not on purpose.

I will have a talk with @lfrancke once he is back in the drivers seat. Till then I'll move this to track.

Maleware commented 1 month ago

After some clarifying, testing and looking at the results of renovate runs, it looks pretty good with renovate and multi architecture.

It is watching all dependencies necessary and updates correct and according. However, this is not due to renovate being configured this way, it's the arm environment being at a level now with x86.

I've checked and tested a few repos ( not all ) and wasn't able to find a flaw in terms of MA.

This said, there is no possibility ( according to google and docs ) to configure renovate to check first if dependencies are multi arch available. It's save to assume that if a dependency is multi-arch, the next release will be too.

Nothing to do and looks good. Closing the issue as done.