Skip to content

Conversation

@gene-redpanda
Copy link
Member

@gene-redpanda gene-redpanda commented Sep 29, 2025

Updates various clients and tooling in the repo and moves us to task from make to bring the repo into alignment with the k8s operator.

@gene-redpanda gene-redpanda added the ci-ready indicates that a PR is ready for builds to run label Sep 29, 2025
@gene-redpanda gene-redpanda removed the ci-ready indicates that a PR is ready for builds to run label Oct 8, 2025
@gene-redpanda gene-redpanda added the ci-ready indicates that a PR is ready for builds to run label Oct 8, 2025
@gene-redpanda gene-redpanda changed the title test Move from Make to Task Oct 8, 2025
@gene-redpanda gene-redpanda removed the ci-ready indicates that a PR is ready for builds to run label Oct 8, 2025
@gene-redpanda gene-redpanda marked this pull request as ready for review October 8, 2025 19:40

vars:
ARTIFACT_DIR: "{{.PWD}}/artifacts"
DEPLOYMENT_ID: '{{.DEPLOYMENT_ID | default "devex-cicd"}}'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see this defined and some other variables with the same definitions multiple times (and sometimes not used). Is that intentional? If not would it be better to move share variables into Taskfile.yml at the top level?

- |
OS=$(uname)
if [ "$OS" = "Darwin" ]; then
curl -L {{.MAC_RPK}} -o {{.ARTIFACT_DIR}}/tmp/rpk.zip

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just my two cents, I find it better to put non-local variables into the scope of the task so it's clear what is local to this task and what's expected to be shared.

@gene-redpanda gene-redpanda added the ci-ready indicates that a PR is ready for builds to run label Oct 9, 2025
When run during the connect test without this particular method of testing for the existence of keys the connect test fails.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-ready indicates that a PR is ready for builds to run

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants