Agree! Great work and I know a lot of very hard work in a short time. Well done.

I’ve joined because I heard there was concerns about the build in edgex-go

We were talking about the CI auto build for the new repo for edgex consul...basically long story short is the consul now needs to have nexus3.edgexfoundry.org:10004/docker-edgex-consul:1.1.0 on the nightly

Oh

So this is a misunderstanding..

There was another issue where Tingyu things security-secretstore-setup has old code in it

I will address it as well

Pipelines do not run nightly. The docker-edgex-consul merge build failed, looks like an issue with the settings file on the docker login

edgex-go is a freestyle run nightly which means there will be a delay on getting code into the nightly build. Both the merge and staging jobs for edges-go are passing though

Lisa: yes I understand but the initial pipeline merge job was never trigged and when I tried to trigger the pipeline job for docker-edgex-consul it seems I triggered it wrong and it failed to build, James asked eball to trigger the job properly, I assume when that's done it should work properly

Merge job: https://jenkins.edgexfoundry.org/view/edgex-go/job/edgex-go-master-merge-go/

nexus3.edgexfoundry.org:10004/docker-edgex-consul:1.1.0

docker inspect -f"{{.Created}}" nexus3.edgexfoundry.org:10004/docker-edgex-consul:1.1.0