opened
stevef1uk
username_0
### Summary 

### Steps to reproduce the behavior

### Expected behavior

### Actual behavior

### Jx version

The output of `jx version` is:

```
COPY OUTPUT HERE
```

### Jenkins type

<!--
Select which Jenkins installation type are you using. 
-->
- [ ] Classic Jenkins
- [ ] Serverless Jenkins

### Kubernetes cluster

<!--
What kind of Kubernetes cluster are you using & how did you create it?
-->

### Operating system / Environment

<!--
In which environment are you running the jx CLI?
-->
Build Success - but not really with qinikube for quoickstarts etc
issue
created
ccojocar
username_1
@username_0 How did you expose the prow `hook` with minikube? This endpoint needs to be reachable from GitHub.
comment
created
stevef1uk
username_0
I tried to use a sub domain DNS record to route through to my mac from the internet and then used kubectl port-forward on the mac. However, I had to guess that I needed to route to the 'hook' service. I manually edited the GitHub Webhooks, but wasn't able to get it to redeliver successfully. I know the route through to my mac worked (having opened a port on my internet router for this) as  I stood up a temporary web page to check that part. I am guessing that the port forwarding to prow on minikube didn't;t work. Any clue as to which service / pod/port I should be targeting?

Also, I am surprised that a call from GitHub is required to build the code initially?
comment
created
ginosubscriptions
username_2
I'm actually having the exact same problem on the latest JX3 version with Minikube. **jx create quickstart** completes successfully, my webhooks are reachable from outside the Minikube cluster (i.e.: GitHub can actually complete pull requests => it does it for the jx3-minikube repository). Still, once the entire creation process has run, no application is available (from **jx get applications**).
Not clear what's happening. The only thing I can say is that I tested it with the GCP/GKE setup and one of the big differences I see between the Minikube install of JX3 and the Google Kubernetes Engine one is that there are no Nexus or Helm repositories created (also no ingresses corresponding with these). Maybe that is normal, but I would consider those key components for deployments. I also see no "build job" logs with **jx get build logs** for the quickstart.
comment
created
ginosubscriptions
username_2
Given my previous comment on "it's happening to me too", would it be possible to reopen this issue, or should I clone and create a new one?
comment