Why not https://github.com/lensfun/lensfun? It seems this is kept up to
date anyway so there probably wouldn't be an urgent need for automatic
mirroring. Are the commits to this repo pushed back to sourceforge?
If the repo above is suitable in principle then I would create a
temporary fork where I setup Travis CI on my own repo until it works,
and then submit a PR so that Travis CI runs on the repo above and not my
fork. This means accepting a .travis.yml file in the root and then the
repo owner would have to go to Travis CI, login through GitHub, and
press a button to enable Travis CI for this repo. As long as a committer
is registered on GitHub and has the commit email associated to their
account, then the automatic build failure emails should fly in, so no
need to check manually. That's the theory, we'd have to test if it
actually works.
Maik
On 28/06/2018 13:35, Sebastian Kraft wrote:
On 23.06.2018 22:49, Maik Riechert wrote:
Yes, I also had a look at integration with Sourceforge and nothing
seems to have changed. The easiest would be the mirror on GitHub,
however it would be nice if the mirroring is automated. I think we
could use a Travis CI job for that since they support cron-type
scheduling for some time now (e.g. repeat every day), which means it
would clone from sourceforge and then "push --mirror" to GitHub. It's
not a proper use of Travis CI and should be considered a temporary
work-around until moving to GitHub completely.
That sounds good. Do you want to set it up on your GitHub account? I
can then regularly check the build state and reports if you share the
link to the Travis CI logs.
Thanks,
Sebastian
Cheers
Maik
On 22/06/2018 03:24, Sebastian Kraft wrote:
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
