Uploaded image for project: 'Appcelerator Studio'
  1. Appcelerator Studio
  2. TISTUD-6313

Support mechanism to allow the developer to create custom build targets and build configurations

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Build
    • Labels:

      Description

      Feature Request

      Essentially Client would like to see a similar pattern that is available in xcode for creating, editing and managing targets and build configurations.

      The current appcelerator targets are limited i.e. simulator, device, dist-appstore, dist-adhoc

      Current scenarios

      To amplify on a couple of current scenarios as described by customer and that they would like to solve:

      1. Assume we have an outside vendor providing code.
      He has setup his tiapp.xml file with app ids and various keys for acs auth, google map api, etc.
      We get the code, now we have to edit the tiapp.xml and replace the app ids and various keys for acs auth, google map api, etc with our own values
      We then build and deploy locally for testing.
      Perhaps issues are found with the code drop and we need to get another drop from the vendor.
      Once we do, the we have to remember to change app ids and various keys for acs auth, google map api, etc.

      What would be nice is if we could create some targets notionally like:

      device-vendor - assign a "vendor specific" tiapp.xml to here
      device-local - assign the "default" tiapp.xml to here
      adhoc-local - assign the "default" tiapp.xml to here
      dist-local - assign the "default" tiapp.xml to here (assume appstore destination)

      simulator-vendor - assign a "vendor specific" tiapp.xml to here
      simulator-local - assign the "default" tiapp.xml to here

      Now the "build configuration" could be assigned as appropriate i.e. device, adhoc, dist, simulator

      2. Assume we have an app we are developing destined for the appstore.
      Our current process is to create a "shadow appid" in our enterprise account to eliminate building adhoc appstore versions for internal testing.
      We setup the enterprise tiapp.xml with the appropriate settings.
      We setup the appstore tiapp.xml with the appropriate settings.

      Once we are done with internal testing, we then resign / build with the "real" appid

      What would be nice is if we could create some targets notionally like:

      device-enterprise - assign a "enterprise specific" tiapp.xml to here
      device-appstore - assign the "default or appstore" tiapp.xml to here

      dist-enterprise - assign the "enterprise specific" tiapp.xml to here
      dist-appstore - assign the "default or appstore" tiapp.xml to here

      simulator-specific - assign a "enterprise specific" tiapp.xml to here
      simulator-appstore - assign the "default appstore" tiapp.xml to here

      Now the "build configuration" could be assigned as appropriate i.e. device, adhoc, dist, simulator

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kkolipaka Kondal Kolipaka (Inactive)
                Reporter:
                egomez Eduardo Gomez (Inactive)
              • Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: