kos don't seem to infer main from build correctly

[eddycharly]

What happened?

We tried to use the kos section to build images with a main.go in a subfolder of the repo.

We specified main in the build and referenced the build from the kos section but it doesn't seem to infer the setting.

See https://github.com/kyverno/chainsaw/blob/main/.goreleaser.yaml

How can we reproduce this?

The config file we use is visible at https://github.com/kyverno/chainsaw/blob/main/.goreleaser.yaml

Failing run logs https://github.com/kyverno/chainsaw/actions/runs/6638453325/job/18034825927

goreleaser version

v1.21.2

GoReleaser Check

• goreleaser check shows no errors

Search

• I did search for other open and closed issues before opening this

Supporter

• I am a sponsor or a Pro customer

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

No response

[caarlos0]

I'll take a look when I get some time, thanks for reporting 🙏

[eddycharly]

Thanks @caarlos0

I managed to make it work, using kos requires that the build is configured in a way that is compatible with the ko tool though.

[eddycharly]

This config works https://github.com/kyverno/chainsaw/blob/main/.goreleaser.yaml

Notable change is the way main is specified in the build config https://github.com/kyverno/chainsaw/blob/9b1a85b2da6c064b3582454b462c608e64bc1836/.goreleaser.yaml#L14

[caarlos0]

ah, yes, the build goes a step further trying to look for main funcs in the cwd, which I guess ko does not.

Probably we could run this (the checkMain func) in the builder Default method so it passes down to ko too.

[eddycharly]

Looks like ko expects a relative path to a folder, things like cmd, cmd/main.go or ./cmd/main.go don't seem work with ko, only ./cmd (in my case).

A more strict validation with a useful message explaining what is wrong would be great.
Or just some words about that in the docs ?

[caarlos0]

ah, gotcha, I think probably try to validate it better + docs

[caarlos0]

can probably add a validation regex to the yamlschema, too

[gabrielcipriano]

In builds.main The path must always be relative? or only when used with Ko?

[eddycharly]

In builds.main The path must always be relative? or only when used with Ko?

It's a ko requirement, I don't think it applies when ko is not used.