search

jenkins-x / jx

Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Cloud Native pipelines from Tekton
https://jenkins-x.io/
Apache License 2.0
4.58k stars 787 forks source link

DevPods: No snapshot available #6981

Closed diethardsteiner closed 4 years ago

diethardsteiner commented 4 years ago

Summary

DevPods: Release created but no snapshot. I followed the instructions of the "The DevOps 2.6 Toolkit: Jenkins X" and the result is not as described in the book.

Steps to reproduce the behavior

I followed these instructions

Expected behavior

There is both a snapshot and release available.

Actual behavior

go-demo-6 % jx get applications                                                (master)go-demo-6
APPLICATION STAGING PODS URL
go-demo-6   1.0.479 1/1  http://go-demo-6.jx-staging.35.190.145.60.nip.io

The book states: "We can see that the go-demo-6 application is available as a SNAPSHOT as well as a specific release in the STAGING environment (e.g., 0.0.159 ). SNAPSHOT is the release running in our personal development environment (DevPod)."

There is only the release showing up but not the snapshot.

Jx version

brew info jx                                                   (master)code-examples
jenkins-x/jx/jx: stable 2.0.1236
A tool to install and interact with Jenkins X on your Kubernetes cluster.
https://jenkins-x.io/
/usr/local/Cellar/jx/2.0.1150 (8 files, 218.2MB) *
  Built from source on 2020-01-24 at 09:41:25
From: https://github.com/jenkins-x/homebrew-jx/blob/master/Formula/jx.rb
==> Caveats
Bash completion has been installed to:
  /usr/local/etc/bash_completion.d

zsh completions have been installed to:
  /usr/local/share/zsh/site-functions

Jenkins type

Kubernetes cluster

GCP

Operating system / Environment

MacOS

deanesmith commented 4 years ago

@vfarcic Do you have any background on this?

vfarcic commented 4 years ago

jx get applications did show snapshots in the past. Now I'm not sure whether that was intentionally removed (without a deprecation notice) or it is a bug caused by some other changes.

dmaljovec commented 4 years ago

@vfarcic I have been going through your book and have to start by saying thank you. It is a great resource for our team as we try to get a handle on JenkinsX and how we can use it at our company.

I also ran into this issue. I don't know if it is related, but as I was walking through the steps, I did note something else anomalous, and I don't know if it is related? One thing that was suspicious earlier on was I did not see the exposecontroller-service-... running in my devpod when I was asked to run kubectl -n $SKAFFOLD_DEPLOY_NAMESPACE get pods inside the devpod at around line 91 in the associated gist. Mine looks more like:

NAME                                  READY   STATUS    RESTARTS   AGE
go-demo-6-go-demo-6-...               1/1     Running   0          12h
go-demo-6-go-demo-6-db-arbiter-0      1/1     Running   0          12h
go-demo-6-go-demo-6-db-primary-0      1/1     Running   0          12h
go-demo-6-go-demo-6-db-secondary-0    1/1     Running   0          12h

Maybe this is related, maybe this is a red herring? 🤷‍♂

Thanks again for such a thorough and well thought out resource!

vfarcic commented 4 years ago

@dmaljovec I updated the book soon after this issue was created. If you have eBook from LeanPub or Amazon, you should be able to download the updated version. Please send me a private message to Twitter (@vfarcic), LinkedIn, or anywhere else, and I'll send you a free coupon from LeanPub so that you can have the latest update.

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

jenkins-x-bot commented 4 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Provide feedback via https://jenkins-x.io/community. /close

jenkins-x-bot commented 4 years ago

@jenkins-x-bot: Closing this issue.

In response to [this](https://github.com/jenkins-x/jx/issues/6981#issuecomment-687798515): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. >Provide feedback via https://jenkins-x.io/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [jenkins-x/lighthouse](https://github.com/jenkins-x/lighthouse/issues/new?title=Command%20issue:) repository.