Skip to content

refactor: cometbft image build (backport #5179)#5181

Merged
mergify[bot] merged 2 commits intov0.38.xfrom
mergify/bp/v0.38.x/pr-5179
Jun 5, 2025
Merged

refactor: cometbft image build (backport #5179)#5181
mergify[bot] merged 2 commits intov0.38.xfrom
mergify/bp/v0.38.x/pr-5179

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Jun 5, 2025


This is a refactor of the CometBFT docker image build.

The current state of this build is completely broken. It builds an amd64 and an arm64 version, and publishes each of them individually without doing a multi-arch image. The result is only the arch that finishes last ends up tagged.

This PR will make the single-arch builds tagged with arch specific labels, and the current labels with be multi-arch builds.

PR checklist

  • Tests written/updated
  • Changelog entry added in .changelog (we use unclog to manage our changelog)
  • Updated relevant documentation (docs/ or spec/) and code comments

This is an automatic backport of pull request #5179 done by [Mergify](https://mergify.com).

---

This is a refactor of the CometBFT docker image build.

The current state of this build is completely broken. It builds an amd64
and an arm64 version, and publishes each of them individually without
doing a multi-arch image. The result is only the arch that finishes last
ends up tagged.

This PR will make the single-arch builds tagged with arch specific
labels, and the current labels with be multi-arch builds.

#### PR checklist

- [x] Tests written/updated
- [x] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [x] Updated relevant documentation (`docs/` or `spec/`) and code
comments

(cherry picked from commit fa76e35)

# Conflicts:
#	.github/workflows/cometbft-docker.yml
@mergify mergify bot requested review from a team as code owners June 5, 2025 16:50
@mergify mergify bot added the conflicts label Jun 5, 2025
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Jun 5, 2025

Cherry-pick of fa76e35 has failed:

On branch mergify/bp/v0.38.x/pr-5179
Your branch is up to date with 'origin/v0.38.x'.

You are currently cherry-picking commit fa76e354.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .github/workflows/docker-build-cometbft.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .github/workflows/cometbft-docker.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@ironbird-prod
Copy link
Copy Markdown

ironbird-prod bot commented Jun 5, 2025

Ironbird - launch a network To use Ironbird, you can use the following commands:
  • /ironbird start OR /ironbird start --load-test-config= - Launch a testnet with the specified chain and load test configuration.
  • /ironbird chains - List of chain images that ironbird can use to spin-up testnet
  • /ironbird loadtests - List of load test modes that ironbird can run against testnet
Custom Load Test Configuration You can provide a custom load test configuration using the `--load-test-config=` flag:
/ironbird start cosmos --load-test-config={
  "block_gas_limit_target": 0.75,
  "num_of_blocks": 50,
  "msgs": [
    {"weight": 0.3, "type": "MsgSend"},
    {"weight": 0.3, "type": "MsgMultiSend"},
	{"weight": 0.4, "type": "MsgArr", "ContainedType": "MsgSend", "NumMsgs": 3300}
  ]
}

Use /ironbird loadtests to see more examples.

@mergify mergify bot merged commit e6ddb26 into v0.38.x Jun 5, 2025
18 checks passed
@mergify mergify bot deleted the mergify/bp/v0.38.x/pr-5179 branch June 5, 2025 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant