Gabe Montero

On Tue, Jul 14, 2020 at 11:34 AM Ben Parees wrote: > What I'm wondering is when this import happens -- is it once for each > major OCP version...

Cool idea, regardless if it remains as a "change to triggers" as originally cited, or if it evolves into a "something additional instead of changing something existing" as the existing...

@waveywaves - FYI in case you were unaware ^^ @waveywaves == Vibhav :-)

@ImJasonH - in case this has not bubbled up in your RH onboarding - a possible historical reference for launching jenkins and jenkins pipelines from k8s (in this case k8s...

@jkhelil when you get the chance can you launch your own OCP cluster, run dev_setup.sh -- use-local-branch , and capture a screen shot of the new panels and attach that...

Certainly better than before @jkhelil but it looks like something got lost when I tried to describe it to you before. I was hoping it would look like how the...

Minimally something to definitely highlight up top in the documentation, in both pipeline and trigger projects. And yes, as @dibyom noted here and as myself and others have noted in...

@sayan-biswas the upgrade test failure and at first blush does not seem like a flake: ``` + kubectl apply -k /source/developer/openshift/work/environment/compute/api-ci-53b85bfcda-pozs-p3-openshiftapps-com Error from server (Invalid): error when applying patch: {"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"argoproj.io/v1alpha1\",\"kind\":\"Application\",\"metadata\":{\"annotations\":{},\"name\":\"pipeline-service\",\"namespace\":\"openshift-gitops\"},\"spec\":{\"destination\":{\"namespace\":\"pipeline-service\",\"server\":\"https://kubernetes.default.svc\"},\"project\":\"default\",\"sources\":[{\"path\":\"developer/openshift/gitops/argocd/pipeline-service\",\"repoURL\":\"https://github.com/openshift-pipelines/pipeline-service.git\",\"targetRevision\":\"43e768066fa0f61b9634127d8280be634d48cdce\"}],\"syncPolicy\":{\"automated\":{\"prune\":true,\"selfHeal\":true},\"retry\":{\"backoff\":{\"duration\":\"10s\",\"factor\":2,\"maxDuration\":\"3m\"},\"limit\":-1},\"syncOptions\":[\"CreateNamespace=true\"]}}}\n"}},"spec":{"destination":{"namespace":"pipeline-service"},"source":null,"sources":[{"path":"developer/openshift/gitops/argocd/pipeline-service","repoURL":"https://github.com/openshift-pipelines/pipeline-service.git","targetRevision":"43e768066fa0f61b9634127d8280be634d48cdce"}]}}...

> > The changes look OK best to my understanding @sayan-biswas > > Given the complexity / amount of change, attempting to bootstrap from infra-deployments where you point pipeline-service to...

> > > The changes look OK best to my understanding @sayan-biswas > > > Given the complexity / amount of change, attempting to bootstrap from infra-deployments where you point...