build-image icon indicating copy to clipboard operation
build-image copied to clipboard

This is the build image used for running automated builds

Results 139 build-image issues
Sort by recently updated
recently updated
newest added

**Is your build failing?** No. **Describe the bug** As I reported in [this topic](https://answers.netlify.com/t/target-directory-for-rust-is-not-stored/74736), copying the `target` directory is always failed. It seems the copy command defined in `fast_copy_cache` ([here](https://github.com/netlify/build-image/blob/focal/run-build-functions.sh#L789))...

type: bug

#### Summary Fixes #485. Projects that contain a `deps.edn` file are compiled by the [Clojure CLI](https://clojure.org/reference/deps_and_cli). (This is analogous to a Gemfile, which signals that a project is built with...

> TODO... On the plus side, the guide is really short and easy to abide by 😄

According to https://github.com/netlify/build-image/issues/118#issuecomment-364566072, > The only piece that happens "outside that" is the initial git clone which creates the repository directory and happens using the deploy key that is installed...

Hi, If we try to build a repo that has Cypress NPM dependency, the `npm install` step takes several minutes because each install caches only NPM node modules, but Cypress...

https://github.com/netlify/build-image/blob/30f629161c0736b1a3ecd8b418e5eeffab5c0faf/run-build-functions.sh#L440 I thing this command build for debug by default, this should be done by using `swift build -c release` instead. This has a huge performance impact (using release can...

It would be really cool if there was support for [Haskell](https://www.haskell.org/) so that people could build their [Hakyll](https://jaspervdj.be/hakyll/) static sites through Netlify!

Hey there 👋 There's currently some issues Netlify users are experiencing connecting their projects with the Github package repository and private packages. See [this](https://community.netlify.com/t/support-guide-using-private-npm-modules-on-netlify/795/30). The problem is that you need...

I have this configuration ``` [build] base = "" publish = "dist/" command = "yarn build-prod" environment = { YARN_VERSION = "1.22.4", NODE_ENV = "production", NODE_VERSION = "12" } ```...

It doesn't look like the Go dependency cache is actually being persisted. Note how at the start of the build `$(GOPATH)/pkg` is always empty, gets filled with dependencies, and then...