Hi Trevor, A couple of comments inline. Cheers Steve. Perhaps in the reference docker deployment it is. But with us allowing alternate registry implementations, this may not always be the case, so

Hi all -- I've incorporated Steve's feedback below into a V3 document. Please see attached. Let me know if there is any further comment. Today is my last official working day of 2018 so I'd like to

Hi all -- I've attached a document that contains everything I can think of w/r/t accommodating Go Modules in our CI/CD pipeline. Moving to modules for dependency mgmt is a goal for the Edinburgh

Thanks Trevor. I’ll add this to the agenda for this week. ~James R.Gregg

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 17 January 2019 7:00am to 8:00am (GMT-08:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 24 January 2019 7:00am to 8:00am (GMT-08:00) America/Los

Hi all -- I'm going to piggy back on the thread below and loop in the Go email distro for more discussion about modules. I've attached a V2 of the previous document that was sent. It includes two more

Hi Everyone, I think there is one main problem to consider when using go mod in a mono-repo. - git tag collisions This could happen for example if when edgex-go goes from v1.0.0 to v2.0.0 if we

Jeremy, I think in terms of the added workflow complexity, it would require additional overhead to the helpdesk / release engineer to create the repos where the submodules would reside. What

James, In addition to the initial creation of the repo (which isn't a big deal) and devs needing to pull submodules, there's also the added step of having to update one repo (the one using the

Thank you Eric Is there additional overhead for setting team permissions that allow the update to the main repo? Does LF manage GitHub via infrastructure as code?

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 31 January 2019 7:00am to 8:00am (GMT-08:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 7 February 2019 7:00am to 8:00am (GMT-08:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 14 February 2019 7:00am to 8:00am (GMT-08:00) America/Los

Hi all – Attached please find a proposal for handling our releases and versioning now that we’re well on our way to using Go modules. I suggest we give this some time for review in both the DevOps

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 21 February 2019 7:00am to 8:00am (GMT-08:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 28 February 2019 7:00am to 8:00am (GMT-08:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 7 March 2019 7:00am to 8:00am (GMT-08:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 14 March 2019 7:00am to 8:00am (GMT-07:00) America/Los

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) When: Thursday, 21 March 2019 7:00am to 8:00am (GMT-07:00) America/Los