Create a script to create a build drop to enable running functional tests on boxes that didn't build the product. #466
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| #!/bin/bash | ||
|
|
||
| . "$(dirname ${BASH_SOURCE[0]})/../InitializeEnvironment.sh" | ||
|
|
||
| CONFIGURATION=$1 | ||
| BUILDDROP_ROOT=$2 | ||
| if [ -z $BUILDDROP_ROOT ] || [ -z $CONFIGURATION ]; then | ||
| echo 'ERROR: Usage: CreateBuildDrop.sh [configuration] [build drop root directory]' | ||
| exit 1 | ||
| fi | ||
|
|
||
| # Set up some paths | ||
| BUILDDROP_BUILDOUTPUT=$BUILDDROP_ROOT/BuildOutput | ||
| BUILDDROP_SRC=$BUILDDROP_ROOT/src | ||
| BUILDDROP_PROJFS=$BUILDDROP_SRC/ProjFS.Mac | ||
| BUILDDROP_KEXT=$BUILDDROP_BUILDOUTPUT/ProjFS.Mac/Native/Build/Products/$CONFIGURATION | ||
|
|
||
| # Set up the build drop directory structure | ||
| rm -rf $BUILDDROP_ROOT | ||
| mkdir -p $BUILDDROP_BUILDOUTPUT | ||
| mkdir -p $BUILDDROP_SRC | ||
| mkdir -p $BUILDDROP_PROJFS | ||
| mkdir -p $BUILDDROP_KEXT | ||
|
|
||
| # Copy to the build drop, retaining directory structure. | ||
| rsync -avm $VFS_OUTPUTDIR/Git $BUILDDROP_BUILDOUTPUT | ||
| rsync -avm $VFS_PUBLISHDIR $BUILDDROP_ROOT | ||
| rsync -avm $VFS_SCRIPTDIR $BUILDDROP_SRC/Scripts | ||
| rsync -avm $VFS_SRCDIR/ProjFS.Mac/Scripts $BUILDDROP_PROJFS | ||
|
There was a problem hiding this comment. Should this keep the There was a problem hiding this comment. It keeps the script folders so that we can keep the logic on how we run functional tests or install/start the kext encoded in the script. |
||
| rsync -avm $VFS_OUTPUTDIR/ProjFS.Mac/Native/Build/Products/$CONFIGURATION/PrjFSKext.kext $BUILDDROP_KEXT | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are cases in the build scripts that use
sudo. How do we know when we will need to use that vs not?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm making the assumption in this script that the CI agent will have access to wherever it is asked to publish the drop. Also, this caught my clumsiness a few times where I fat fingered /[something] instead of ~/[something].