I would like to mention again the issue that had, to my knowledge, been already discussed several times but still, no solution to it was found. One has to perform tests with the use of the most recent changes. It takes some time for the changes to appear on the test and performance servers, it is also impossible to test for some time after the server restarts because of the Bad Gateway error. When changes are made frequently, it can block testing for a really long time. There are situations in which for this reason the testing of a ticket which normally should take up to 20 minutes can take even two hours (e.g. this is what happened today). I think something needs to be done about it, as it can considerably slow the work down.
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
--
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 openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/e1e543e7-c4b6-4179-bd95-fb54fc4c470c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAHq-FDP6sTOkGjTTj5XsdKENq6VpZUHZ58_OOsAKDsWq3pP_hg%40mail.gmail.com.
I'd be ok with changing when test is reloaded, so it only happens once an hour (perhaps on the hour, if possible). I think Pawel is right that we can point all our tasks to one deployment task, not ... 7 or 8
This does assume the root of the problem is that test.openlmis.org isn't predictable, which makes working with the test server difficult.
An alternative (just to bring it up) would be to use UAT as our QA server, and make updating that server something that is only done when QA-ing a ticket.
Nick Reid | nick...@villagereach.org
Software Developer, Information Systems Group
VillageReach Starting
at the Last Mile
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA
CELL: +1.510.410.0020
SKYPE: nickdotreid
www.villagereach.org
I'd be ok with changing when test is reloaded, so it only happens once an hour (perhaps on the hour, if possible). I think Pawel is right that we can point all our tasks to one deployment task, not ... 7 or 8
This does assume the root of the problem is that test.openlmis.org isn't predictable, which makes working with the test server difficult.
An alternative (just to bring it up) would be to use UAT as our QA server, and make updating that server something that is only done when QA-ing a ticket.
Nick Reid | nick.reid@villagereach.org
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAHq-FDP6sTOkGjTTj5XsdKENq6VpZUHZ58_OOsAKDsWq3pP_hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
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 openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CY4PR02MB21997D0D5459777D3F666AC894320%40CY4PR02MB2199.namprd02.prod.outlook.com.
Lukasz --
Could you explain the need for a developer to get their changes "live" on test quickly?
I feel like getting to some concrete needs might help guide this discussion....
❤znick
Nick Reid | nick...@villagereach.org
Software Developer, Information Systems Group
VillageReach Starting
at the Last Mile
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA
CELL: +1.510.410.0020
SKYPE: nickdotreid
www.villagereach.org
--
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 openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/8d984066-8da8-4bcd-b89f-bc8b51a4c5e6%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAJzpfksNCfPR19v8Ck3w5gLjgs9o2V3K%2B0C94zm3CPXFYvquQ%40mail.gmail.com.
If now we change the endpoint in that way the schema will be modified and other services will not be able to handle the new schema - like move endpoint to pageable version. This will probably make the system unavailable, the QA will be blocked and we are not be able to do anything until to the next deploy to the test server which will fix the issue. '
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAdp53yahvG1LmcpbyM64PLJxBy2VnP_oJhscEoh5zRwTG3D0g%40mail.gmail.com.
@here Re: Dev forum discussion about testing environment "Frequent deploys slowing QA down or blocking it"
We would like to come to an agreement on which environment to use for testing. Since uat.openlmis.org is not used for demos anymore (we demo in demo-v3.openlmis.org), we would like to have the test team (@sammieim, @jbebak) use uat instead of test.openlmis.org so that we can avoid QA downtime. I would like to hear back from the teams if anyone disagrees. Otherwise we will move forward with uat.
- If anyone is using uat for any other purposes, please let @joshzamor, @jbebak and myself know
- Deployment to uat will be scheduled. Should this be hourly or a different schedule? Please provide feedback here.
- @joshzamor will notify the channel here when the environment is ready (deploy jobs scheduled and running)
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/8d984066-8da8-4bcd-b89f-bc8b51a4c5e6%40googlegroups.com.
--Paweł Albecki
Software Developer
palb...@soldevelo.com
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
--
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...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAAJzpfksNCfPR19v8Ck3w5gLjgs9o2V3K%2B0C94zm3CPXFYvquQ%40mail.gmail.com.
SolDevelo Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
--
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...@googlegroups.com.
This issue tracked the change: https://openlmis.atlassian.net/browse/OLMIS-3873
Thanks for bringing this up Joanna, please take a look at http://uat.openlmis.org and let us know if this new approach helps your process.
Best,
Josh