https://www.prisma.io/ logo
Join Slack
Powered by
Hello all, I’m running into an issue in an enterpr...
# prisma-client
a
Hello all, I’m running into an issue in an enterprise Jenkins environment where it seems trying to reach 
<https://binaries.prisma.sh>
will hang until an 
ETIMEDOUT
error during a 
yarn install
My options are limited, and in parallel trying to figure out the network security on the jenkins env to figure out how to get past this issue, but in the meantime, I’m trying to understand how I can work around this by using Engine environment variables.
I am working out of a darwin environment, and the application is deployed to an AWS Lambda environment. So my binaryTargets has been set to 
binaryTargets = [“native”, “rhel-openssl-1.0.x”]
This downloads the following binaries: 
node_modules/prisma/engines/<somesha>/libquery_engine-darwin.dylib.node
and 
node_modules/prisma/engines/<somesha>/libquery_engine-rhel-openssl-1.0.x.so.node
As I understand, these are library binaries.
My goal now is prevent the install script from reaching out to 
<https://binaries.prisma.sh>
because that is the culprit issue that hangs my 
yarn install
command. So my hope is that, by specifying the location of a locally downloaded binary, that the postinstall script will just ignore needing to download any of the binaries.
I’ve decided to store the 
rhel-openssl
binary right inside my repo in a 
prisma/engines
folder at the top level of my application. So this means, I should set 
PRISMA_QUERY_ENGINE_LIBRARY=/path/to/app/prisma/engines/libquery_engine-rhel-openss-1.0.x.so.node
Now even though I have this env set in the Jenkins job, the install script still seems to go out and tries to download binaries that I don’t even need to build my application. Does this mean I need to set all the environments for every single engine env? Then the postinstall script won’t attempt to download them?
n
Open in Slack
PreviousNext
Powered by