I’m curious how everyone structures their SDF proj...
# suitescript
c
I’m curious how everyone structures their SDF projects / customizations. Do you house everything in a single project, or multiple projects? Do you have seperate git repos for each project, or one for all of them? I would like to consolidate all of our stuff into a single project, however the deployments seem to take forever once the project gets too large. However, opening and juggling multiple projects seems messy, especially when there is a lot of overlap in the functionality between each one
s
we strive to keep things as simple as possible but no simpler. For us that means starting with a single SDF project. We use a feature branch for new development and adjust the deploy.xml, commenting out other entries not related to the feature being developed. This keeps deployment for that feature lean and mean.
upon completion of the feature, we merge (including the
deploy.xml
that reflects just the artifacts needed for that feature) to master
we then tag the repo so we can always get back to 'what was deployed as of tag XXX'
if a feature gets complex enough we can put it in a subfolder then make that subfolder an SDF project root.
d
we are going through this process right now... we have a single monolithic repo, several developers pushing feature branches and deploying to dev/qa/prod environments. Looking to use github-actions or aws-codebuild to run suitecloud to deploy for me