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
Show versions of inputs that would be used if a manual job would be triggered *now* #269
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
Related: #413 (comment) - need to think about UI/UX here and how it relates to the first to points in the linked comment. /cc @kimeberz |
Hey there! We're automatically closing this issue since the original poster (or another commenter) hasn't been active in the past six months. We therefore assume that this issue has been lost or resolved on its own. Close issues that remain inactive for a long period may get automatically locked. Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue. |
Reopening this as it still comes up pretty frequently. I think it makes sense to tackle at some point, or at least track the need for it. |
Would love this! :-) |
Beep boop! This issue has been idle for long enough that it's time to check If it is, what is blocking it? Would anyone be interested in submitting a If no activity is observed within the next week, this issue will be |
Beep boop! This issue is still interesting to me and apparently "came up pretty frequently" in the past. I'm not sure if that's the perfect candidate for auto-closing, but given the fact that nothing happened for more than 3 years, it might be okay. |
@voelzmo I'll just re-open and mark it 'help wanted' so it stays around. I think this is one of those things that everyone agrees is a good idea, but there's not much to say about it, and it's kind of low-impact so our priorities have been elsewhere. |
The
promote
job in our pipeline is triggered manually. As the fan-in of inputs and theirpassed
requirements is non-trivial, I'd like concourse to help me with the work I'm currently doing in my head. Which is: figure out which versions of the inputs I would get if I hit the+
button now.So, ideally, somehow I would get a list of inputs as it is currently shown for running jobs as in this screenshot, for example
The text was updated successfully, but these errors were encountered: