You can create a new build command, select the options you want and click the Build button to generate the OneScript release file for you. At this point you can also give this build command a name and save it to your OneScript server. This way it can be reused later, used by other OneScript Clients or run from a command line.
There is only 1 required parameter to run a build command from the command line. The -s parameter, the ID of the OneScript server connection definition (which may be different on different OneScript Clients) The OneScript server connection definition that you are currently using to connect to the OneScript server is displayed in the top right hand corner of the window and its ID is in parenthesis. The server connection definition shown in the image below is named "First" and its ID is 1.
If I expand the Command Line section of the editing page I will see the command line to run the build command I'm currently editing and it will show the command's ID (-c) which can be the second command line parameter. This doesn't change on different OneScript clients since it is stored on your OneScript server.
So the command below just says use the OneScript Client's server connection definition with the ID of 1 and get the build command with the ID of 2, then run it.
OneScript will create your build using the options saved in your command. You can override any of the options at the command line with override parameter.
After showing you the command line to run your build command we show you the equivalent selections using command line overrides. If you ever need to create overrides you could just make your selections in the editor and then copy the overrides from here.
If you select an override for each of the groupings shown above, you don't even need the -c parameter.
If requests are included in your build a file will be excluded if it is in a request to exclude even if it would have been included with another option.
The overrides allow you to have total control over the build from the command line.