jx: Jx boot creating clusters that CI but don't CD...
Summary
I have just created a fresh cluster instance with jx boot, including external DNS, TLS and vault. The cluster appears to run build pipelines but is not automatically processing PRs on Dev or Staging environments.
Viewing the PRs on these environments shows ‘1 pending check’ and ‘tide Pending - Not mergeable’.
Jx version
The output of jx version is:
jx 2.0.902
Kubernetes cluster v1.13.10-gke.0
kubectl v1.16.2
helm client Client: v2.14.0+g05811b8
git 2.21.0
Operating System Mac OS X 10.13.6 build 17G6030
Jenkins type
- Serverless Jenkins X Pipelines (Tekton + Prow)
- Classic Jenkins
Kubernetes cluster
jx boot
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 28 (27 by maintainers)
Commits related to this issue
- fix: Stop lowercasing environmentGitOwner value Prow is case-sensitive when it comes to matching events for an org/repo name combo to a configured org/repo name combo in its configuration. So if you'... — committed to abayer/jx by abayer 4 years ago
- fix: Stop lowercasing environmentGitOwner value Prow is case-sensitive when it comes to matching events for an org/repo name combo to a configured org/repo name combo in its configuration. So if you'... — committed to abayer/jx by abayer 4 years ago
- fix: environment repo SourceRepository names should be lower-case relates to https://github.com/jenkins-x/jx/issues/5914 Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com> — committed to abayer/jxboot-resources by abayer 4 years ago
- fix: Stop lowercasing environmentGitOwner value Prow is case-sensitive when it comes to matching events for an org/repo name combo to a configured org/repo name combo in its configuration. So if you'... — committed to jenkins-x/jx by abayer 4 years ago
- fix: Stop lowercasing environmentGitOwner value Prow is case-sensitive when it comes to matching events for an org/repo name combo to a configured org/repo name combo in its configuration. So if you'... — committed to daveconde/jx by abayer 4 years ago
I noticed this issue as well, and environments I created later with
jx create environmentworked correcty (PRs getting merged automatically, deployments getting done upon merging to master). It’s just the default environments that get created during installations that do not seem to trigger the pipelines.