Hi Maik,
I like the idea of using a continuous integration service to test Lensfun
with different compilers and platforms. In the past I have looked at Travis
and others, but couldnt find something that nicely integrates with
Sourceforge. From my point of view we are not bound to Sourceforge forever,
but for short term there are too many other important issues before moving
to another hoster.
However, if you can recommend and configure a CI service that integrates
with the current Sourceforge hosting that would be great. Is there
something you have in mind?
Maybe as a workaround we can run Travis CI on a non-official branch on
GitHub and frequently push our Sourceforge master over to GitHub. Similarly
as it is done with the calibration service repo...
Cheers,
Sebastian
Am 21. Juni 2018 7:35:42 nachm. schrieb Maik Riechert <maik.riech...@arcor.de>:
Hi,
I was wondering what the opinion of developers is on the topic of
continuous integration, using services like Travis CI and Appveyor. This
would make build problems across platforms / compilers visible
immediately and reduce the chance of releasing a new version that
doesn't compile in certain settings. I'm happy to help with setting this
up but wanted to start a discussion first.
Cheers
Maik
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lensfun-users mailing list
Lensfun-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lensfun-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lensfun-users mailing list
Lensfun-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lensfun-users
