{"action":"created","issue":{"url":"https://api.github.com/repos/concourse/concourse/issues/1686","repository_url":"https://api.github.com/repos/concourse/concourse","labels_url":"https://api.github.com/repos/concourse/concourse/issues/1686/labels{/name}","comments_url":"https://api.github.com/repos/concourse/concourse/issues/1686/comments","events_url":"https://api.github.com/repos/concourse/concourse/issues/1686/events","html_url":"https://github.com/concourse/concourse/issues/1686","id":262052938,"number":1686,"title":"Add a flag to turn off the new \"hidden jobs\" check","user":{"login":"dumbbell","id":159804,"avatar_url":"https://avatars2.githubusercontent.com/u/159804?v=4","gravatar_id":"","url":"https://api.github.com/users/dumbbell","html_url":"https://github.com/dumbbell","followers_url":"https://api.github.com/users/dumbbell/followers","following_url":"https://api.github.com/users/dumbbell/following{/other_user}","gists_url":"https://api.github.com/users/dumbbell/gists{/gist_id}","starred_url":"https://api.github.com/users/dumbbell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dumbbell/subscriptions","organizations_url":"https://api.github.com/users/dumbbell/orgs","repos_url":"https://api.github.com/users/dumbbell/repos","events_url":"https://api.github.com/users/dumbbell/events{/privacy}","received_events_url":"https://api.github.com/users/dumbbell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-02T11:17:24Z","updated_at":"2017-10-02T13:21:10Z","closed_at":null,"author_association":"NONE","body":"## What challenge are you facing?\r\n\r\nWith Concourse 3.5.0, hidden jobs (i.e. not part of any groups) are considered an error (#1150).\r\n\r\nWe have many parallel jobs with several resources flowing from and to all of them, thus a single resource is displayed multiple times in the UI, with as many lines as needed to connect jobs. We use hidden jobs on purpose to remove load on the UI: those hidden jobs \"gather\" resources/lines so we go back to a single \"copy\" of a resource when we move to the next group.\r\n\r\nHere is an example:\r\n![screenshot-2017-10-2 server-release v3 7 x - concourse](https://user-images.githubusercontent.com/159804/31074681-20ae879c-a772-11e7-9b50-596ebfc94c62.png)\r\n\r\nAt the end of this group, we have a hidden job which does nothing but deduplicates lines. As you see, the UI is already unreadable. Adding the hidden job to the group doubles the height of the graph.\r\n\r\n## A Modest Proposal\r\n\r\nThe real root problem is the UI which is not designed for pipelines with many jobs and resources. But this is not a quick and easy task.\r\n\r\nI would love a way to turn off the new check for hidden jobs. I know we could have a useless group for all hidden jobs, but this would be another workaround on top of a workaround.\r\n\r\n* Concourse version: 3.4.1\r\n* Deployment type (BOSH/Docker/binary): BOSH\r\n* Infrastructure/IaaS: AWS"},"comment":{"url":"https://api.github.com/repos/concourse/concourse/issues/comments/333532246","html_url":"https://github.com/concourse/concourse/issues/1686#issuecomment-333532246","issue_url":"https://api.github.com/repos/concourse/concourse/issues/1686","id":333532246,"user":{"login":"jama-pivotal","id":19274230,"avatar_url":"https://avatars3.githubusercontent.com/u/19274230?v=4","gravatar_id":"","url":"https://api.github.com/users/jama-pivotal","html_url":"https://github.com/jama-pivotal","followers_url":"https://api.github.com/users/jama-pivotal/followers","following_url":"https://api.github.com/users/jama-pivotal/following{/other_user}","gists_url":"https://api.github.com/users/jama-pivotal/gists{/gist_id}","starred_url":"https://api.github.com/users/jama-pivotal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jama-pivotal/subscriptions","organizations_url":"https://api.github.com/users/jama-pivotal/orgs","repos_url":"https://api.github.com/users/jama-pivotal/repos","events_url":"https://api.github.com/users/jama-pivotal/events{/privacy}","received_events_url":"https://api.github.com/users/jama-pivotal/received_events","type":"User","site_admin":false},"created_at":"2017-10-02T13:21:10Z","updated_at":"2017-10-02T13:21:10Z","author_association":"CONTRIBUTOR","body":"Ah, that's an interesting (and unforseen) use case! We might want to dial down the check to make it less aggressive so it prompts for a Y/N if you want to proceed with setting a hidden, instead of just straight blocking you"}}
{"actor":{"display_login":"jama-pivotal"}}