Hello all, I am using github action to deploy, act...
# help
b
Hello all, I am using github action to deploy, actually it's taking about 40 minutes, and I want to add some integrations tests which requires running
sst start
so it will take about 1.5 hour to deploy. Actually when running deploy from local machine, it take much fewer time to deploy, I think because there is some caching process in sst I found that there is a caching option for github actions here: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#using-the-cache-action So I want to ask what files and folders should I cache, is
.sst
folder enough?
t
It's probably slow not because of caching but because of the time it takes to spin up brand new aws resources from scratch
Also what verison of sst are you on?
b
I deploy to a used stage, not new, so not all resources are being created I am using 0.62 version
t
It's hard to tell what's slow without examining the build logs
It's unlikely 40min is anything from SST
can you take a look at the logs and see where the time is spent?
b
Actually most time spent on building NextJs constructs, generating pages and optimizing NextJs constructs are in a stack called
Web
and even if I change only functions related to another stack, the building of
Web
runs.
@thdxr @Frank is there ability to make building process runs for only changed stacks? I mean to make building like deployment, it's not deploying non changed stacks, so make it also not building it
t
This is a concept we're thinking about implementing, requires some big changes since cdk doesn't support this concept natively
b
Got it. thanks for your hard working