Official Docker image
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it. This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests. We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2] With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it. I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies. [1] https://gitlab.com/koha-community/koha-testing-docker [2] https://gitlab.com/tomascohen/koha-dpkg-docker -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
bravo!!!! 2018-04-17 15:30 GMT+02:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it.
This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests.
We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2]
With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it.
I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies.
[1] https://gitlab.com/koha-community/koha-testing-docker [2] https://gitlab.com/tomascohen/koha-dpkg-docker
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Hi Tomas, I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that. I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.) I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are: WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string. WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory? I’ll have to try that after lunch… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Tomas Cohen Arazi Sent: Tuesday, 17 April 2018 11:30 PM To: koha-devel <koha-devel@lists.koha-community.org> Subject: [Koha-devel] Official Docker image Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it. This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests. We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2] With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it. I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies. [1] https://gitlab.com/koha-community/koha-testing-docker [2] https://gitlab.com/tomascohen/koha-dpkg-docker -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F
Try docker-compose up. Not run. The readme is outdated! El mié., 9 de may. de 2018 10:45 p. m., David Cook <dcook@prosentient.com.au> escribió:
Hi Tomas,
I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that.
I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.)
I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are:
WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string.
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory?
I’ll have to try that after lunch…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Tomas Cohen Arazi *Sent:* Tuesday, 17 April 2018 11:30 PM *To:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* [Koha-devel] Official Docker image
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it.
This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests.
We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2]
With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it.
I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies.
[1] https://gitlab.com/koha-community/koha-testing-docker
[2] https://gitlab.com/tomascohen/koha-dpkg-docker
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Readmes are not supposed to be read! El mié., 9 de may. de 2018 23:14, Tomas Cohen Arazi <tomascohen@gmail.com> escribió:
Try docker-compose up. Not run. The readme is outdated!
El mié., 9 de may. de 2018 10:45 p. m., David Cook < dcook@prosentient.com.au> escribió:
Hi Tomas,
I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that.
I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.)
I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are:
WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string.
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory?
I’ll have to try that after lunch…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Tomas Cohen Arazi *Sent:* Tuesday, 17 April 2018 11:30 PM *To:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* [Koha-devel] Official Docker image
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it.
This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests.
We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2]
With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it.
I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies.
[1] https://gitlab.com/koha-community/koha-testing-docker
[2] https://gitlab.com/tomascohen/koha-dpkg-docker
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Jonathan, go to bed! On 10/05/18 13:29, Jonathan Druart wrote:
Readmes are not supposed to be read!
El mié., 9 de may. de 2018 23:14, Tomas Cohen Arazi <tomascohen@gmail.com <mailto:tomascohen@gmail.com>> escribió:
Try docker-compose up. Not run. The readme is outdated!
El mié., 9 de may. de 2018 10:45 p. m., David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au>> escribió:
Hi Tomas,
I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that.
I was able to set SYNC_REPO using “$env:SYNC_REPO = 'C:\Users\dcook\Git\koha'” in powershell… Retried “docker-compose build” and got the following: WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Decided to just try “docker-compose up” and it’s downloading images so I’ll let you know how it goes… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi [mailto:tomascohen@gmail.com] Sent: Thursday, 10 May 2018 12:15 PM To: David Cook <dcook@prosentient.com.au> Cc: koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Official Docker image Try docker-compose up. Not run. The readme is outdated! El mié., 9 de may. de 2018 10:45 p. m., David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió: Hi Tomas, I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that. I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.) I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are: WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string. WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory? I’ll have to try that after lunch… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> [mailto:koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> ] On Behalf Of Tomas Cohen Arazi Sent: Tuesday, 17 April 2018 11:30 PM To: koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > Subject: [Koha-devel] Official Docker image Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it. This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests. We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2] With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it. I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies. [1] https://gitlab.com/koha-community/koha-testing-docker [2] https://gitlab.com/tomascohen/koha-dpkg-docker -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F
For anyone using Docker for Windows, one annoying thing to note is that Docker for Windows requires HyperV to be activated, and that conflicts with other virtualization software like Vmware (and I think Virtualbox although I haven’t tried that I think). Enabling/disabling HyperV isn’t that hard but it does require a restart which can be irritating if you’re in the middle of other work. Still… Docker seems neat. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of David Cook Sent: Thursday, 10 May 2018 1:35 PM To: 'Tomas Cohen Arazi' <tomascohen@gmail.com> Cc: 'koha-devel' <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Official Docker image I was able to set SYNC_REPO using “$env:SYNC_REPO = 'C:\Users\dcook\Git\koha'” in powershell… Retried “docker-compose build” and got the following: WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Decided to just try “docker-compose up” and it’s downloading images so I’ll let you know how it goes… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi [mailto:tomascohen@gmail.com] Sent: Thursday, 10 May 2018 12:15 PM To: David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > Cc: koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > Subject: Re: [Koha-devel] Official Docker image Try docker-compose up. Not run. The readme is outdated! El mié., 9 de may. de 2018 10:45 p. m., David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió: Hi Tomas, I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that. I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.) I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are: WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string. WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory? I’ll have to try that after lunch… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> [mailto:koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> ] On Behalf Of Tomas Cohen Arazi Sent: Tuesday, 17 April 2018 11:30 PM To: koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > Subject: [Koha-devel] Official Docker image Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it. This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests. We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2] With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it. I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies. [1] https://gitlab.com/koha-community/koha-testing-docker [2] https://gitlab.com/tomascohen/koha-dpkg-docker -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F
You need to docker-compose down between tries. Otherwise MySQL is not refreshed and you might have inconsistent data on it. El jue., 10 de may. de 2018 3:33 a. m., David Cook <dcook@prosentient.com.au> escribió:
For anyone using Docker for Windows, one annoying thing to note is that Docker for Windows requires HyperV to be activated, and that conflicts with other virtualization software like Vmware (and I think Virtualbox although I haven’t tried that I think).
Enabling/disabling HyperV isn’t that hard but it does require a restart which can be irritating if you’re in the middle of other work.
Still… Docker seems neat.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *David Cook
*Sent:* Thursday, 10 May 2018 1:35 PM *To:* 'Tomas Cohen Arazi' <tomascohen@gmail.com>
*Cc:* 'koha-devel' <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
I was able to set SYNC_REPO using “$env:SYNC_REPO = 'C:\Users\dcook\Git\koha'” in powershell…
Retried “docker-compose build” and got the following:
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Decided to just try “docker-compose up” and it’s downloading images so I’ll let you know how it goes…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* Tomas Cohen Arazi [mailto:tomascohen@gmail.com <tomascohen@gmail.com>] *Sent:* Thursday, 10 May 2018 12:15 PM *To:* David Cook <dcook@prosentient.com.au> *Cc:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
Try docker-compose up. Not run. The readme is outdated!
El mié., 9 de may. de 2018 10:45 p. m., David Cook < dcook@prosentient.com.au> escribió:
Hi Tomas,
I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that.
I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.)
I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are:
WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string.
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory?
I’ll have to try that after lunch…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Tomas Cohen Arazi *Sent:* Tuesday, 17 April 2018 11:30 PM *To:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* [Koha-devel] Official Docker image
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it.
This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests.
We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2]
With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it.
I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies.
[1] https://gitlab.com/koha-community/koha-testing-docker
[2] https://gitlab.com/tomascohen/koha-dpkg-docker
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Care to update the README.md? I would send a merge request, but I already am running behind on a few things. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi [mailto:tomascohen@gmail.com] Sent: Thursday, 10 May 2018 8:41 PM To: David Cook <dcook@prosentient.com.au> Cc: koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Official Docker image You need to docker-compose down between tries. Otherwise MySQL is not refreshed and you might have inconsistent data on it. El jue., 10 de may. de 2018 3:33 a. m., David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió: For anyone using Docker for Windows, one annoying thing to note is that Docker for Windows requires HyperV to be activated, and that conflicts with other virtualization software like Vmware (and I think Virtualbox although I haven’t tried that I think). Enabling/disabling HyperV isn’t that hard but it does require a restart which can be irritating if you’re in the middle of other work. Still… Docker seems neat. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> [mailto:koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> ] On Behalf Of David Cook Sent: Thursday, 10 May 2018 1:35 PM To: 'Tomas Cohen Arazi' <tomascohen@gmail.com <mailto:tomascohen@gmail.com> > Cc: 'koha-devel' <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > Subject: Re: [Koha-devel] Official Docker image I was able to set SYNC_REPO using “$env:SYNC_REPO = 'C:\Users\dcook\Git\koha'” in powershell… Retried “docker-compose build” and got the following: WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Decided to just try “docker-compose up” and it’s downloading images so I’ll let you know how it goes… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi [mailto:tomascohen@gmail.com] Sent: Thursday, 10 May 2018 12:15 PM To: David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > Cc: koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > Subject: Re: [Koha-devel] Official Docker image Try docker-compose up. Not run. The readme is outdated! El mié., 9 de may. de 2018 10:45 p. m., David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió: Hi Tomas, I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that. I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.) I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are: WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string. WARNING: The COVERAGE variable is not set. Defaulting to a blank string. WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string. db uses an image, skipping es uses an image, skipping memcached uses an image, skipping selenium uses an image, skipping koha uses an image, skipping Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory? I’ll have to try that after lunch… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> [mailto:koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> ] On Behalf Of Tomas Cohen Arazi Sent: Tuesday, 17 April 2018 11:30 PM To: koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > Subject: [Koha-devel] Official Docker image Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it. This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests. We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2] With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it. I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies. [1] https://gitlab.com/koha-community/koha-testing-docker [2] https://gitlab.com/tomascohen/koha-dpkg-docker -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F
Greetings, El jue., 10 de may. de 2018 3:33 a. m., David Cook <dcook@prosentient.com.au> escribió:
For anyone using Docker for Windows, one annoying thing to note is that Docker for Windows requires HyperV to be activated,
I can confirm that annoyance, which is why I was glad to move my work laptop to Ubuntu.
and that conflicts with other virtualization software like Vmware
While I have not used Vmware...
(and I think Virtualbox although I haven’t tried that I think).
I can confirm that it is true with Virtualbox on Windows. Windows doesn’t like letting multiple virtualization environments run at the same time.
Enabling/disabling HyperV isn’t that hard but it does require a restart which can be irritating if you’re in the middle of other work.
Yep.
Still… Docker seems neat.
It is. Another work project of mine uses codeship builds for continuous integration testing and publishing of changes which get pushed to an Amazon container. GPML, Mark Tompsett
Please file an issue, maybe someone with time to take care picks it? El jue., 10 may. 2018 a las 21:08, David Cook (<dcook@prosentient.com.au>) escribió:
Care to update the README.md? I would send a merge request, but I already am running behind on a few things.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* Tomas Cohen Arazi [mailto:tomascohen@gmail.com] *Sent:* Thursday, 10 May 2018 8:41 PM
*To:* David Cook <dcook@prosentient.com.au> *Cc:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
You need to docker-compose down between tries. Otherwise MySQL is not refreshed and you might have inconsistent data on it.
El jue., 10 de may. de 2018 3:33 a. m., David Cook < dcook@prosentient.com.au> escribió:
For anyone using Docker for Windows, one annoying thing to note is that Docker for Windows requires HyperV to be activated, and that conflicts with other virtualization software like Vmware (and I think Virtualbox although I haven’t tried that I think).
Enabling/disabling HyperV isn’t that hard but it does require a restart which can be irritating if you’re in the middle of other work.
Still… Docker seems neat.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *David Cook
*Sent:* Thursday, 10 May 2018 1:35 PM *To:* 'Tomas Cohen Arazi' <tomascohen@gmail.com>
*Cc:* 'koha-devel' <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
I was able to set SYNC_REPO using “$env:SYNC_REPO = 'C:\Users\dcook\Git\koha'” in powershell…
Retried “docker-compose build” and got the following:
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Decided to just try “docker-compose up” and it’s downloading images so I’ll let you know how it goes…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* Tomas Cohen Arazi [mailto:tomascohen@gmail.com <tomascohen@gmail.com>] *Sent:* Thursday, 10 May 2018 12:15 PM *To:* David Cook <dcook@prosentient.com.au> *Cc:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
Try docker-compose up. Not run. The readme is outdated!
El mié., 9 de may. de 2018 10:45 p. m., David Cook < dcook@prosentient.com.au> escribió:
Hi Tomas,
I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that.
I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.)
I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are:
WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string.
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory?
I’ll have to try that after lunch…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Tomas Cohen Arazi *Sent:* Tuesday, 17 April 2018 11:30 PM *To:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* [Koha-devel] Official Docker image
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it.
This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests.
We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2]
With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it.
I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies.
[1] https://gitlab.com/koha-community/koha-testing-docker
[2] https://gitlab.com/tomascohen/koha-dpkg-docker
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
I hope you can check the updated README.md, David Regards El vie., 11 may. 2018 a las 14:48, Tomas Cohen Arazi (<tomascohen@gmail.com>) escribió:
Please file an issue, maybe someone with time to take care picks it?
El jue., 10 may. 2018 a las 21:08, David Cook (<dcook@prosentient.com.au>) escribió:
Care to update the README.md? I would send a merge request, but I already am running behind on a few things.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* Tomas Cohen Arazi [mailto:tomascohen@gmail.com] *Sent:* Thursday, 10 May 2018 8:41 PM
*To:* David Cook <dcook@prosentient.com.au> *Cc:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
You need to docker-compose down between tries. Otherwise MySQL is not refreshed and you might have inconsistent data on it.
El jue., 10 de may. de 2018 3:33 a. m., David Cook < dcook@prosentient.com.au> escribió:
For anyone using Docker for Windows, one annoying thing to note is that Docker for Windows requires HyperV to be activated, and that conflicts with other virtualization software like Vmware (and I think Virtualbox although I haven’t tried that I think).
Enabling/disabling HyperV isn’t that hard but it does require a restart which can be irritating if you’re in the middle of other work.
Still… Docker seems neat.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *David Cook
*Sent:* Thursday, 10 May 2018 1:35 PM *To:* 'Tomas Cohen Arazi' <tomascohen@gmail.com>
*Cc:* 'koha-devel' <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
I was able to set SYNC_REPO using “$env:SYNC_REPO = 'C:\Users\dcook\Git\koha'” in powershell…
Retried “docker-compose build” and got the following:
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Decided to just try “docker-compose up” and it’s downloading images so I’ll let you know how it goes…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* Tomas Cohen Arazi [mailto:tomascohen@gmail.com <tomascohen@gmail.com>] *Sent:* Thursday, 10 May 2018 12:15 PM *To:* David Cook <dcook@prosentient.com.au> *Cc:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Official Docker image
Try docker-compose up. Not run. The readme is outdated!
El mié., 9 de may. de 2018 10:45 p. m., David Cook < dcook@prosentient.com.au> escribió:
Hi Tomas,
I’ve decided to try Docker for Windows, and to try out your koha-testing-docker using that.
I cloned the git repository from https://gitlab.com/koha-community/koha-testing-docker and I’m reading the README.md, but I stumble at “docker-compose build”. (Initially I didn’t read the README.md and just tried ‘docker build’ and that looked OK at a glance.)
I see “Requirement: The SYNC_REPO variable needs to be defined and contain the full path for a Koha's git repository clone”, but the error messages I get are:
WARNING: The SYNC_REPO variable is not set. Defaulting to a blank string.
WARNING: The COVERAGE variable is not set. Defaulting to a blank string.
WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string.
WARNING: The LOCAL_USER_ID variable is not set. Defaulting to a blank string.
db uses an image, skipping
es uses an image, skipping
memcached uses an image, skipping
selenium uses an image, skipping
koha uses an image, skipping
Is SYNC_REPO supposed to be a path to a http://git.koha-community.org/koha.git directory?
I’ll have to try that after lunch…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g>
Ultimo, NSW <https://maps.google.com/?q=72/330+Wattle+St+Ultimo,+NSW&entry=gmail&source=g> 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Tomas Cohen Arazi *Sent:* Tuesday, 17 April 2018 11:30 PM *To:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* [Koha-devel] Official Docker image
Hi everyone, on the CI front, I have recently introduced (successfully) the broad use of Docker images to run the full test suite. This project, named koha-testing-docker [1], evolved into a usable development environment too. Right now I'm trying to spend some time on porting kohadevbox things into it.
This Docker image is built and published automatically by our Jenkins server, and then used in the three nodes we have to run the tests.
We also have a Docker image for building koha-* packages wherever we need to (yes, we want to automate this, and properly test the generated packages using the CI infrastructure). [2]
With this knowledge, and the infrastructure part of it solved, I would like to start publishing an official Docker image of Koha. Once we have this, the koha-testing-docker tools would be rebuilt on top of it.
I raise the subject in light of recent discussions about supported OSs, Perl versions and dependencies.
[1] https://gitlab.com/koha-community/koha-testing-docker
[2] https://gitlab.com/tomascohen/koha-dpkg-docker
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
participants (6)
-
Bob Birchall -
David Cook -
Hugo Agud -
Jonathan Druart -
Mark Tompsett -
Tomas Cohen Arazi