Hi Magnus, we use a release script in QFieldSync, where we directly release from travis when a new tag pushed and tests run successfully (and some other conditions like tag name matches the version in metadata etc. are met).
https://github.com/opengisch/qfieldsync/blob/master/.travis.yml#L27 It also only packages a sub-folder with the plugin, so scripts for ci etc that live outside this folder are not packaged. Hope that helps :) Matthias On 03/11/2017 10:12 PM, Magnus Homann wrote: > Hello, currently I tag my plugin code in git, and extract and build a > zip-file which is uploaded to plugin repo. > The Makefile that plugin_builder is supplyng, also have an option to zip > locally deployed files for later upload. > > I prefer to packaged directly from tag in git, but then every file that > is in git will be packaged! > > Have anyone made a mixed approach, packaging directly from a git tag, > but only a sub-set of the files? > > /Magnus > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ Qgis-developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
