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

[Nuno Santos]

Croitor,

You have a very strong point here. Qmake is hardcoded to the build path. I have 
tried to override that with 

https://doc.qt.io/qt-5/qmake-environment-reference.html 


But it didn’t worked! 

I decided to add sudo: required to travis file and create the same directory I 
have in my local machine. This trick worked!

Thanks!

Best,

Nuno

> On 18 Feb 2019, at 12:22, Croitor Alexandru  wrote:
> 
> Not 100% sure, but assuming the macx-clang mkspec actually exists, I think 
> that your Qt installation is not relocatable. Although locally I tried moving 
> the online installed qt dir, and invoking qmake on an example worked fine.
> 
> Maybe try running qmake -d .. &> log.txt and check if that gives you any info 
> on which paths qmake is looking for. Maybe setting a qt.conf with a 
> PrefixPath might also help.
> 
> Just some suggestions.
> 
> On Mon, Feb 18, 2019 at 1:08 PM Nuno Santos  > wrote:
> Hi,
> 
> I have found this slide deck very very very interesting.
> 
>> http://www.slidedeck.io/lasconic/qtci-qtcon2016 
>> 
> It seems that MuseScore doing precisely what I want to do with Travis help.
> 
> I became aware that Travis can build for Mac OSX. I didn’t knew that. And 
> that it is possible to build for windows as well through AppVeyor. This were 
> my number one requirements for this CI quest so I decided to give it a try.
> 
> I don’t have time to go through all the configuration steps from the scratch 
> with Jenkins. Yes, I could save money because Jenkins is free, but time is 
> money too and time is my most valuable resource. 
> 
> 
> I’m now tinkering around a Mac OSX build with Travis but I’m running into a 
> problem…
> 
> For my desktop builds I depend on a static build of Qt. Obviously I don’t 
> want to compile Qt from source at each build so I’m downloading into the 
> worker a prebuilt Qt kit and I’m calling my build script which will call 
> qmake on the project, on the worker environment. The problem is:
> 
> 1.06s$ ./build.sh
> Building app.pro  on 1550491076
> Could not find qmake spec 'macx-clang'.
> 
> qmake is returning with the error above, saying that it can’t find qmake spec 
> ‘macx-clang’
> 
> What are the possible reasons for qmake to return with such error? What is 
> qmake looking for that it can’t find?
> 
> Does anyone has an idea why this is happening?
> 
> Thanks in advance!
> 
> Regards,
> 
> Nuno
> 
>> On 17 Feb 2019, at 15:33, Croitor Alexandru > > wrote:
>> 
>> Hi,
>> 
>> The mentioned qtci repo https://github.com/benlau/qtci 
>>  also has two reference links which look 
>> useful. Pasting here as well.
>> 
>> http://www.slidedeck.io/lasconic/qtci-qtcon2016 
>> 
>> http://andrewdolby.com/articles/2016/continuous-deployment-for-qt-applications/
>>  
>> 
>> 
>> Another source of inspiration can be the travis and appveyor config files at 
>> https://github.com/bjorn/tiled  which is a 
>> Qt application built with qbs.
>> 
>> One provider also worth considering is VSTS / Azure Pipelines.
>> 
>> They offer free CI / CD and free runners (Windows, Linux, macOS) for open 
>> source Git projects. 
>> https://azure.microsoft.com/en-us/services/devops/pipelines/ 
>> 
>> They claim each job can be up to 6 hours, which is higher than what Travis 
>> allows iirc.
>> 
>> Some discussion about it can be found here 
>> https://www.reddit.com/r/programming/comments/9enz31/announcing_azure_pipelines_with_unlimited_cicd/
>>  
>> 
>> 
>> Cheers.
>> 
>> On Sun, Feb 17, 2019 at 3:34 PM René Hansen > > wrote:
>> Does anyone have any experience using Travis for for Qt projects?
>> 
>> I found this project, which seems to at least have a good general approach 
>> to setting up a usable environment for Travis:
>> 
>> https://github.com/benlau/qtci 
>> 
>> If anyone has tried using it, I'd love to hear about it.
>> 
>> 
>> /René
>> 
>> On Thu, 14 Feb 2019 at 10:22 Elvis Stansvik > > wrote:
>> Den tors 14 feb. 2019 kl 10:08 skrev Nuno Santos > >:
>> >
>> > Hey,
>> >
>> > Thank you all for sharing your solutions and approaches. Among here there 
>> > are two obvious winners:
>> >
>> > - Jenkins
>> > - Buildbot
>> >
>> > I want to keep the build config within the project so I guess Jenkins will 
>> > be my way to go.
>> 
>> For brevity, this is the side-project I mentioned to make Buildbot
>> more like Travis in that respect:
>> 

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

[Croitor Alexandru]

Not 100% sure, but assuming the macx-clang mkspec actually exists, I think
that your Qt installation is not relocatable. Although locally I tried
moving the online installed qt dir, and invoking qmake on an example worked
fine.

Maybe try running qmake -d .. &> log.txt and check if that gives you any
info on which paths qmake is looking for. Maybe setting a qt.conf with a
PrefixPath might also help.

Just some suggestions.

On Mon, Feb 18, 2019 at 1:08 PM Nuno Santos 
wrote:

> Hi,
>
> I have found this slide deck very very very interesting.
>
> http://www.slidedeck.io/lasconic/qtci-qtcon2016
>
>
> It seems that MuseScore doing precisely what I want to do with Travis help.
>
> I became aware that Travis can build for Mac OSX. I didn’t knew that. And
> that it is possible to build for windows as well through AppVeyor. This
> were my number one requirements for this CI quest so I decided to give it a
> try.
>
> I don’t have time to go through all the configuration steps from the
> scratch with Jenkins. Yes, I could save money because Jenkins is free, but
> time is money too and time is my most valuable resource.
>
>
> I’m now tinkering around a Mac OSX build with Travis but I’m running into
> a problem…
>
> For my desktop builds I depend on a static build of Qt. Obviously I don’t
> want to compile Qt from source at each build so I’m downloading into the
> worker a prebuilt Qt kit and I’m calling my build script which will call
> qmake on the project, on the worker environment. The problem is:
>
> 1.06s$ ./build.sh
> Building app.pro on 1550491076
> *Could not find qmake spec 'macx-clang'.*
>
> qmake is returning with the error above, saying that it can’t find qmake
> spec ‘macx-clang’
>
> What are the possible reasons for qmake to return with such error? What is
> qmake looking for that it can’t find?
>
> Does anyone has an idea why this is happening?
>
> Thanks in advance!
>
> Regards,
>
> Nuno
>
> On 17 Feb 2019, at 15:33, Croitor Alexandru  wrote:
>
> Hi,
>
> The mentioned qtci repo https://github.com/benlau/qtci also has two
> reference links which look useful. Pasting here as well.
>
> http://www.slidedeck.io/lasconic/qtci-qtcon2016
>
> http://andrewdolby.com/articles/2016/continuous-deployment-for-qt-applications/
>
> Another source of inspiration can be the travis and appveyor config files
> at https://github.com/bjorn/tiled which is a Qt application built with
> qbs.
>
> One provider also worth considering is VSTS / Azure Pipelines.
>
> They offer free CI / CD and free runners (Windows, Linux, macOS) for open
> source Git projects.
> https://azure.microsoft.com/en-us/services/devops/pipelines/
> They claim each job can be up to 6 hours, which is higher than what Travis
> allows iirc.
>
> Some discussion about it can be found here
> https://www.reddit.com/r/programming/comments/9enz31/announcing_azure_pipelines_with_unlimited_cicd/
>
> Cheers.
>
> On Sun, Feb 17, 2019 at 3:34 PM René Hansen  wrote:
>
>> Does anyone have any experience using Travis for for Qt projects?
>>
>> I found this project, which seems to at least have a good general
>> approach to setting up a usable environment for Travis:
>>
>> https://github.com/benlau/qtci
>>
>> If anyone has tried using it, I'd love to hear about it.
>>
>>
>> /René
>>
>> On Thu, 14 Feb 2019 at 10:22 Elvis Stansvik  wrote:
>>
>>> Den tors 14 feb. 2019 kl 10:08 skrev Nuno Santos <
>>> nunosan...@imaginando.pt>:
>>> >
>>> > Hey,
>>> >
>>> > Thank you all for sharing your solutions and approaches. Among here
>>> there are two obvious winners:
>>> >
>>> > - Jenkins
>>> > - Buildbot
>>> >
>>> > I want to keep the build config within the project so I guess Jenkins
>>> will be my way to go.
>>>
>>> For brevity, this is the side-project I mentioned to make Buildbot
>>> more like Travis in that respect:
>>> https://github.com/buildbot/buildbot_travis
>>>
>>> It's maintained (and I believe used) by the Buildbot maintainers
>>> themselves. I've looked at it, but we haven't tried to use it. One
>>> reason is that it works by dynamically adjusting the Buildbot config,
>>> and I was unsure how this would work if we still wanted to have parts
>>> of the Buildbot config that were custom/static (like I mentioned, we
>>> have some other automation tasks that we run on top of the same
>>> Buildbot master instance).
>>>
>>> Anyway, just thought I'd drop the link. Probably good idea to go with
>>> Jenkins if you want in-repo build recipies out of the box.
>>>
>>> Elvis
>>>
>>> >
>>> > Now I just need to go though all the configuration details. If anyone
>>> knows any really pragmatic documentation on how to setup Jenkins server
>>> with GitHub and how to setup a worker on Mac and Windows, please share.
>>> >
>>> > Thanks,
>>> >
>>> > Best regards,
>>> >
>>> > Nuno
>>> >
>>> > On 13 Feb 2019, at 19:02, Elvis Stansvik  wrote:
>>> >
>>> > Den ons 13 feb. 2019 kl 00:06 skrev Nuno Santos <
>>> nunosan...@imaginando.pt>:
>>> >
>>> >
>>> > Hi,
>>> >
>>> > I’m curious about what you Qt 

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

[Nuno Santos]

Hi,

I have found this slide deck very very very interesting.

> http://www.slidedeck.io/lasconic/qtci-qtcon2016 
> 
It seems that MuseScore doing precisely what I want to do with Travis help.

I became aware that Travis can build for Mac OSX. I didn’t knew that. And that 
it is possible to build for windows as well through AppVeyor. This were my 
number one requirements for this CI quest so I decided to give it a try.

I don’t have time to go through all the configuration steps from the scratch 
with Jenkins. Yes, I could save money because Jenkins is free, but time is 
money too and time is my most valuable resource. 


I’m now tinkering around a Mac OSX build with Travis but I’m running into a 
problem…

For my desktop builds I depend on a static build of Qt. Obviously I don’t want 
to compile Qt from source at each build so I’m downloading into the worker a 
prebuilt Qt kit and I’m calling my build script which will call qmake on the 
project, on the worker environment. The problem is:

1.06s$ ./build.sh
Building app.pro on 1550491076
Could not find qmake spec 'macx-clang'.

qmake is returning with the error above, saying that it can’t find qmake spec 
‘macx-clang’

What are the possible reasons for qmake to return with such error? What is 
qmake looking for that it can’t find?

Does anyone has an idea why this is happening?

Thanks in advance!

Regards,

Nuno

> On 17 Feb 2019, at 15:33, Croitor Alexandru  wrote:
> 
> Hi,
> 
> The mentioned qtci repo https://github.com/benlau/qtci 
>  also has two reference links which look 
> useful. Pasting here as well.
> 
> http://www.slidedeck.io/lasconic/qtci-qtcon2016 
> 
> http://andrewdolby.com/articles/2016/continuous-deployment-for-qt-applications/
>  
> 
> 
> Another source of inspiration can be the travis and appveyor config files at 
> https://github.com/bjorn/tiled  which is a Qt 
> application built with qbs.
> 
> One provider also worth considering is VSTS / Azure Pipelines.
> 
> They offer free CI / CD and free runners (Windows, Linux, macOS) for open 
> source Git projects. 
> https://azure.microsoft.com/en-us/services/devops/pipelines/ 
> 
> They claim each job can be up to 6 hours, which is higher than what Travis 
> allows iirc.
> 
> Some discussion about it can be found here 
> https://www.reddit.com/r/programming/comments/9enz31/announcing_azure_pipelines_with_unlimited_cicd/
>  
> 
> 
> Cheers.
> 
> On Sun, Feb 17, 2019 at 3:34 PM René Hansen  > wrote:
> Does anyone have any experience using Travis for for Qt projects?
> 
> I found this project, which seems to at least have a good general approach to 
> setting up a usable environment for Travis:
> 
> https://github.com/benlau/qtci 
> 
> If anyone has tried using it, I'd love to hear about it.
> 
> 
> /René
> 
> On Thu, 14 Feb 2019 at 10:22 Elvis Stansvik  > wrote:
> Den tors 14 feb. 2019 kl 10:08 skrev Nuno Santos  >:
> >
> > Hey,
> >
> > Thank you all for sharing your solutions and approaches. Among here there 
> > are two obvious winners:
> >
> > - Jenkins
> > - Buildbot
> >
> > I want to keep the build config within the project so I guess Jenkins will 
> > be my way to go.
> 
> For brevity, this is the side-project I mentioned to make Buildbot
> more like Travis in that respect:
> https://github.com/buildbot/buildbot_travis 
> 
> 
> It's maintained (and I believe used) by the Buildbot maintainers
> themselves. I've looked at it, but we haven't tried to use it. One
> reason is that it works by dynamically adjusting the Buildbot config,
> and I was unsure how this would work if we still wanted to have parts
> of the Buildbot config that were custom/static (like I mentioned, we
> have some other automation tasks that we run on top of the same
> Buildbot master instance).
> 
> Anyway, just thought I'd drop the link. Probably good idea to go with
> Jenkins if you want in-repo build recipies out of the box.
> 
> Elvis
> 
> >
> > Now I just need to go though all the configuration details. If anyone knows 
> > any really pragmatic documentation on how to setup Jenkins server with 
> > GitHub and how to setup a worker on Mac and Windows, please share.
> >
> > Thanks,
> >
> > Best regards,
> >
> > Nuno
> >
> > On 13 Feb 2019, at 19:02, Elvis Stansvik  > > wrote:
> >
> > Den ons 13 feb. 2019 kl 00:06 skrev Nuno Santos  > >:
> >
> >
> > Hi,
> >
> > I’m curious about what you Qt heads 

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

[Croitor Alexandru]

Hi,

The mentioned qtci repo https://github.com/benlau/qtci also has two
reference links which look useful. Pasting here as well.

http://www.slidedeck.io/lasconic/qtci-qtcon2016
http://andrewdolby.com/articles/2016/continuous-deployment-for-qt-applications/

Another source of inspiration can be the travis and appveyor config files
at https://github.com/bjorn/tiled which is a Qt application built with qbs.

One provider also worth considering is VSTS / Azure Pipelines.

They offer free CI / CD and free runners (Windows, Linux, macOS) for open
source Git projects.
https://azure.microsoft.com/en-us/services/devops/pipelines/
They claim each job can be up to 6 hours, which is higher than what Travis
allows iirc.

Some discussion about it can be found here
https://www.reddit.com/r/programming/comments/9enz31/announcing_azure_pipelines_with_unlimited_cicd/

Cheers.

On Sun, Feb 17, 2019 at 3:34 PM René Hansen  wrote:

> Does anyone have any experience using Travis for for Qt projects?
>
> I found this project, which seems to at least have a good general approach
> to setting up a usable environment for Travis:
>
> https://github.com/benlau/qtci
>
> If anyone has tried using it, I'd love to hear about it.
>
>
> /René
>
> On Thu, 14 Feb 2019 at 10:22 Elvis Stansvik  wrote:
>
>> Den tors 14 feb. 2019 kl 10:08 skrev Nuno Santos <
>> nunosan...@imaginando.pt>:
>> >
>> > Hey,
>> >
>> > Thank you all for sharing your solutions and approaches. Among here
>> there are two obvious winners:
>> >
>> > - Jenkins
>> > - Buildbot
>> >
>> > I want to keep the build config within the project so I guess Jenkins
>> will be my way to go.
>>
>> For brevity, this is the side-project I mentioned to make Buildbot
>> more like Travis in that respect:
>> https://github.com/buildbot/buildbot_travis
>>
>> It's maintained (and I believe used) by the Buildbot maintainers
>> themselves. I've looked at it, but we haven't tried to use it. One
>> reason is that it works by dynamically adjusting the Buildbot config,
>> and I was unsure how this would work if we still wanted to have parts
>> of the Buildbot config that were custom/static (like I mentioned, we
>> have some other automation tasks that we run on top of the same
>> Buildbot master instance).
>>
>> Anyway, just thought I'd drop the link. Probably good idea to go with
>> Jenkins if you want in-repo build recipies out of the box.
>>
>> Elvis
>>
>> >
>> > Now I just need to go though all the configuration details. If anyone
>> knows any really pragmatic documentation on how to setup Jenkins server
>> with GitHub and how to setup a worker on Mac and Windows, please share.
>> >
>> > Thanks,
>> >
>> > Best regards,
>> >
>> > Nuno
>> >
>> > On 13 Feb 2019, at 19:02, Elvis Stansvik  wrote:
>> >
>> > Den ons 13 feb. 2019 kl 00:06 skrev Nuno Santos <
>> nunosan...@imaginando.pt>:
>> >
>> >
>> > 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
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>
> ___
> Interest mailing list
> 

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

[René Hansen]

Does anyone have any experience using Travis for for Qt projects?

I found this project, which seems to at least have a good general approach
to setting up a usable environment for Travis:

https://github.com/benlau/qtci

If anyone has tried using it, I'd love to hear about it.


/René

On Thu, 14 Feb 2019 at 10:22 Elvis Stansvik  wrote:

> Den tors 14 feb. 2019 kl 10:08 skrev Nuno Santos  >:
> >
> > Hey,
> >
> > Thank you all for sharing your solutions and approaches. Among here
> there are two obvious winners:
> >
> > - Jenkins
> > - Buildbot
> >
> > I want to keep the build config within the project so I guess Jenkins
> will be my way to go.
>
> For brevity, this is the side-project I mentioned to make Buildbot
> more like Travis in that respect:
> https://github.com/buildbot/buildbot_travis
>
> It's maintained (and I believe used) by the Buildbot maintainers
> themselves. I've looked at it, but we haven't tried to use it. One
> reason is that it works by dynamically adjusting the Buildbot config,
> and I was unsure how this would work if we still wanted to have parts
> of the Buildbot config that were custom/static (like I mentioned, we
> have some other automation tasks that we run on top of the same
> Buildbot master instance).
>
> Anyway, just thought I'd drop the link. Probably good idea to go with
> Jenkins if you want in-repo build recipies out of the box.
>
> Elvis
>
> >
> > Now I just need to go though all the configuration details. If anyone
> knows any really pragmatic documentation on how to setup Jenkins server
> with GitHub and how to setup a worker on Mac and Windows, please share.
> >
> > Thanks,
> >
> > Best regards,
> >
> > Nuno
> >
> > On 13 Feb 2019, at 19:02, Elvis Stansvik  wrote:
> >
> > Den ons 13 feb. 2019 kl 00:06 skrev Nuno Santos <
> nunosan...@imaginando.pt>:
> >
> >
> > 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
> ___
> 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?

[Elvis Stansvik]

Den tors 14 feb. 2019 kl 10:08 skrev Nuno Santos :
>
> Hey,
>
> Thank you all for sharing your solutions and approaches. Among here there are 
> two obvious winners:
>
> - Jenkins
> - Buildbot
>
> I want to keep the build config within the project so I guess Jenkins will be 
> my way to go.

For brevity, this is the side-project I mentioned to make Buildbot
more like Travis in that respect:
https://github.com/buildbot/buildbot_travis

It's maintained (and I believe used) by the Buildbot maintainers
themselves. I've looked at it, but we haven't tried to use it. One
reason is that it works by dynamically adjusting the Buildbot config,
and I was unsure how this would work if we still wanted to have parts
of the Buildbot config that were custom/static (like I mentioned, we
have some other automation tasks that we run on top of the same
Buildbot master instance).

Anyway, just thought I'd drop the link. Probably good idea to go with
Jenkins if you want in-repo build recipies out of the box.

Elvis

>
> Now I just need to go though all the configuration details. If anyone knows 
> any really pragmatic documentation on how to setup Jenkins server with GitHub 
> and how to setup a worker on Mac and Windows, please share.
>
> Thanks,
>
> Best regards,
>
> Nuno
>
> On 13 Feb 2019, at 19:02, Elvis Stansvik  wrote:
>
> 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
___
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]

Hey,

Thank you all for sharing your solutions and approaches. Among here there are 
two obvious winners:

- Jenkins
- Buildbot

I want to keep the build config within the project so I guess Jenkins will be 
my way to go.

Now I just need to go though all the configuration details. If anyone knows any 
really pragmatic documentation on how to setup Jenkins server with GitHub and 
how to setup a worker on Mac and Windows, please share.

Thanks,

Best regards,

Nuno

> On 13 Feb 2019, at 19:02, Elvis Stansvik  wrote:
> 
> 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] 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] 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

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 <https://twitter.com/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  <mailto:chg...@gmail.com>> 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] What are you using for continuous integration?

[Christian Gagneraud]

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] What are you using for continuous integration?

[Christian Gagneraud]

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

>
> 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] What are you using for continuous integration?

[Jérôme Godbout]

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!

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] What are you using for continuous integration?

[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?

Thanks!

Best,

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