Date

16 Oct 2018

7am PST / 4pm CET

Meeting Link

https://zoom.us/j/737202874

Attendees

Discussion items

Time	Item	Who	Notes
5m	Agenda and action item review	Josh
35m	Feature flags	Josh Zamor (Deactivated)	Use in 3.5? Followup on multiple suppliers. (followup Nikodem Graczewski (Unlicensed), Josh Zamor (Deactivated), Sebastian Brudziński) Is this pressing? Is the only alternative branching? Briefly show Togglz Console and local example Testing Improvements to be had: Security of console Redis FeatureProvider - feature discovery from other services (nice to have) Expose features and states to web ui
15m	TeamCity Remote Run demo	Wesley Brown
5 min	Overview of integration tests from referencedata for database migrations	Mateusz Kwiatkowski	OLMIS-5303 - Getting issue details... STATUS Integration test for migrations in referencedata service Dev Forum post
(dev forum or next time)	Followup on audit log initializer	Josh Zamor (Deactivated)	We completed OLMIS-3078 - Getting issue details... STATUS which will help production data sets, however for demo data we would still iterate over all the demo data records on the first start as they don't have snapshots yet. Is a slow startup still / more an issue? With the increased size of the demo data that we're adding, and thoughts to have millions of records, do we think we have an issue? When Ref Distro is started, DB usage is sustaining 100% CPU for > 5 minutes
(next time)	Orderable versioning	Chongsun Ahn (Unlicensed)	Continue the show and tell on the how
(not pressing atm)	DHIS2 followup on how (keeping this on the agenda to discuss the plan prior to implementation, however implementation isn't pressing on this just yet)	Josh Zamor (Deactivated)	There are meeting notes from https://openlmis.atlassian.net/wiki/x/LYDSGQ Still items being figured out Plan is to start this after the mCSD / FHIR work

Notes

Team City

Benefits:
- Commit-less, you can run a pipeline without a commit. In Jenkins the way we'd experiment with code is to commit to a branch, and then Jenkins et al would report on what's happened.
- UX is quite a bit nicer.
Non-trivial to re-tool our build infrastructure from Jenkins to TC
- We could have an opportunity to experiment more with this on a greenfield service/project.
Why didn't we go with Travis-CI? At project kickoff Travis-CI was having issues with build start latency for open source projects. 30m or longer was typical.
Do we need to save on costs? Not that we're aware of. It'd be nice however we're also being told we're under spent on server costs.
Can Jenkins do something similar?

Migration Testing

Pros:

Tests more than what just starting the service does

Cons:

Tests as written aren't very useful when they pass

Mateusz to continue the discussion on dev forum

Action Items

Wesley Brown to do a quick search if there's an obvious way to replicate TC's "remote run" in Jenkins
Josh Zamor (Deactivated) to schedule supplying partners & feature flags discussion
Mateusz Kwiatkowski to followup on migration testing on dev forum: brainstorming