Add a command for cloud-build

[joehoyle]

So people can more easily test the builds as if there were in cloud, I've added a command that will run their .build-script using the same build-container that we used in CodeBuild.

[rmccue]

Is it possible to have this build into a temp-/sub-directory instead of overwriting the current dir?

[rmccue]

Suggestion: check-build?

[tfrommen]

Why not just build?

[kovshenin]

I think the intention is to test that a build runs without errors, and doesn't actually produce a build that can be deployed to Altis, so build may be a bit misleading.

[kovshenin]

Is it possible to have this build into a temp-/sub-directory instead of overwriting the current dir?

I was going to ask the same and went down a rabbit hole into how to force a volume mount with an overlay filesystem. Turned out to be a bit trickier than I though, but copying into a non-host directory and running the build there would also be okay I suppose.

[rmccue]

Turned out to be a bit trickier than I though, but copying into a non-host directory and running the build there would also be okay I suppose.

Yeah, I'd copy it probably.

[joehoyle]

Hmm yeah if we want this to be a "readonly" operation, we'd need to do things a bit differently. We could increase the scope to run the "build process" from Altis Cloud (not just the build script), so that would mean: git clone, etc. In a subdir that's cleaned up afterwards or something. We could copy the entire working directory, but we'd want to exclude things like uploads, and existing node_modules could present another area of "not like for like" with production.

[kovshenin]

That's one of the reasons I was hoping to have an overlay filesystem. With git clone it would mean that any changes have to be committed and pushed before testing, and the biggest advantage of having this available in Local Server is being able to test builds before committing your work.

Doing a copy and excluding things in .gitignore may be a good balance.

[rmccue]

What if we make it the user's choice? By default, cp -r the working directory; allow a --commit[=HEAD] option.

[kovshenin]

Wouldn't the commit still have to exist in the remote? And if so, wouldn't it likely already have a remote build available/running in Vantage?

[rmccue]

Not necessarily, it can use your local commits which may not have been pushed; additionally, you're likely pushing to a feature branch which isn't getting built in Vantage, not one of the deploy branches.