Contract tests

Hi all,
I am working on contract tests.

I am trying to configure project to run tests on a Jenkins platform.
I am using docker-compose configuration file from blue service.
Also I override docker-compose file to configure contract test.
I need ip adres to run all services(like in blue service).

For Jenkins I need also number of port. I think port 80 is busy now.
I think I can add “NGINX_PORT=80” variable to .env file.

Concract tests will be running using bash script like this comand: “./run_contract_tests.sh -v 172.0.0.1 80”

What do you think?

Regards,
Przemek

Hi,

It’d help if you could clarify:

I’m not sure why you think you need a host port for this, or why you have to over-ride the compose file?

The current compose file here: https://github.com/OpenLMIS/openlmis-contract-tests/blob/master/docker-compose.requisition-service.yml

Looks like it’s an older setup - before blue and the services all communicated through nginx. I would think a correct setup would be to update the above compose file to match blue, and then update it so that the contract test service (docker compose service) is linked to nginx and waits for it to stop returning 503 (bad gateways) for services that are starting.

Does this make sense? If not lets schedule some time with a lead that’s worked on openlmis-blue / CI/CD recently to make sure we get the setup matching what we’ve recently made to Blue.

Best,
Josh

···

On Wednesday, October 5, 2016 at 11:05:19 AM UTC-7, Przemysław Studziński wrote:

Hi all,
I am working on contract tests.

I am trying to configure project to run tests on a Jenkins platform.
I am using docker-compose configuration file from blue service.
Also I override docker-compose file to configure contract test.
I need ip adres to run all services(like in blue service).

For Jenkins I need also number of port. I think port 80 is busy now.
I think I can add “NGINX_PORT=80” variable to .env file.

Concract tests will be running using bash script like this comand: “./run_contract_tests.sh -v 172.0.0.1 80”

What do you think?

Regards,
Przemek

Yes, the blue setup is being migrated here.

  I've might have caused some confusion by mentioning to Przemek that port 80 won't be free on the CI server. I overlooked the fact that contract tests themselves also run in a docker container - in that case we should be able to make services talk to each other through that nginx container link ( for example). Is that what you mean?

Regards,

Paweł
···

http://nginx_proxy/requisitions
On 06.10.2016 00:50, Josh Zamor wrote:

Hi,

    It'd help if you could clarify:



     - is the issue you're having on the public Jenkins?  build.openlmis.org?



    I'm not sure why you think you need a host port for this, or why you have to over-ride the compose file?



    The current compose file here:  Looks like it's an older setup - before blue and the services all communicated through nginx.  I would think a correct setup would be to update the above compose file to match blue, and then update it so that the contract test service (docker compose service) is linked to nginx and waits for it to stop returning 503 (bad gateways) for services that are starting. Does this make sense?  If not lets schedule some time with a lead that's worked on openlmis-blue / CI/CD recently to make sure we get the setup matching what we've recently made to Blue. Best, Josh On Wednesday, October 5, 2016 at 11:05:19 AM UTC-7, Przemysław Studziński wrote:

  You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.

  To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

  To post to this group, send email to openlmis-dev@googlegroups.com.

  To view this discussion on the web visit [https://groups.google.com/d/msgid/openlmis-dev/44a66a6f-bd29-4634-81ae-27929099fc5f%40googlegroups.com](https://groups.google.com/d/msgid/openlmis-dev/44a66a6f-bd29-4634-81ae-27929099fc5f%40googlegroups.com?utm_medium=email&utm_source=footer).

  For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

https://github.com/OpenLMIS/openlmis-contract-tests/blob/master/docker-compose.requisition-service.yml

Hi all,

        I am working on contract tests.



        I am trying to configure project to run tests on a Jenkins platform.

        I am using docker-compose configuration file from blue service.

        Also I override docker-compose file to configure contract test.

        I need ip adres to run all services(like in blue service).



        For Jenkins I need also number of port. I think port 80 is busy now.

        I think I can add "NGINX_PORT=80" variable to .env file.



        Concract tests will be running using  bash script like this comand: "./run_contract_tests.sh  -v 172.0.0.1 80"



         What do you think?



        Regards,

        Przemek

That sounds right Pawel, thanks.

···

On Thursday, October 6, 2016 at 5:16:02 AM UTC-7, Paweł Gesek wrote:

Yes, the blue setup is being migrated here.

  I've might have caused some confusion by mentioning to Przemek that port 80 won't be free on the CI server. I overlooked the fact that contract tests themselves also run in a docker container - in that case we should be able to make services talk to each other through that nginx container link ([http://nginx_proxy/requisitions](http://nginx_proxy/requisitions)
  for example). Is that what you mean?

Regards,

Paweł

On 06.10.2016 00:50, Josh Zamor wrote:

Hi,

    It'd help if you could clarify:



     - is the issue you're having on the public Jenkins?  [build.openlmis.org](http://build.openlmis.org)?



    I'm not sure why you think you need a host port for this, or why you have to over-ride the compose file?



    The current compose file here:  [https://github.com/OpenLMIS/openlmis-contract-tests/blob/master/docker-compose.requisition-service.yml](https://github.com/OpenLMIS/openlmis-contract-tests/blob/master/docker-compose.requisition-service.yml)



    Looks like it's an older setup - before blue and the services all communicated through nginx.  I would think a correct setup would be to update the above compose file to match blue, and then update it so that the contract test service (docker compose service) is linked to nginx and waits for it to stop returning 503 (bad gateways) for services that are starting.



    Does this make sense?  If not lets schedule some time with a lead that's worked on openlmis-blue / CI/CD recently to make sure we get the setup matching what we've recently made to Blue.



    Best,

    Josh



    On Wednesday, October 5, 2016 at 11:05:19 AM UTC-7, Przemysław Studziński wrote:

Hi all,

        I am working on contract tests.



        I am trying to configure project to run tests on a Jenkins platform.

        I am using docker-compose configuration file from blue service.

        Also I override docker-compose file to configure contract test.

        I need ip adres to run all services(like in blue service).



        For Jenkins I need also number of port. I think port 80 is busy now.

        I think I can add "NGINX_PORT=80" variable to .env file.



        Concract tests will be running using  bash script like this comand: "./run_contract_tests.sh  -v 172.0.0.1 80"



         What do you think?



        Regards,

        Przemek

  You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.

  To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

  To post to this group, send email to openlmis-dev@googlegroups.com.

  To view this discussion on the web visit [https://groups.google.com/d/msgid/openlmis-dev/44a66a6f-bd29-4634-81ae-27929099fc5f%40googlegroups.com](https://groups.google.com/d/msgid/openlmis-dev/44a66a6f-bd29-4634-81ae-27929099fc5f%40googlegroups.com?utm_medium=email&utm_source=footer).

  For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).