For all the devs out there... We're currently stru...
# generalk
King Leung
09/30/2019, 3:18 PMFor all the devs out there... We're currently struggling to implement both GitHub and SDF concurrently. We only have the following prerequisites: 1. We would like to use the IDE Deploy to Account feature (we have a total of 6 SBX). 2. We would like to keep the GitHub master repo as a mirror of our Prod SuiteScript folder. 3. We would like a streamlined method where we would not have to copy files and only submit the JS for code review.
King Leung
09/30/2019, 3:34 PMAnyone in large Dev org please chime in... It would be greatly appreciated.
r
Richard Tanner
09/30/2019, 5:17 PMWe use the Gitflow branching strategy. Basically we keep all of our suitescript code in a single repo. Any active development is done in either a feature or hotfix branch and then merged once complete. Merging to the Develop or Master branch is always done through a pull request so a code review can be performed. Anything merged to master is production ready code so the master branch should always mirror the code that is in NS Production and should be deployable at any time.
https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
Richard Tanner
09/30/2019, 5:19 PMUploading code files which are being actively worked on can be challenging with this approach. We use the Deploy to Account feature to deploy to production but we can't really use it to deploy to our dev environment without risking overwriting someone else's work. For the time being we are manually copying the code into Netsuite which is a little clunky. I know there is some work being done to update the tooling so this will hopefully be a temporary problem.
s
Seth Duda
09/30/2019, 5:51 PMSDF works ok when you have one person working on the code/config in a specific SDF project. However, I agree, it completely breaks down when you have multiple people trying to work concurrently, all trying to update the same dev/sb account.
k
King Leung
10/01/2019, 12:13 PMThanks for the input.