move the API docs building/hosting on Travis/Github

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

move the API docs building/hosting on Travis/Github

3nids
Hi,

Reading the issues we have with our website, have you considered moving the building/hosting of C++ API docs to Travis/Github similarly than we do for the Python API documentation?

It would be pretty easy to move these as they don't take much time to build. Docs would be built on Travis and deployed to Github pages (exactly same than for PyQGIS).

* no issue with hosting / traffic
* easier contribution from the community
* automatic detection of issue (form Travis builds)

My 2 cents.

Denis

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: move the API docs building/hosting on Travis/Github

Nathan Woodrow
That sounds like a good idea.  I thought we already did that but it seems not?

- Nathan

On Thu, Sep 5, 2019 at 5:27 PM Denis Rouzaud <[hidden email]> wrote:
Hi,

Reading the issues we have with our website, have you considered moving the building/hosting of C++ API docs to Travis/Github similarly than we do for the Python API documentation?

It would be pretty easy to move these as they don't take much time to build. Docs would be built on Travis and deployed to Github pages (exactly same than for PyQGIS).

* no issue with hosting / traffic
* easier contribution from the community
* automatic detection of issue (form Travis builds)

My 2 cents.

Denis
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: move the API docs building/hosting on Travis/Github

Alessandro Pasotti-2
Good idea, if that doesn't make Travis PR builds slower (Cron?)

On Thu, Sep 5, 2019, 09:30 Nathan Woodrow <[hidden email]> wrote:
That sounds like a good idea.  I thought we already did that but it seems not?

- Nathan

On Thu, Sep 5, 2019 at 5:27 PM Denis Rouzaud <[hidden email]> wrote:
Hi,

Reading the issues we have with our website, have you considered moving the building/hosting of C++ API docs to Travis/Github similarly than we do for the Python API documentation?

It would be pretty easy to move these as they don't take much time to build. Docs would be built on Travis and deployed to Github pages (exactly same than for PyQGIS).

* no issue with hosting / traffic
* easier contribution from the community
* automatic detection of issue (form Travis builds)

My 2 cents.

Denis
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: move the API docs building/hosting on Travis/Github

Tim Sutton-6
Hi

I have already been working on this - as Denis has discovered on Telegram….

T

On 5 Sep 2019, at 19:00, Alessandro Pasotti <[hidden email]> wrote:

Good idea, if that doesn't make Travis PR builds slower (Cron?)

On Thu, Sep 5, 2019, 09:30 Nathan Woodrow <[hidden email]> wrote:
That sounds like a good idea.  I thought we already did that but it seems not?

- Nathan

On Thu, Sep 5, 2019 at 5:27 PM Denis Rouzaud <[hidden email]> wrote:
Hi,

Reading the issues we have with our website, have you considered moving the building/hosting of C++ API docs to Travis/Github similarly than we do for the Python API documentation?

It would be pretty easy to move these as they don't take much time to build. Docs would be built on Travis and deployed to Github pages (exactly same than for PyQGIS).

* no issue with hosting / traffic
* easier contribution from the community
* automatic detection of issue (form Travis builds)

My 2 cents.

Denis
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

 




---

Tim Sutton





_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc