tifastlane - npm Package Compare versions

Comparing version 0.1.0 to 0.2.0

bin/tifastlane.js

@@ -40,6 +40,2 @@ #!/usr/bin/env node
 
-        var appDeliveryDir = deliveryDir + '/' + tiapp.id;
-        var appDeliveryMetaDir = appDeliveryDir + '/metadata/en-US';
-        var appDeliveryScreenDir = appDeliveryDir + '/screenshots/en-US';
-
         //Create delivery directory if it doesn't exist
@@ -102,4 +98,2 @@ if (!fs.existsSync(appDeliveryDir)){
 
-        var appDeliveryDir = deliveryDir + '/' + tiapp.id;
-
         //Create delivery directory if it doesn't exist
@@ -131,4 +125,2 @@ if (!fs.existsSync(appDeliveryDir)){
 
-        var appDeliveryDir = deliveryDir + '/' + tiapp.id;
-
         if (!fs.existsSync(appDeliveryDir + "/Deliverfile")){
@@ -141,3 +133,4 @@ console.log(chalk.red('You need to initialize the "deliver" settings.'));
         var initArgs = [
-            'upload_metadata'
+            'upload_metadata',
+            '--skip-deploy'
         ];
@@ -156,2 +149,74 @@
 
+    function sendapp(){
+
+        if (!fs.existsSync(appDeliveryDir + "/Deliverfile")){
+            console.log(chalk.red('You need to initialize the "deliver" settings.'));
+            program.help();
+            return;
+        }
+
+        var newFileContents = "";
+        var _hasipa = false;
+
+        fs.readFileSync(deliverFile).toString().split('\n').forEach(function (line) {
+
+            if( /^ipa /.test(line) ){
+                _hasipa = true;
+                newFileContents = newFileContents + 'ipa "../../build/' + tiapp.name + '.ipa"' + "\n";
+            }
+            else{
+                newFileContents = newFileContents + line + "\n";
+            }
+            //fs.appendFileSync(deliverFile, line.toString() + "\n");
+        });
+
+        if( !_hasipa ){
+            newFileContents = newFileContents + 'ipa "../../build/' + tiapp.name + '.ipa"' + "\n";
+        }
+
+        fs.writeFileSync(deliverFile, newFileContents);
+
+        var buildArgs = [
+            'build',
+            '-p', 'ios',
+            '-T', 'dist-adhoc',
+            '-O', './build'
+        ];
+
+        function _deliver(){
+            
+            console.log("\n");
+            console.log(chalk.yellow('Starting deliver'));
+
+            var initArgs = [
+                'run'
+            ];
+
+            if( program.skip_verify ){
+                initArgs.push('--force');
+            }
+
+            exec('deliver', initArgs, { cwd: appDeliveryDir }, function(e){
+                console.log(chalk.green('Done'));
+            });            
+        }
+
+        if( program.skip_build ){
+            console.log(chalk.yellow('Skipping Titanium App Store Build'));
+            _deliver();
+        }
+        else{
+
+            console.log(chalk.yellow('Starting Titanium App Store Build'));
+            console.log("\n");
+
+            exec('titanium', buildArgs, null, function(e){
+                _deliver();
+            });
+
+        }
+
+    }
+
+
     function register(platform) {
@@ -251,2 +316,3 @@
         .option('--updatemeta', 'Update metadata and screenshots on iTunes Connect')
+        .option('--sendapp', 'Send new App version to iTunes Connect')
         .option('-f, --force', 'On register it forces the provisioning profiles to be renewed')
@@ -257,2 +323,3 @@ .option('-i, --skip_itc', 'Skip the creation of the app on iTunes Connect')
         .option('--skip_verify', 'Skip verification of metadata on update')
+        .option('--skip_build', 'Skip build of App Store ipa')
 
@@ -285,2 +352,8 @@ program.parse(process.argv);
 
+    //Path Dirs
+    var appDeliveryDir = deliveryDir + '/' + tiapp.id;
+    var deliverFile = appDeliveryDir + "/Deliverfile";
+    var appDeliveryMetaDir = appDeliveryDir + '/metadata/en-US';
+    var appDeliveryScreenDir = appDeliveryDir + '/screenshots/en-US';
+
     // check for a new version
@@ -304,2 +377,5 @@ updateNotifier({
     }
+    else if( program.sendapp ){
+        sendapp();
+    }
     else if( program.register ){
@@ -306,0 +382,0 @@ register(program.args[0]);

package.json

 {
   "name": "tifastlane",
-  "version": "0.1.0",
-  "description": "Integrating fastlane.tools into Titanium Development",
+  "version": "0.2.0",
+  "description": "iOS Continuos Deployment support for Titanium using fastlane.tools. With TiFastlane you'll be able to fully optimize the way you submit your app updates and maintain your certificates and provisioning profiles on the App Store.",
   "main": "index.js",
@@ -6,0 +6,0 @@ "bin": {

README.md

@@ -1,11 +0,12 @@
-# TiFastlane
+# TiFastlane [![Twitter: @ulizama](https://img.shields.io/badge/[e-mail]?style=flat)](https://twitter.com/ulizama)
 
-A wrapper to the awesome [fastlane.tools](https://fastlane.tools/) so you can use them seamlessly with your Titanium Development.
+Building apps for iOS it's all great until you have to deal with Certificates, Provisioning Profiles and sending iTunes Connect. Then came [fastlane.tools](https://fastlane.tools/) a collection of 9 tools that enable Continuous Deployment of iOS Apps.
 
-*Please note that this tool is currently in beta development.*
+TiFastlane it's a way to use those tools for Titanium development. Now you'll be able to do real continous deployment of your Titanium app. Sending your app for review will be a breeze:
 
-## About fastlane.tools
+	tifastlane sendapp
 
-The [fastlane](https://fastlane.tools/) family is a collection of tools that enable Continuous Deployment of iOS Apps. It has 9 different tools that allow things like registering the app, creating provisioning profiles and even automatic delivery to the App Store and TestFlight.
+With TiFastlane you'll be able to fully optimize the way you submit your app updates and maintain your certificates and provisioning profiles.
 
+
 ## Install [![npm version](https://badge.fury.io/js/tifastlane.svg)](http://badge.fury.io/js/tifastlane)
@@ -33,3 +34,3 @@
 
-`tifastlane` must be executed from your Titanium App directory. It will automatically ready your `tiapp.xml` to determine your App configuration for all the tools.
+`tifastlane` must be executed from your Titanium App directory. It will automatically read your `tiapp.xml` to determine your App configuration for all the tools.
 
@@ -40,11 +41,11 @@ You can view the current settings that would be used by running:
 
-## Register App (produce + sigh)
+## App IDs and Provisioning Profiles
 
-We have merged the actions of [produce](https://github.com/fastlane/produce) and [sigh](https://github.com/KrauseFx/sigh) into a single call.
+Register your Titanium App ID on the Apple Developer Program and iTunes Connect, and then generate the Provisioning Profiles for App Store, Ad Hoc and Development.
 
 	tifastlane register
 	
-This simple command will register the current Titanium App on the Apple Developer Program and iTunes Connect, and then generate the Provisioning Profiles for App Store, Ad Hoc and Development.
+Everything is done behing the scenes using [produce](https://github.com/fastlane/produce) and [sigh](https://github.com/KrauseFx/sigh). If the App ID already exists on the Developer Program or iTunes Connect it will be safely skipped.
 
-For default provisiong profiles will be generated for all platforms, but if you wish to only target a specific platform `appstore`, `adhoc` or `development`:
+For default provisiong profiles will be generated for all platforms, but if you wish you can target a single platform: `appstore`, `adhoc` or `development`.
 
@@ -55,3 +56,3 @@ tifastlane register <platform>
 
-* `-i, --skip_itc` - Skips creating the app on Itunes Connect
+* `-i, --skip_itc` - Skips creating the app on iTunes Connect
 * `--force` - By default if the Provisioning Profiles exist, they will be skipped. User force to recreate and resign the profiles.
@@ -61,21 +62,21 @@ * `--skip_install` - Skip installation of new provisioning profiles
 
-## Update iTunes Connect (deliver)
+## Maintain iTunes Connect (deliver)
 
-Now is possible to update your iTunes Connect metadata (Title, Description, Icon, etc) and screenshots using [deliver](https://github.com/KrauseFx/deliver). With this tool not only will you be able to update your app data from the command line, but you'll be able to keep track of it with version control.
+Update your app binary, your app metadata (Title, Description, Icon, etc) and your app screenshots using [deliver](https://github.com/KrauseFx/deliver).
 
 ### Initializing Deliverfile
 
-You will need to initialize your app settings. If this is a new app with no information on iTunes Connect then do:
+TiFastlane needs to initialize the configuration files needed to keep iTunes Connect updated with the correct information. If the app it's not in iTunes Connect then run to start fresh settings:
 
 	tifastlane init
 	
-If your app is already on iTunes Connect, then run the wizard which will download all your metadata and screenshots:
+If your app is already on iTunes Connect, then run the wizard which will automatically download all your current metadata and screenshots:
 
 	tifastlane initwizard
 
-After correct initialization you will see on the `TiFLDelivery` directory, a new directory with the name of your app.
+After correct initialization you will see on the `TiFLDelivery` directory, a new directory with the id of your app.
 
 ### Configuration Files
 
-All metadata and screenshots are easily maintaned from the `TiFLDelivery\APPID` directory, here you will find the following files:
+All metadata and screenshots are easily maintained from the `TiFLDelivery\APPID` directory, here you will find the following files:
 
@@ -94,19 +95,32 @@ **Deliveryfile**
 
-### Updating App on iTunes Connect
+## Sending App Updates
 
-Updating the App metadata and screenshots it's as easy as running:
+When you have a new version of your App that you wish to push to iTunes Connect, all you have to do is:
 
-	tifastlane updatemeta
+	tifastlane sendapp
 	
-This will login to iTunes Connect and update your app information based on your configuration, as well as uploading all the App screenshots.
+TiFastalane will get Titanium to build the ipa. It will build it as AdHoc so we get an ipa, so make sure to select your App Store certificate so it works when sending it to iTunes Connect.
 
-By default, before submitting you will be shown a report file with all the changes that will be made which you'll need to confirm. To skip this confirmation, which might be really useful for automation, just use:
+After the build, then using [deliver](https://github.com/KrauseFx/deliver) TiFastlane will login to iTunes Connect. It will automatically read the new version of your ipa and create a new version if necessary, upload the metadata, screenshots and finally your binary.
 
-* `--skip_verify` - Skips configuration verification before upload.
+After the ipa has succesfully uploaded, it will wait and try to submit it for review automatically. Make sure that you set the `submit_further_information` section on your Deliverfile.
 
-### Uploading ipa to App Store
+### Advanced Options
 
-Currently I'm working on the ability to upload your ipa to the App Store with an option to automatically submit for review.
+By default, before submitting you will be shown a report file with all the changes that will be made which you'll need to confirm. To skip this confirmation, which might be really useful for automation:
 
+* `--skip_verify` - Skips configuration prompt before upload.
 
+And if you want to send the binary without having to do a rebuild:
+
+* `--skip_build` - Skips ipa build
+
+### Updating only metadata
+
+You might want to update only the metadata and/or screenshots of your App without having to submit a new version or binary. To do so use:
+
+	tifastlane updatemeta
+	
+This will login to iTunes Connect and update your app information based on your configuration, as well as uploading all the App screenshots.
+
 ##TODO
@@ -124,2 +138,3 @@
 
+* 0.2.0 Now you can upload your app update.
 * 0.1.0 Now you can update your iTunes Connect metadata and screenshots (deliver)
@@ -126,0 +141,0 @@ * 0.0.3 Added register - Register App (produce + sigh)

No alert changes

Improved metrics

Total package byte prevSize

22232

increased by17.84%

Lines of code

347

increased by20.49%

Number of lines in readme file

155

increased by10.71%

No dependency changes