Hi Chris, Thanks for the suggestions. Gave me a lot of ideas for improvement.
The company I work for uses FTP to store the app bundles. :). But I consider coupling to a certain type of deployment alone is not good. I will look into the publish over plugin, and see how it can be coupled along. I would love to hear some ideas from you guys too. Scanning the ipa file and getting the details such as icons, bundle identifier and bundle version is awesome. I am on it. I would like the repo to be forked and a commit access in it. But if i incorporate the above changes it will drastically change the plugin, is it fine that i do these things while its a part of jenkins, or should I make these changes and then tell you guys?. The repo got moved to: https://github.com/jeslyvarghese/otabuilder-plugin And my github handle is: jeslyvarghese Thank You. Regards Jesly And On Thu, Dec 6, 2012 at 5:17 PM, Christopher Orr <ch...@orr.me.uk> wrote: > However, this plugin seems like it's pretty niche due to the FTP > integration. Do people really still use FTP? :) > I wonder whether the "Publish over..." plugins have an integration point > that could be used. > > Otherwise, it would be useful if the plugin had a build step which > generated the OTA Manifest.plist, automatically determining the Bundle > Identifier, Bundle Version (and perhaps icon and title) from the .ipa, > rather than having to configure these manually. > > Then you could upload the OTA artifacts however you like, rather than > being bound to FTP.. > > In any case, regarding a release, we can fork your GitHub repo into the > jenkinsci account. Then you can use that as your canonical repository, and > run the release from there, which I believe is just a case of running "jpi > release". >
