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 <chg...@gmail.com> wrote:
> 
> On Wed, 13 Feb 2019 at 13:54, Christian Gagneraud <chg...@gmail.com 
> <mailto:chg...@gmail.com>> wrote:
>> 
>> On Wed, 13 Feb 2019 at 13:46, Jérôme Godbout <godbo...@amotus.ca> 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 <interest-boun...@qt-project.org> On Behalf Of Nuno Santos
>>> Sent: February 12, 2019 6:05 PM
>>> To: Interests Qt (interest@qt-project.org) <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

Reply via email to