Boeing
Build and distribute config-file-validator rpm
Build an RPM for the config-file-validator and go through the process of getting it added to Fedora. After it's been added to Fedora it can be added to EPEL
@kehoecj Thanks for the validator, I am looking forward to use this project for linting YAMLs.
I released a minor version of config-file-validator on a fork here
It uses goreleaser to build tarballs, debian and rpm packages. It uses goreleaser integration with ko to build container images for arm64 and amd64 platform.
Let me know if there are any comments on this and if you want to proceed ahead with goreleaser. I'll create a PR afterward.
@kranurag7 Thanks for taking a look at this - we're using go-release-action now (thanks to @LeslieLeung). Would this be able to integrate with that to produce the RPM's and DEB's?
@kehoecj I think we cannot de that with go-release-action. It seems they only support releasing binaries wrapped in .zip or tarballs.
@kranurag7 does goreleaser support our current releases (windows/Linux/macOS binaries) in addition to .deb and .rpm or can we use both goreleaser and go-release-action together in separate jobs/stages?
Yes, goreleaser do support binaries including debs and rpms.
Regarding using together, I think it'll be good if only one of the job having contents: write permissions writes to the releases page. But theoretically, yes, it seems doable where we will have one job using go-release-action and another job running goreleaser.
Okay great - sounds like we can just go with goreleaser then. If you can modify what you have on your fork to include the output of the current release job then I think that will be ready for submission