Skip to content

ci(testapp-docker): release two images, not one (backport #5014)#5167

Merged
mergify[bot] merged 3 commits intov1.xfrom
mergify/bp/v1.x/pr-5014
Jun 4, 2025
Merged

ci(testapp-docker): release two images, not one (backport #5014)#5167
mergify[bot] merged 3 commits intov1.xfrom
mergify/bp/v1.x/pr-5014

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Jun 4, 2025

Previously, we would only push a single arm64 image. Evidence: https://hub.docker.com/r/cometbft/e2e-node/tags

This is an automatic backport of pull request #5014 done by Mergify.

@melekes @mergify
ci(testapp-docker): release two images, not one (#5014)
f700005 
Previously, we would only push a single arm64 image. Evidence:
https://hub.docker.com/r/cometbft/e2e-node/tags

(cherry picked from commit 0fb96b3)

# Conflicts:
#	.github/workflows/testapp-docker.yml
@mergify mergify bot requested review from a team as code owners June 4, 2025 18:26
@mergify mergify bot added the conflicts label Jun 4, 2025
@mergify mergify bot assigned melekes Jun 4, 2025
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Jun 4, 2025

Cherry-pick of 0fb96b3 has failed:

On branch mergify/bp/v1.x/pr-5014
Your branch is up to date with 'origin/v1.x'.

You are currently cherry-picking commit 0fb96b3f.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/testapp-docker.yml

no changes added to commit (use "git add" and/or "git commit -a")

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 4, 2025

Ironbird - launch a network To use Ironbird, you can use the following commands:
  • /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
  • /ironbird start OR /ironbird start --load-test-config= - Launch a testnet with the specified chain and load test configuration.
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 540c7c5 into v1.x Jun 4, 2025
19 checks passed
@mergify mergify bot deleted the mergify/bp/v1.x/pr-5014 branch June 4, 2025 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@zrbecker zrbecker zrbecker approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@melekes melekes

Labels

conflicts

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@zrbecker @melekes