Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

step view to show kubectl exec command #19

Closed
jstrachan opened this issue Jul 31, 2020 · 6 comments
Closed

step view to show kubectl exec command #19

jstrachan opened this issue Jul 31, 2020 · 6 comments
Labels

Comments

@jstrachan
Copy link
Contributor

similar to #18 it would be nice to be able to copy/paste the kubectl command to open a terminal in a step of a pipeline.

e.g. something like...

kubectl exec -it -c $containerName $podName  bash

so folks can quickly open a terminal inside a step's container

@nodece
Copy link
Contributor

nodece commented Aug 8, 2020

I wonder your mean is quick re-run the pipeline?

@jstrachan jstrachan added the good first issue Good for newcomers label Sep 28, 2020
@jstrachan
Copy link
Contributor Author

to be clear, given a step of a pipeline, it would be awesome to disaplay the kubectl command so that you can copy/paste and open a terminal inside the container of the pod of the pipeline so you can diagnose it (assuming its still running)

@jenkins-x-bot
Copy link

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
Copy link

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
Copy link

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-test
Copy link
Contributor

@jenkins-x-bot: Closing this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants