Run the command ./bin/fhc.js build and check if the windows options/type will appears
cmacedo@camilas-MBP ~/work/fh-fhc (RHMAP-21057) $ ./bin/fhc.js build
Usage:
fhc build --project=<project> --app=<app> --cloud_app=<cloud_app> [--tag=<tag>]
--environment=<environment> --destination=<destination> [--version=<version>]
[--config=<config>] [--privateKeyPass=<privateKeyPass>] [--certpass=<certpass>]
[--download=<download>] [--bundleId=<bundleId>]
[--cordova_version=<cordova_version>] [--git-tag=<git-tag>]
[--git-branch=<git-branch>] [--git-commit=<git-commit>] [--json=<json>]
Options:
--help Show help [boolean]
--version, -v Specific to the destination (e.g. Android version
4.0). [boolean]
--project, -p Unique 24 character GUID of the project. [required]
--app, -a Unique 24 character GUID of the client app which will
be built. [required]
--cloud_app, --ca Unique 24 character GUID of the cloud app which the
client app will connect to. [required]
--tag, -t The name of a connection tag for the cloud app, must
be in Semantic Version format, e.g. 0.0.1. See:
http://semver.org.
--environment, -e The id of a target environment, e.g. dev. [required]
--destination, -d One of: android, iphone, ipad, ios(for universal
binary), blackberry [required]
--config, -c Either 'debug' (default), 'distribution', or
'release'.
--privateKeyPass, --pk Private key password of the bundleId, only needed for
'release' builds.
--certpass, --cp Certificate password.
--download, --dw Boolean value to inform to download or not the built
when it finish.
--bundleId, -b The unique bundle identifier of the credential
bundle. You can get it using 'fhc credentials list'.
Required for all iOS builds.
--cordova_version, --cv For specifying which version of Cordova to use.
Currently supported: either 2.2 or 3.3. Only valid
for Android for now.
--git-tag, --gt Long value of URL that you want shorter for the
henr.ie URL.
--git-branch, --gb The name of the git branch to build, defaults to
'master'.
--git-commit, --gc The full hash of the commit to build, if not the head
of the branch. Must be used with <branch name>.
--json, -j Output into json format
Examples:
fhc build --project=<project> Build a client <app> of the
--app=<app-id> <project> connect to the <cloud_app>
--cloud_app=<cloud-app-id> --tag=<tag> deployed into the <environment>
--environment=<environment>
--destination=<destination>
--version=<version>
--config=<release|distribution>
--privateKeyPass=<private-key-password>
--certpass=<certificate-password>
--download=<true|false>
--bundleId=<credential bundle id>
--cordova_version=<cordova version>
--git-tag=<tag name>
--git-branch=<branch name>
--git-commit=<commit hash>
Run the command ./bin/fhc.js ups variant add and check if some Win option will appears.
cmacedo@camilas-MBP ~/work/fh-fhc (RHMAP-21057) $ ./bin/fhc.js ups variant add
Usage:
fhc ups variant add --app=<app> --name=<name> --type=<type>
[--serverKey=<serverKey>] [--senderId=<senderId>] [--production=<production>]
[--passphrase=<passphrase>] [--certificate=<certificate>] [--json=<json>]
Options:
--help Show help [boolean]
--version Show version number [boolean]
--app, -a Unique 24 character GUID of your application.[required]
--name, -n Name of the variant. [required]
--type, -t Type of the variant. Choose from:
- android
- ios
[required]
--serverKey, --sk Server Key to use Android Firebase Cloud Messaging
(E.g. AIza5a448c2f31700a466fbc9d33d33942b043a27596)
--senderId, --si Sender ID to use Android Firebase Cloud Messaging
(E.g.contact@email.com)
--production, -p To inform if is a production certificate to use the
Apple Push Network. Default value is false.
--passphrase, --pp Password of the certificate to use the Apple Push
Network
--certificate, --cert Path with the name of the iOS certificate file, *.p12,
to use the Apple Push Network.
--json, -j Output in json format
Examples:
fhc ups variant add --app=<appId> Add Android variant for the <appId>
--name=<name> --type=android with the <name>, and <serverKey> and
--serverKey=<serverKey> <senderId>
--senderId=<senderId>
fhc ups variant add --app=<appId> Add Android variant for the <appId>
--name=<name> --type=ios with the <name>, and <production>
--production=<true|false> and <passphrase>
--passphrase=<passphrase>
--certificate=<certificate>
Run the command ./bin/fhc.js ups variant delete and check if some win option will appears.
cmacedo@camilas-MBP ~/work/fh-fhc (RHMAP-21057) $ ./bin/fhc.js ups variant delete
Usage:
fhc ups variant delete --app=<app> --id=<id> --type=<type> [--json=<json>]
Options:
--help Show help [boolean]
--version Show version number [boolean]
--app, -a Unique 24 character GUID of your application. [required]
--id, -i Variant ID which should be removed. To get this value use $fhc ups
variant list --app=<app> [required]
--type, -t Type of the variant. Choose from:
- android
- ios
[required]
--json, -j Output in json format
Examples:
fhc ups variant delete --app=<appId> Delete the variant with <id> from
--id=<id> the <appId>
Checklist:
[x] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member
Jira link(s)
https://issues.jboss.org/browse/RHMAP-21057
What
Remove Windows feature/options
Why
Windows feature are not so long supported.
How
grunt potupload
taskVerification Steps
./bin/fhc.js build
and check if the windows options/type will appears./bin/fhc.js ups variant add
and check if some Win option will appears../bin/fhc.js ups variant delete
and check if some win option will appears.Checklist: