Re: [Interest] What are you using for continuous integration?

[Hamish Moffatt]

On 14/2/19 12:08 pm, william.croc...@analog.com wrote:




We have been using buildbot on a Linux server and multiple Macintosh 
and Windows

machines as workers for about 9 years. The workers build our Qt based
application, run tests, and if everything passes the application is 
uploaded to
the buildbot server which then passes the application to our web 
server so users

can download nightly builds of the application.



What ever happened to good ole cron jobs. 



Travis is written in Ruby, Jenkins in Java + Tomcat (!!), so Buildbot 
(Python) is about as close to old skool as it gets.


I just set one up this week. It still works fine and there's still 
regular releases.




Hamish

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] What are you using for continuous integration?

[william.croc...@analog.com]

We have been using buildbot on a Linux server and multiple Macintosh and Windows
machines as workers for about 9 years. The workers build our Qt based
application, run tests, and if everything passes the application is uploaded to
the buildbot server which then passes the application to our web server so users
can download nightly builds of the application.



What ever happened to good ole cron jobs.

Bill
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] What are you using for continuous integration?

[Adam Light]

On Tue, Feb 12, 2019 at 3:05 PM Nuno Santos 
wrote:

> Hi,
>
> I’m curious about what you Qt heads are using for continuous integration.
>
>
We have been using buildbot on a Linux server and multiple Macintosh and
Windows machines as workers for about 9 years. The workers build our Qt
based application, run tests, and if everything passes the application is
uploaded to the buildbot server which then passes the application to our
web server so users can download nightly builds of the application.

I wouldn't call it easy to set up, but that's largely because I was
learning Python as I was setting up the system.

Adam
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] What are you using for continuous integration?

[Elvis Stansvik]

Den ons 13 feb. 2019 kl 00:06 skrev Nuno Santos :
>
> Hi,
>
> I’m curious about what you Qt heads are using for continuous integration.
>
> I have googled a few times this for this topic and I have found a couple of 
> options but every time I tried to spend the minimum amount of time to setup 
> one, it seems an incredible effort. I’m looking for a solution that allows me 
> to:
>
> - push to a specific branch on GitHub
> - get a local CI agent to fetch that branch and build it
>
> Ideally I would like it to be :
>
> - fast to setup
> - Windows & Mac compatible
> - ideally with docker integration
>
> Drone works damn well for web projects. I wanted something that cool for 
> automatic desktop software building and packaging
>
> What are you people using?

We use Buildbot. It has worked very well, and we use it for some other
automation tasks besides software builds. It builds and tests software
from our local GitLab instance. Builds are mostly done in Docker
containers, though for macOS and Windows we run the Buildbot workers
on bare metal.

Downside is it's configured using Python and the configuration takes
some getting used to when setting it up for the first time (but it's
very well designed and worth learning). The upside is it's Python :)
so it's *very* flexible. Downside is also that the config is central
and not kept with the repos (though there is a project to support
Travis-style in-repo config).

Elvis

>
> Thanks!
>
> Best,
>
> Nuno
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] reCAPTCHA does not appear QML WebEngineView

[He Minzhang]

Or modify the WebEngine module directly.

获取 Outlook for Android


From: He Minzhang 
Sent: Thursday, February 14, 2019 1:27:04 AM
To: interest@qt-project.org; Miller, Doug
Subject: Re: reCAPTCHA does not appear QML WebEngineView

Whether WebEngine publicly calls http api, or directly hooks WebEngine to send 
http api internally.

Can refer to the source code in github.

获取 Outlook for Android


From: Interest  on behalf of Miller, Doug 

Sent: Wednesday, February 13, 2019 9:51:02 PM
To: interest@qt-project.org
Subject: [Interest] reCAPTCHA does not appear QML WebEngineView

I'm trying to interact with an URL that implements reCAPTCHA as a check box.  
On the same machine the Chrome browser makes this check box visible and usable, 
but in QML's WebEngineView is is not even visible.  I have the same proxy 
settings as the Chrome browser, so what else needs to be configure for this to 
work?

Thanks for any help.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] reCAPTCHA does not appear QML WebEngineView

[He Minzhang]

Whether WebEngine publicly calls http api, or directly hooks WebEngine to send 
http api internally.

Can refer to the source code in github.

?? Outlook for Android


From: Interest  on behalf of Miller, Doug 

Sent: Wednesday, February 13, 2019 9:51:02 PM
To: interest@qt-project.org
Subject: [Interest] reCAPTCHA does not appear QML WebEngineView

I'm trying to interact with an URL that implements reCAPTCHA as a check box.  
On the same machine the Chrome browser makes this check box visible and usable, 
but in QML's WebEngineView is is not even visible.  I have the same proxy 
settings as the Chrome browser, so what else needs to be configure for this to 
work?

Thanks for any help.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] What are you using for continuous integration?

[Bob Hood]

On 2/12/2019 4:05 PM, Nuno Santos wrote:

Hi,

I’m curious about what you Qt heads are using for continuous integration.


We have been using TeamCity (v9) for many years now to great effect.  We are 
using the "free" version, which is limited to only 3 agents, but running 
multiple servers (Production, Private, etc.) for each layer of our pipeline.


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] reCAPTCHA does not appear QML WebEngineView

[Miller, Doug]

I'm trying to interact with an URL that implements reCAPTCHA as a check box.  
On the same machine the Chrome browser makes this check box visible and usable, 
but in QML's WebEngineView is is not even visible.  I have the same proxy 
settings as the Chrome browser, so what else needs to be configure for this to 
work?

Thanks for any help.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] What are you using for continuous integration?

[Andy]

FWIW I just started using GitLab's CI for a smaller, non-Qt project. I like
it better than Travis (my other recent experience). The way GitLab CI
presents the pipelines & results in the interface makes sense to me.

Here are the top-level docs:

   https://docs.gitlab.com/ee/ci/

I think all CIs are fiddly to set up, so you aren't going to avoid that.
The GitLab one is no exception and took me a few tries to get what I want.
The nice thing about CIs is that you (probably) don't have to touch them a
lot, yet they provide a huge benefit to a project.

Good luck!

---
Andy Maloney  //  https://asmaloney.com
twitter ~ @asmaloney 



On Wed, Feb 13, 2019 at 6:40 AM Nuno Santos 
wrote:

> Christian,
>
> Thanks for your reply. Some questions below.
>
> We use jenkins too at work, I highly recommend the pipeline approach
> too. And if you can, use the declarative pipeline. Using docker
> container is a must as well.
> We run everything in docker, the jenkins master and build agents are
> all dockerised, and they start build and test jobs in docker
> containers too, you have to bindmount the docker socket for that you
> run 'side' containers.
>
>
> Can you recommend straight to the point documentation on this. I have
> always find Jenkins very time demanding to setup.
>
> I have used quite a few CI, and for me the best these days is
> definitely gitlab. You can run your own build-agents.
>
>
> For someone that is starting from the scratch. Would you recommend
> investing time in Jenkins or Gitlab?
>
> Thanks!
>
> Best regards,
>
> Nuno
>
> On 13 Feb 2019, at 00:58, Christian Gagneraud  wrote:
>
> On Wed, 13 Feb 2019 at 13:54, Christian Gagneraud 
> wrote:
>
>
> On Wed, 13 Feb 2019 at 13:46, Jérôme Godbout  wrote:
>
>
> Jenkins work well for me (you can ditch the custom Groovy and just call
> some python or whatever script you like)
>
> https://jenkins.io/
>
> I recommend the pipeline and put a jenkinsfile into your repos to setup
> the build. So your requirements and builds step are versioned along the
> source, so it can changes in the time and you still can goes back to the
> old version without having multiple build systems.
>
> https://jenkins.io/doc/book/pipeline/jenkinsfile/
>
> It's cross platform, a little more painful under Windows just like any
> services I guess, but it does work well overall. Best of all it's free!
>
>
> We use jenkins too at work, I hig
>
>
> Sorry, pressed ctrl-enter by mistake.
> We use jenkins too at work, I highly recommend the pipeline approach
> too. And if you can, use the declarative pipeline. Using docker
> container is a must as well.
> We run everything in docker, the jenkins master and build agents are
> all dockerised, and they start build and test jobs in docker
> containers too, you have to bindmount the docker socket for that you
> run 'side' containers.
> I have used quite a few CI, and for me the best these days is
> definitely gitlab. You can run your own build-agents.
>
> Chris
>
>
>
> Amotus
> une compagnie DimOnOff
> RAPPROCHEZ LA DISTANCE
> Jérôme Godbout
> Développeur Logiciel Sénior /
> Senior Software Developer
> p: +1 (418) 800-1073 ext.:109
> amotus.ca
> statum-iot.com
> -Original Message-
> From: Interest  On Behalf Of Nuno Santos
> Sent: February 12, 2019 6:05 PM
> To: Interests Qt (interest@qt-project.org) 
> Subject: [Interest] What are you using for continuous integration?
>
> Hi,
>
> I’m curious about what you Qt heads are using for continuous integration.
>
> I have googled a few times this for this topic and I have found a couple
> of options but every time I tried to spend the minimum amount of time to
> setup one, it seems an incredible effort. I’m looking for a solution that
> allows me to:
>
> - push to a specific branch on GitHub
> - get a local CI agent to fetch that branch and build it
>
> Ideally I would like it to be :
>
> - fast to setup
> - Windows & Mac compatible
> - ideally with docker integration
>
> Drone works damn well for web projects. I wanted something that cool for
> automatic desktop software building and packaging
>
> What are you people using?
>
> Thanks!
>
> Best,
>
> Nuno
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] What are you using for continuous integration?

[Nuno Santos]

Christian,

Thanks for your reply. Some questions below.

> We use jenkins too at work, I highly recommend the pipeline approach
> too. And if you can, use the declarative pipeline. Using docker
> container is a must as well.
> We run everything in docker, the jenkins master and build agents are
> all dockerised, and they start build and test jobs in docker
> containers too, you have to bindmount the docker socket for that you
> run 'side' containers.

Can you recommend straight to the point documentation on this. I have always 
find Jenkins very time demanding to setup.

> I have used quite a few CI, and for me the best these days is
> definitely gitlab. You can run your own build-agents.

For someone that is starting from the scratch. Would you recommend investing 
time in Jenkins or Gitlab? 

Thanks!

Best regards,

Nuno

> On 13 Feb 2019, at 00:58, Christian Gagneraud  wrote:
> 
> On Wed, 13 Feb 2019 at 13:54, Christian Gagneraud  > wrote:
>> 
>> On Wed, 13 Feb 2019 at 13:46, Jérôme Godbout  wrote:
>>> 
>>> Jenkins work well for me (you can ditch the custom Groovy and just call 
>>> some python or whatever script you like)
>>> 
>>> https://jenkins.io/
>>> 
>>> I recommend the pipeline and put a jenkinsfile into your repos to setup the 
>>> build. So your requirements and builds step are versioned along the source, 
>>> so it can changes in the time and you still can goes back to the old 
>>> version without having multiple build systems.
>>> 
>>> https://jenkins.io/doc/book/pipeline/jenkinsfile/
>>> 
>>> It's cross platform, a little more painful under Windows just like any 
>>> services I guess, but it does work well overall. Best of all it's free!
>> 
>> We use jenkins too at work, I hig
> 
> Sorry, pressed ctrl-enter by mistake.
> We use jenkins too at work, I highly recommend the pipeline approach
> too. And if you can, use the declarative pipeline. Using docker
> container is a must as well.
> We run everything in docker, the jenkins master and build agents are
> all dockerised, and they start build and test jobs in docker
> containers too, you have to bindmount the docker socket for that you
> run 'side' containers.
> I have used quite a few CI, and for me the best these days is
> definitely gitlab. You can run your own build-agents.
> 
> Chris
> 
>> 
>>> 
>>> Amotus
>>> une compagnie DimOnOff
>>> RAPPROCHEZ LA DISTANCE
>>> Jérôme Godbout
>>> Développeur Logiciel Sénior /
>>> Senior Software Developer
>>> p: +1 (418) 800-1073 ext.:109
>>> amotus.ca
>>> statum-iot.com
>>> -Original Message-
>>> From: Interest  On Behalf Of Nuno Santos
>>> Sent: February 12, 2019 6:05 PM
>>> To: Interests Qt (interest@qt-project.org) 
>>> Subject: [Interest] What are you using for continuous integration?
>>> 
>>> Hi,
>>> 
>>> I’m curious about what you Qt heads are using for continuous integration.
>>> 
>>> I have googled a few times this for this topic and I have found a couple of 
>>> options but every time I tried to spend the minimum amount of time to setup 
>>> one, it seems an incredible effort. I’m looking for a solution that allows 
>>> me to:
>>> 
>>> - push to a specific branch on GitHub
>>> - get a local CI agent to fetch that branch and build it
>>> 
>>> Ideally I would like it to be :
>>> 
>>> - fast to setup
>>> - Windows & Mac compatible
>>> - ideally with docker integration
>>> 
>>> Drone works damn well for web projects. I wanted something that cool for 
>>> automatic desktop software building and packaging
>>> 
>>> What are you people using?
>>> 
>>> Thanks!
>>> 
>>> Best,
>>> 
>>> Nuno
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> https://lists.qt-project.org/listinfo/interest
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] How to get macdeployqt to ship QtSpeech plugin?

[Vadim Peretokin]

Aha! Thanks.

On Tue, Feb 12, 2019 at 9:48 PM Samuel Gaist  wrote:

> On 12 Feb 2019, at 18:05, Vadim Peretokin  wrote:
> >
> > Hi!
> >
> > How can I get Qt 5.12 macdeployqt to include QtSpeech plugin in the
> distribution? My project makes use of it, QtSpeech plugin is available in
> the Qt installation, but yet it is not getting added to the application.
> >
> > Thanks,
> > Vadim.
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
>
> Hi,
>
> You have to apply this patch:
>
> https://codereview.qt-project.org/#/c/253094/
>
> and build macdeployqt (nothing else is needed)
>
> Best regards
>
> Samuel
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest