cargo pipeline error #1582
Comments
|
Same thing with Docker:
|
|
A few more debug logs: |
|
@ckoehler where is the source that you're trying to build, generally we checkout a project using git-checkout that we want to build. I don't see a git-checkout in your config, you can use maybe fetch too if you want to pull a tarball. You'll be able to find examples for fetch in wolfi repository. Let me know if you are able to make some more progress after this. There's also a useful |
|
It's the current directory, mapped into |
|
Maybe there's also a workflow problem? I am usually packaging local apps in CI, so the source is available from a git checkout already, no need to fetch anything remotely. What's the best way to do that? |
|
@ckoehler the honest answer for now is that I lack this context as of now. I've never tried building local packages, I can look into this tomorrow if it's possible but generally whole packages fetch the source code from internet and build it from source. I'll look into this tomorrow if this is still an issue that's not solved. |
|
Here's a self-contained yaml file that pulls and builds a project from git. The cargo build is successful, but the package generation isn't. package:
name: probe
version: 0.1.0
description: probe
copyright:
- license: MIT
dependencies:
runtime:
environment:
contents:
keyring:
- https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
repositories:
- https://packages.wolfi.dev/os
packages:
pipeline:
- uses: git-checkout
with:
expected-commit: 5092046571b4791f68a47c29527a14d6d57aee3a
repository: https://github.com/ckoehler/probe.git
tag: v0.2.2
- uses: cargo/build
I built it with Docker and the dev-container method, including |
|
@ckoehler this should keep you moving. package:
name: probe
version: 0.1.0
description: probe
copyright:
- license: MIT
environment:
contents:
packages:
- build-base
pipeline:
- uses: git-checkout
with:
expected-commit: 5092046571b4791f68a47c29527a14d6d57aee3a
repository: https://github.com/ckoehler/probe.git
tag: v0.2.2
- uses: cargo/build
with:
output: probeNotes about why it was failing can be read in this PR notes: #1596 I saw you've two binaries But this is something where we plan to improve in the future as we plan to adopt Thanks for being patient. |
|
Ah interesting! The actual repo I have trouble with actually has no binaries, but a couple of libraries (rlib). Does the same thing apply to that case? |
|
I guess it does, I didn't know the |
melange is giving an error even tho the build is successful.
Log
Reproduce
Create a new Rust project, the default works.
cargo new melange-test; cd melange-testCreate a melange file with this content:
Build:
melange build --arch amd64 test.yamlArch doesn't matter, just keeping the output shorter.
aarch64also fails.Version
The text was updated successfully, but these errors were encountered: