{"action":"opened","issue":{"url":"https://api.github.com/repos/polyswarm/development/issues/7","repository_url":"https://api.github.com/repos/polyswarm/development","labels_url":"https://api.github.com/repos/polyswarm/development/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/polyswarm/development/issues/7/comments","events_url":"https://api.github.com/repos/polyswarm/development/issues/7/events","html_url":"https://github.com/polyswarm/development/issues/7","id":351737192,"node_id":"MDU6SXNzdWUzNTE3MzcxOTI=","number":7,"title":"Design: e2e / CI 2.0","user":{"login":"myhndl","id":5186697,"node_id":"MDQ6VXNlcjUxODY2OTc=","avatar_url":"https://avatars2.githubusercontent.com/u/5186697?v=4","gravatar_id":"","url":"https://api.github.com/users/myhndl","html_url":"https://github.com/myhndl","followers_url":"https://api.github.com/users/myhndl/followers","following_url":"https://api.github.com/users/myhndl/following{/other_user}","gists_url":"https://api.github.com/users/myhndl/gists{/gist_id}","starred_url":"https://api.github.com/users/myhndl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/myhndl/subscriptions","organizations_url":"https://api.github.com/users/myhndl/orgs","repos_url":"https://api.github.com/users/myhndl/repos","events_url":"https://api.github.com/users/myhndl/events{/privacy}","received_events_url":"https://api.github.com/users/myhndl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-17T21:01:23Z","updated_at":"2018-08-17T21:01:23Z","closed_at":null,"author_association":"MEMBER","body":"Current e2e setup leaves a lot to be desired. There are many pain points, including:\r\n1. Branch / tag names matter and cause breakage if they don't conform to a pattern (e2e#5)\r\n1. e2e pipelines spanning multiple projects reduces code duplication in each project, but present quite confusing UX. For example, a change to microengine that causes e2e testing to fail may fail in the e2e pipeline stage. If it does, emails and notifications go out saying e2e failed in addition to microengine failed.\r\n1. The manner in which one stage of the pipeline (e.g. kick-e2e in microengine) relies on another (e.g. e2e in e2e) is hacky at best. It abuses the GitLab API and requires a dedicated GitLab user to even work as is.\r\n1. Terraformed projects should deploy from the CI\r\n\r\n\r\n"}}
{"actor":{"display_login":"myhndl"}}