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

Show versions of inputs that would be used if a manual job would be triggered *now* #269

Open
voelzmo opened this issue Feb 3, 2016 · 9 comments

Comments

@voelzmo
Copy link

voelzmo commented Feb 3, 2016

The promote job in our pipeline is triggered manually. As the fan-in of inputs and their passed 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
screen shot 2016-02-03 at 18 19 27

@concourse-bot
Copy link
Collaborator

concourse-bot commented Feb 3, 2016

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:

  • #113003021 Show versions of inputs that would be used if a manual job would be triggered now

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

@vito vito changed the title [Feature Request] Show versions of inputs that would be used if a manual job would be triggered *now* Show versions of inputs that would be used if a manual job would be triggered *now* Jul 15, 2016
@vito
Copy link
Member

vito commented Jul 15, 2016

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

@jama22
Copy link
Member

jama22 commented Jul 25, 2017

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.
Thanks!

@jama22 jama22 closed this as completed Jul 25, 2017
@cah-andrew-fitzgerald
Copy link

Got here from #1172 -> #413 -> here.
This use case would still be nice for verifying release builds/other manual steps

@vito vito reopened this Oct 25, 2017
@vito
Copy link
Member

vito commented Oct 25, 2017

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.

@vito vito removed the enhancement label Nov 28, 2017
jwntrs pushed a commit that referenced this issue Apr 26, 2018
Submodule src/github.com/DataDog/datadog-go 00000000...e67964b4 (new submodule)
Submodule src/github.com/concourse/atc 7d909fc..8ca07c1:
  > Merge pull request #269 from baptiste-bonnaudet/master

Signed-off-by: Mark Huang <mhuang@pivotal.io>
@marco-m
Copy link
Contributor

marco-m commented Jan 31, 2019

Would love this! :-)

@stale
Copy link

stale bot commented Jul 16, 2019

Beep boop! This issue has been idle for long enough that it's time to check
in and see if it's still important.

If it is, what is blocking it? Would anyone be interested in submitting a
PR
or
continuing the discussion to help move things forward?

If no activity is observed within the next week, this issue will be
exterminated closed, in accordance with our stale issue
process
.

@stale stale bot added the wontfix label Jul 16, 2019
@stale stale bot closed this as completed Jul 23, 2019
@voelzmo
Copy link
Author

voelzmo commented Jul 23, 2019

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.

@vito
Copy link
Member

vito commented Jul 24, 2019

@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.

@vito vito reopened this Jul 24, 2019
@stale stale bot removed the wontfix label Jul 24, 2019
@vito vito added this to End Goals in Build re-running Aug 6, 2019
@vito vito removed this from End Goals in Build re-running Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants