You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We shouldn't need Ruby installed on the runner, and again the container just to be able to build Ruby versions. This commit moves functionality that doesn't **need** to be in Ruby to bash. This is needed as ruby/setup-ruby does not currently work with ARM ruby/setup-ruby#577.
Copy file name to clipboardExpand all lines: README.md
+2-23
Original file line number
Diff line number
Diff line change
@@ -53,30 +53,9 @@ This build tool supports heroku's multiple stacks. The built rubies will go in t
53
53
54
54
### Building
55
55
56
-
First we'll need to generate the docker images needed for building the appropriate stack.
57
-
58
-
```sh
59
-
$ bundle exec rake "generate_image[heroku-22]"
60
-
```
61
-
62
-
Generate a ruby build script:
63
-
64
-
```sh
65
-
$ bundle exec rake "new[3.1.3,heroku-22]"
66
56
```
67
-
68
-
From here, we can now execute a ruby build:
69
-
70
-
```
71
-
$ bash rubies/heroku-22/ruby-3.1.3.sh
72
-
```
73
-
74
-
When it's complete you should now see `builds/heroku-22/ruby-3.1.3.tgz`.
75
-
76
-
If you set the env vars `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, you can upload them to s3. By default, we upload to the `heroku-buildpack-ruby` s3 bucket.
0 commit comments