On 11/10/20 6:53 PM, Andrea Aime wrote:
Travis CI letting us down
Switch to a 10k credits and credit consumption per minute, gonna
happen by end of November.
Need to switch to something else for the Travis builds:
*
Github actions. Work, worried about using only one tool, and
everyone is switching to them.
*
Circle CI, we have had mixed success with the Windows build, and
there is a time limit (think 50 minutes). GeoNode is using
CircleCI. Apparently we’d get 4 concurrent builds for Linux
<https://circleci.com/blog/optimizing-open-source-projects-on-circleci/#:~:text=Parallelism%20is%20available%20if%20you,as%20they%20use%20more%20resources.>.
*
Azure Pipelines is also an option.
*
Anything else? Anyone that would like to work on a migration?
*
*
Auch! I didn't get that memo.
We used about 17000 minutes on our open source projects over the last
month @B3Partners so we'll probably be ditching Travis-CI... so I may be
able to lend a hand once we choose a direction.
Some of our projects already run on Jenkins as well using a Jenkinsfile,
but up until now I haven't managed setting up a build matrix with 2
different Java versions and a multitude of database flavours on a single
Jenkins instance running in parallel. (and running them all sequentially
takes all day).
Matrix builds should be doable reading
https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/ though.
I've looked into Github action/runners in the past, but (at least for
windows) ran into problems with the small disk capacity of the images
they use (specifically trying to use SQL Server on their Windows runner).
- Mark
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
