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

add command: get run #49

Closed
jstrachan opened this issue Jan 12, 2018 · 5 comments
Closed

add command: get run #49

jstrachan opened this issue Jan 12, 2018 · 5 comments
Labels
area/build kind/enhancement An enhancement of an existing feature lifecycle/rotten

Comments

@jstrachan
Copy link
Member

to be able to list all the current pipeline runs in the jenkins server.

So kinda like the jx get pipeline command but listing the jobs in the current jenkins server.

Might be nice to list different things like:

  • list runs for a given pipeline name
  • list active pipeline runs
  • list last / failed runs?
@jstrachan jstrachan added this to the 1 milestone Jan 12, 2018
@jstrachan jstrachan modified the milestones: 1, 4 Feb 27, 2018
@jtnord jtnord added the kind/enhancement An enhancement of an existing feature label Nov 27, 2018
@jtnord
Copy link

jtnord commented Nov 27, 2018

@jstrachan is this not implemented now as jx get build logs (with the exception of getting the last failed/active runs)?

@jenkins-x-bot
Copy link
Contributor

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

@deanesmith deanesmith removed this from the 4 milestone Jun 18, 2019
@jenkins-x-bot
Copy link
Contributor

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
Contributor

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
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 kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build kind/enhancement An enhancement of an existing feature lifecycle/rotten
Projects
None yet
Development

No branches or pull requests

6 participants