Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: manually callable workflow to build .wasm binaries using cosmwasm/rust-optimizer #70

Closed
Tracked by #7
Unique-Divine opened this issue Aug 29, 2023 · 1 comment · Fixed by #107
Closed
Tracked by #7
Assignees
Labels
ci GitHub actions or other continuous integration changes type: enhancement New feature or request

Comments

@Unique-Divine
Copy link
Member

Unique-Divine commented Aug 29, 2023

Desired Dev X

Suppose that my machine doesn't have the right architecture to generate Wasm bytecode intended for production. This could be Windows without WSL or a Darwin (MacOS) architecture that could result in nondeterminism.

As a workaround, there should be an easy way me to:

  1. Push Rust code for contracts that I'm certain will compile to a branch
  2. Start a pull request for that branch with the changes
  3. Manually trigger or request a repo owner to trigger a workflow that generates the Wasm bytecode (for production) and then publishes it as an artifact for that branch

Then, I can download the artifacts and checksums to include in the pull request.

@Unique-Divine Unique-Divine added type: enhancement New feature or request ci GitHub actions or other continuous integration changes labels Oct 27, 2023
@Unique-Divine Unique-Divine self-assigned this Nov 20, 2023
@Unique-Divine
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci GitHub actions or other continuous integration changes type: enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant