This change incorporates deployer 4.0.0, which makes local and remote builds more equivalent to each other in the matter of where material can be referenced and fetched from outside the build directory.
With this change, both local and remote builds can refer only within their own directory plus, optionally, a directory called lib located at the project root. This is an enhancement for remote builds, but a restriction for local ones.
If the lib directory immediately contains a build script (e.g. lib/build.sh), it will be run before any other build is run. Build scripts located at further depth (e.g. lib/builds/build.sh) will not have that property but can be used as subroutines of other build scripts, including action an web build scripts.
This change incorporates deployer 4.0.0, which makes local and remote builds more equivalent to each other in the matter of where material can be referenced and fetched from outside the build directory.
With this change, both local and remote builds can refer only within their own directory plus, optionally, a directory called
liblocated at the project root. This is an enhancement for remote builds, but a restriction for local ones.If the
libdirectory immediately contains a build script (e.g.lib/build.sh), it will be run before any other build is run. Build scripts located at further depth (e.g.lib/builds/build.sh) will not have that property but can be used as subroutines of other build scripts, including action anwebbuild scripts.