Another use case: Mass deployment to multiple PCs: https://forum.qt.io/topic/111587/classroom-deployment-of-qt-for-multiple-pcs-and-for-all-users-windows
Regards, Sze-Howe On Sat, 15 Feb 2020 at 07:06, Sze Howe Koh <[email protected]> wrote: > > On Sat, 15 Feb 2020 at 04:19, Thiago Macieira <[email protected]> > wrote: > > On Tuesday, 28 January 2020 19:31:34 PST Thiago Macieira wrote: > > > On Tuesday, 28 January 2020 03:52:49 PST Tino Pyssysalo wrote: > > > > It is also possible to transfer the qtaccount.ini file to a CI machine, > > > > which removes the need for manual/interactive login. The qtaccount.ini > > > > just > > > > contains the hash of the password. > > > > > > I suggest you be very careful in suggesting how to transfer the > > > qtaccount.ini file. Test half a dozen public CI systems and give > > > instructions to them all. > > > > > > And specifically tell people NOT to "git add" it to a project on GitHub/ > > > GitLab/BitBucket. > > > > Hello Tino > > > > Can we get an answer here? > > > > What is the recommended way to install Qt on a CI to test a Qt-based > > application? > > > > Travis CI has stopped working completely and I'd like to switch to GitHub > > Actions. Does The Qt Company recommend I use Stephan Binner's PPA? Or does > > it > > want me to use its own compiled binaries? If the latter, please provide > > instructions for automated builds. > > Hello Tino, > > It's not just CI; Qt now can't be easily used with all other > automation technologies like Docker. [1] > > Please note that users have started to suggest workarounds such as > creating throwaway Qt accounts in order to automate the installation. > [2] > > > Regards, > Sze-Howe > > [1] https://forum.qt.io/post/577886 > [2] https://forum.qt.io/post/577926 _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
