- Development for Teensy is only possible with Arduino IDE (do you really develop your code with this "IDE"?) and not with Eclipse / Sloeber etc. as for all other platforms, even if you do not require the Teensy features.
Please correct me, if I am wrong!
Sorry I am not sure what you are saying or asking here.
There are lots of options that you can choose to build for the Teensy, which many of us do.
Yes I do use the Arduino IDE for lots of basic things and also to double check that what I build also works with the IDE. Yes it is not the greatest IDE ever made, but it is not the worst either...
Other options include:
a) Make - there is a make file in the installed stuff to show you how you can do it.
b) Platform IO.
c) Visual Studio with Visual Micro.
d) Sublime Text - (I use this most of the time when I am doing more involved stuff. Again there are multiple ways to do this. All of which I have tried and done:
1) Set Arduino IDE to the option use external editor, do my edits in sublimetext, and then use Arduino to build and upload.
2) Deviot - install which is sort of a cross between Platform IO and an earlier attempt STINO
3) a set of batch files (TSET) and stuff by @defragster and @Frank B - which you can configure your project to build with your options and it builds a script that uses the Arduino Build system. to do the builds
e) VisualTeensy (or is there a newer name yet), which is a setup with VisualCode:
https://github.com/TeensyUser/doc/wiki/VisualTeensy
Again there are several options.
As for Continuous Integration stuff, I believe there are others who do this, that I believe work with Teensy boards. In particular when I make changes to some of the different Adafruit projects I know that they run through several tests and building on several different platforms. I have not double checked that they test against the different teensy boards or not. But I know each time I go through a PR or the like, I do see testing updates and the like.
This would be a great thing for many of our libraries as I know speaking for myself, when I make fixes to some of my own libraries, I often get lazy and forget to test again the LC or the like.
Hope you find a solution that works for you.