1
0
Fork 0
mirror of https://gitlab.com/futo-org/fcast.git synced 2025-06-24 21:25:23 +00:00

Resorting to setting build artifact name via environment variable

This commit is contained in:
Michael Hollister 2025-02-20 01:37:08 -06:00
parent f0989c2a50
commit 54dd4146a5
2 changed files with 8 additions and 1 deletions

View file

@ -26,6 +26,13 @@ npm install
For signing the build artifact you must export the following environment variables or set them in your `.env` file:
```
# .env
# Submission requirements need app title to match what is in the web apps' config.xml.
# However, this results in the build artifact name to contain a space. Seems to be weird
# issues with variable expansion/quoting when running the build script in the GitLab CI
# vs running locally, so allowing artifact name to be defined via a environment variable...
ARTIFACT_NAME="'FCast Receiver.wgt'"
CERT_PATH=/app/receivers/tizen/PATH_TO_CERTS
CERT_IDENTITY=YOUR_IDENTITY
CERT_AUTHOR_PASSWORD=YOUR_PASSWORD

View file

@ -25,6 +25,6 @@ tizen security-profiles add --active --force --name $CERT_IDENTITY --author $CER
tizen cli-config "profiles.path=/home/ubuntu/tizen-studio-data/profile/profiles.xml"
sed -i "s|$CERT_PATH/author/$CERT_IDENTITY/author.pwd|$CERT_AUTHOR_PASSWORD|g" /home/ubuntu/tizen-studio-data/profile/profiles.xml
sed -i "s|$CERT_PATH/SamsungCertificate/$CERT_IDENTITY/distributor.pwd|$CERT_DIST_PASSWORD|g" /home/ubuntu/tizen-studio-data/profile/profiles.xml
../../scripts/package.sh tizen package -t wgt -s $CERT_IDENTITY -r ../../FCastReceiverService/bin/Release/netcoreapp2.1/com.futo.FCastReceiverService-1.0.0.tpk -- "'FCast Receiver.wgt'"
../../scripts/package.sh tizen package -t wgt -s $CERT_IDENTITY -r ../../FCastReceiverService/bin/Release/netcoreapp2.1/com.futo.FCastReceiverService-1.0.0.tpk -- $ARTIFACT_NAME
cd ../../