: Matthias Kuhn <matth...@opengis.ch>
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Ideas concerning plugin deployment
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
condition
On 13.03.2017 11:12, Marco Bernasocchi wrote:
> maybe we could have a pip repo as backend. just talking out loud and
> explicitly adding Ale to the conversation :)
>
Forgot the link: https://packaging.python.org/self_hosted_repository/
> ciao
>
>
>
>
On 13.03.2017 11:06, Tim Sutton wrote:
>> or make plugins PIP packages :)
>
> Yeah or that :-) I think we did discuss it before and it would be pretty
> cool - only thing we lose really if the curated repository approach we
> have now (which might make some people happy I guess)...
maybe we
Hi
> On 13 Mar 2017, at 12:04 PM, Marco Bernasocchi wrote:
>
> Hi
>
> On 13.03.2017 10:44, Tim Sutton wrote:
>> One thing that might actually be nice is for us to introduce some kind
>> of Manifest file for plugins (we could just copy the system from pip) so
>> that plugin
Hi
On 13.03.2017 10:44, Tim Sutton wrote:
> One thing that might actually be nice is for us to introduce some kind
> of Manifest file for plugins (we could just copy the system from pip) so
> that plugin authors can specify which files and resources get packaged.
or make plugins PIP packages :)
Hi Magnus
(by the way nice to see you pop up here on the list after many years!)
> On 13 Mar 2017, at 10:32 AM, Magnus Homann wrote:
>
> Thank you, I'll look into InaSAFE if that is something I could use. The
> Makefile from plugin builder is already using git archive, but
Thank you, I'll look into InaSAFE if that is something I could use. The
Makefile from plugin builder is already using git archive, but packages every
file in the repo.
/Magnus
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info:
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
Hi Magnus,
In InaSAFE plugin, we also use git-archive, but since we use git submodule,
we use git archive-all (available in brew or pip) [1]. We create script to
do the release of the plugin to make it easier [2]. We add more
functionalities like removing test related files (to make the size
can be useful? https://git-scm.com/docs/git-archive
Luigi Pirelli
**
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com
* LinkedIn: https://www.linkedin.com/in/luigipirelli
*
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
11 matches
Mail list logo