pipelines/ruby: add new test pipelines

[Dentrax]

This PR adds new pipelines for Ruby:

• ruby/test
• ruby/require

Example usages:

- uses: ruby/test
  with:
    command: ruby -e "require 'json'"

- uses: ruby/require
  with:
    require: json

- uses: ruby/require
  with:
    requires: |
      require 'json'

[EyeCantCU]

This is great. Left a few comments. Can we also document the usage of the pipeline in melange's docs?

[EyeCantCU]

I think we should get rid of this. We're not doing anything inherently specific to Ruby

[Dentrax]

It seems we have name: field defined on each pipeline, do you say we should omit this field?

[EyeCantCU]

Sorry, the pipeline. It looks like it does the same thing a runs would do

[EyeCantCU]

Wolfi base is implicit. We don't need to define it

[EyeCantCU]

We should add Ruby here, passed as an input. See go/build for what I'm talking about

[Dentrax]

I just checked the other Ruby pipelines and it seems we didn't include the Ruby, was wondering if there was any reason. 🤔

[EyeCantCU]

I don't think it'd ever been considered that pipeline should fetch the toolchain. go/build didn't offer this functionality until a few months ago either. We should provide it because it's helpful, and we can implicitly pull in ruby without defining it in the environment

[Dentrax]

That makes sense, I've added Ruby here and couldn't pass the CI error: https://github.com/chainguard-dev/melange/actions/runs/10788637898/job/29919880644?pr=1483#step:9:1071 - for some reason, it doesn't find ruby-3.2 even its there.

[EyeCantCU]

I don't think this applies to the rest of the pipeline

[Dentrax]

This is a copy-paste thing from python/import pipeline actually. I'm checking the CI logs here but couldn't see the instructions either.

[EyeCantCU]

Yeah, happy to be wrong here, but I don't believe it's transient to the rest of the pipeline. Will let someone that knows for sure chime in

[smoser]

it does "apply", in that it turns off '-x' option (making it not spew bash debug to stderr).

[smoser]

with regard to the error you're seeing [here]:

 2024/09/10 09:27:54 INFO running step "Test a Ruby package require, with optional load clause"
2024/09/10 09:27:54 WARN /bin/sh: ruby-3.2: not found
2024/09/10 09:27:54 INFO ruby-3.2 -e "require 'json'": FAIL
2024/09/10 09:27:54 INFO ERROR: failed to test package. the test environment has been preserved:
2024/09/10 09:27:54 INFO   workspace dir: /tmp/melange-workspace-1987892197
2024/09/10 09:27:54 INFO   guest dir: /tmp/melange-guest-1360058723

A couple things:

1. ruby-3.2 does not provide an executable named 'ruby-3.2'. The package is
   named ruby-3.2 but it only provides /usr/bin/ruby. So thats why you get
   'ruby-3.2' command not found.

2. If the 'inputs.ruby' is providing the package rather than an executable
   name (in python it provides an executable name), to install, and we are assuming that a ruby (ruby-3.X) package will always install /usr/bin/ruby, then you can ditch the searching for a binary (lines 43-57 entirely), and make 'RUBY='ruby' on line 29.

3. in e2e-tests/ruby3.2-json-test.yaml you should actually drop the 'packages:' section, because the 'needs' should fulfill that.

[Dentrax]

Thank you so much @smoser! I just updated the PR and hit a new issue:

ruby-3.2-3.2.4-r1.apk disqualified because ruby-3.3-3.3.5-r1.apk already provides cmd:erb

That's probably due to I set ${{inputs.ruby}}=ruby so it installs the ruby-3.3 (latest) whereas I have ruby-3.2 in the test pipeline. But I'd like to set ruby-3.2 as a default package since most of Wolfi packages using this version. That's why I had to set default: ruby-3.2.