You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: have configuration .soos # YAML, JSON, JS
Motivation: environment specific configuration without the need to pass details as --arguments
Output: execute one soos <target-name> use .soosrc
possible targets: build, compile, clean, server
Example for compile target leveraging branch-specific configuration:
Git hook will trigger soos compile on CI agent - specific .soosrc located in the cloned branch
generate SHA1 for the current version package.json / (optionally shrinkwrap)
soos will check if the image with tag on the registry (official or private)
if not found build the image and push it to the registry
use pulled/created image for building the project by mounting the -v $(pwd):/${soosrc.containerFolder}
execute npm run compile inside the container and place output into /${soosrc.distFolder}
Benefits: user soos config file for
adding specifics when building the Dockerfile (folders, etc)
registry location (public, private)
image name pattern
settings when building the docker run string
variables
The text was updated successfully, but these errors were encountered:
Goal: have configuration .soos # YAML, JSON, JS
Motivation: environment specific configuration without the need to pass details as --arguments
Output: execute one
soos <target-name>
use .soosrcpossible targets: build, compile, clean, server
Example for compile target leveraging branch-specific configuration:
soos compile
on CI agent - specific .soosrc located in the cloned branch-v $(pwd):/${soosrc.containerFolder}
npm run compile
inside the container and place output into /${soosrc.distFolder}Benefits: user soos config file for
The text was updated successfully, but these errors were encountered: