{"action":"created","issue":{"url":"https://api.github.com/repos/gocd/gocd/issues/1924","repository_url":"https://api.github.com/repos/gocd/gocd","labels_url":"https://api.github.com/repos/gocd/gocd/issues/1924/labels{/name}","comments_url":"https://api.github.com/repos/gocd/gocd/issues/1924/comments","events_url":"https://api.github.com/repos/gocd/gocd/issues/1924/events","html_url":"https://github.com/gocd/gocd/issues/1924","id":132994566,"number":1924,"title":"Weak Fan-In Issues","user":{"login":"FredrikWendt","id":89504,"avatar_url":"https://avatars.githubusercontent.com/u/89504?v=3","gravatar_id":"","url":"https://api.github.com/users/FredrikWendt","html_url":"https://github.com/FredrikWendt","followers_url":"https://api.github.com/users/FredrikWendt/followers","following_url":"https://api.github.com/users/FredrikWendt/following{/other_user}","gists_url":"https://api.github.com/users/FredrikWendt/gists{/gist_id}","starred_url":"https://api.github.com/users/FredrikWendt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/FredrikWendt/subscriptions","organizations_url":"https://api.github.com/users/FredrikWendt/orgs","repos_url":"https://api.github.com/users/FredrikWendt/repos","events_url":"https://api.github.com/users/FredrikWendt/events{/privacy}","received_events_url":"https://api.github.com/users/FredrikWendt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"maheshp","id":1061051,"avatar_url":"https://avatars.githubusercontent.com/u/1061051?v=3","gravatar_id":"","url":"https://api.github.com/users/maheshp","html_url":"https://github.com/maheshp","followers_url":"https://api.github.com/users/maheshp/followers","following_url":"https://api.github.com/users/maheshp/following{/other_user}","gists_url":"https://api.github.com/users/maheshp/gists{/gist_id}","starred_url":"https://api.github.com/users/maheshp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maheshp/subscriptions","organizations_url":"https://api.github.com/users/maheshp/orgs","repos_url":"https://api.github.com/users/maheshp/repos","events_url":"https://api.github.com/users/maheshp/events{/privacy}","received_events_url":"https://api.github.com/users/maheshp/received_events","type":"User","site_admin":false},"milestone":null,"comments":8,"created_at":"2016-02-11T14:58:01Z","updated_at":"2016-03-09T18:18:28Z","closed_at":null,"body":"GoCD has great support for proper fan-out and fan-in - it's a unique selling point compared to other build automation tools. The Value Stream Map is a second one.\r\n\r\nBoth these features become flawed with manually triggered pipeline runs.\r\n\r\nThe actual scheduling of work, when caused by manually triggering a pipeline, will not honor the fan-in principles/framework built into the product. It will instead violate all such rules and pick whatever is latest from the configured materials.\r\nThere's no way to manually trigger scheduling of a pipeline which will respect the fan-in feature.\r\n\r\nThe Value Stream Map is limited to showing only one changeset from a source repo, although an UpstreamPipeline might've run with changeset r1, and a DownstramPipeline run with changeset r2. When the ValueStreamMap displays with focus set to the DownstreamPipeline run, instead of showing that UpstreamPipline pointing to r1 and DownstreamPipeline to r2, both runs point to r2 (which is incorrect for UpstreamPipeline).\r\nThe Value Stream Map feature also doesn't differentiate, visually, between pipeline runs which were scheduled honoring the fan-in rules, from those which were run with arbitrarily picked material (ie ignore fan-in).\r\n\r\nCombined, this makes the two biggest selling points for GoCD voided."},"comment":{"url":"https://api.github.com/repos/gocd/gocd/issues/comments/194434126","html_url":"https://github.com/gocd/gocd/issues/1924#issuecomment-194434126","issue_url":"https://api.github.com/repos/gocd/gocd/issues/1924","id":194434126,"user":{"login":"wpc","id":10283,"avatar_url":"https://avatars.githubusercontent.com/u/10283?v=3","gravatar_id":"","url":"https://api.github.com/users/wpc","html_url":"https://github.com/wpc","followers_url":"https://api.github.com/users/wpc/followers","following_url":"https://api.github.com/users/wpc/following{/other_user}","gists_url":"https://api.github.com/users/wpc/gists{/gist_id}","starred_url":"https://api.github.com/users/wpc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wpc/subscriptions","organizations_url":"https://api.github.com/users/wpc/orgs","repos_url":"https://api.github.com/users/wpc/repos","events_url":"https://api.github.com/users/wpc/events{/privacy}","received_events_url":"https://api.github.com/users/wpc/received_events","type":"User","site_admin":false},"created_at":"2016-03-09T18:18:28Z","updated_at":"2016-03-09T18:18:28Z","body":"@arvindsv, @maheshp, @jyotisingh:\r\n\r\nIt is actually very dangerous when the downstream pipeline is deployment pipeline.  It happened multiple times in my previous team: devs try to manual trigger deploy pipeline to recover from production environment issues, but it pull in wrong scripts or artifacts.\r\n\r\nIf warning is on VMS,  I am worried damages may already made before user see it. \r\n\r\n-- wpc\r\n"}}