Re: go service dependencies
toggle quoted messageShow quoted text
Recommend this as a topic for DevOps meeting first; then loop in Core or other WG as necessary once an idea/plan is in place.
From: Jeremy Phelps [mailto:jphelps@...]
Sent: Wednesday, July 18, 2018 3:08 PM
To: Conn, Trevor
Cc: edgex-tsc-devops@...; White2, James
Subject: Re: go service dependencies
Yes, we can spec a `version` parameter in glide.yaml
# The version can be a branch, tag, commit id, or a semantic version
On Wed, Jul 18, 2018 at 3:05 PM, <Trevor.Conn@...> wrote:
Dell Customer Communication
Have you seen an example/proposal for how this would be done?
I can add to our agenda under new business but we may not get to it this week as we have a pretty full
Jeremy Phelps [mailto:jphelps@...]
Sent: Wednesday, July 18, 2018 3:02 PM
edgex-tsc-devops@...; White2, James; Conn, Trevor
Subject: go service dependencies
We currently manage go deps with glide. Though we have discussed moving off of it I don't think we are currently ready. As such, we need to make sure when we are pulling internal
deps that we pull them from the correct branch since we now have california.
security-api-gateway pulls in edgex-go as a dep.
The glide.yaml for california branch (of security-api-gateway) should pull in the california branch of edgex-go.
This would be a good discussion point for the Core-WG meeting this week to look at if we should do this (if it is really an issue) for sure and some other finer points.
Join EdgeX-TSC-DevOps@lists.edgexfoundry.org to automatically receive all group messages.