tifastlane - npm Package Compare versions

Comparing version 0.4.4 to 0.4.5

cli.js

		@@ -134,5 +134,7 @@ #!/usr/bin/env node
		.option('-m, --metadata', 'Send only metadata update to Google Play')
		.option('--skip_upload_images', 'Whether to skip uploading images, screenshots not included (SUPPLY_SKIP_UPLOAD_IMAGES)')
		.option('--skip_upload_screenshots', 'Whether to skip uploading SCREENSHOTS (SUPPLY_SKIP_UPLOAD_SCREENSHOTS)')
		.option('--skip_build', 'Skip build of APK')
		.option('-a, --track', 'The Track to upload the Application to: production, beta, alpha or rollout')
		.option('-r, --rollout', 'The percentage of the rollout')
		.option('-a, --track [value]', 'The Track to upload the Application to: production, beta, alpha or rollout')
		.option('-r, --rollout [value]', 'The percentage of the rollout')
		.action(playsend)
		@@ -139,0 +141,0 @@ ;

docs/ANDROID.md

		@@ -98,3 +98,3 @@ ## Setup a Google Developers Service Account

		## Configuration Files
		## Metadata/Screenshot Files

		@@ -129,1 +129,12 @@ All metadata and screenshots are easily maintained from the `TiFLDelivery\APPID\PlayStore` directory.

		## TiFast Configuration

		By default the main configuration settings are stored in a file called `tifastlane.cfg` in your app project root.

		If you want to be able to have multiple configuration files, for example, to login with other credentials, you can override the configuration file to be loaded by using the `-c` param.

		For example:

		tifast send -c otherconfig.cfg

		This will make TiFastlane use the `otherconfig.cfg` file instead of the default `tifastlane.cfg`. All methods accept the configuration override.

docs/IOS.md

		@@ -114,3 +114,3 @@ ## Get Started

		## Configuration Files
		## Metadata/Screenshot Files

		@@ -133,1 +133,13 @@ All metadata and screenshots are easily maintained from the `TiFLDelivery\APPID` directory, here you will find the following files:
		As with metadata, screenshots support multi language. Based on the dimension of the images they will be correctly set to the appropiate device. The images are ordered alphabetically, so make sure to name them correctly to control the right display order.

		## TiFast Configuration

		By default the main configuration settings are stored in a file called `tifastlane.cfg` in your app project root.

		If you want to be able to have multiple configuration files, for example, to login with other credentials, you can override the configuration file to be loaded by using the `-c` param.

		For example:

		tifast send -c otherconfig.cfg

		This will make TiFastlane use the `otherconfig.cfg` file instead of the default `tifastlane.cfg`. All methods accept the configuration override.

index.js

		@@ -781,3 +781,3 @@ var chalk = require('chalk')

		if(opts.development) pemArgs.push('-d');
		if(opts.development) pemArgs.push('--development');

		@@ -788,3 +788,3 @@ if(opts.generate_p12) pemArgs.push('-g');

		if(opts.force) pemArgs.push('-f');
		if(opts.force) pemArgs.push('--force');

		@@ -982,3 +982,20 @@ console.log( chalk.cyan('Starting Pem'));
		}
		else{
		initArgs.push(
		'--skip_upload_apk'
		);
		}

		if( opts.skip_upload_images ){
		initArgs.push(
		'--skip_upload_images'
		);
		}

		if( opts.skip_upload_screenshots ){
		initArgs.push(
		'--skip_upload_screenshots'
		);
		}

		exec('supply', initArgs, { cwd: appAndroidDeliveryDir }, function(e){
		@@ -1005,3 +1022,3 @@ console.log(chalk.green('\nSupply Done\n'));
		console.log(chalk.yellow('Skipping App Build'));
		_supply();
		_supply(1);

		@@ -1008,0 +1025,0 @@ }else{

package.json

README.md

		@@ -51,2 +51,3 @@ # TiFastlane [![npm version](https://badge.fury.io/js/tifastlane.svg)](http://badge.fury.io/js/tifastlane)
		## Changelog
		* 0.4.5 Added support for multiple config files. `playsend` params update.
		* 0.4.1 Minor bug fixes
		@@ -53,0 +54,0 @@ * 0.4.0 Added `supply` to support Google Play Store. Updated to the latest `fastlane` tools.

Improved metrics