{"action":"created","issue":{"url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin/issues/19","repository_url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin","labels_url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin/issues/19/comments","events_url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin/issues/19/events","html_url":"https://github.com/mibexsoftware/bamboo-plan-dsl-plugin/issues/19","id":206752109,"number":19,"title":"Feature request: improve logging","user":{"login":"hsmade","id":1136373,"avatar_url":"https://avatars.githubusercontent.com/u/1136373?v=3","gravatar_id":"","url":"https://api.github.com/users/hsmade","html_url":"https://github.com/hsmade","followers_url":"https://api.github.com/users/hsmade/followers","following_url":"https://api.github.com/users/hsmade/following{/other_user}","gists_url":"https://api.github.com/users/hsmade/gists{/gist_id}","starred_url":"https://api.github.com/users/hsmade/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hsmade/subscriptions","organizations_url":"https://api.github.com/users/hsmade/orgs","repos_url":"https://api.github.com/users/hsmade/repos","events_url":"https://api.github.com/users/hsmade/events{/privacy}","received_events_url":"https://api.github.com/users/hsmade/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-02-10T09:52:56Z","updated_at":"2017-02-20T15:57:45Z","closed_at":"2017-02-17T15:17:01Z","body":"Whenever I get an error when running the seed task, I just get a stack trace with almost no hint on what groovy script line actually caused it. Now I see 2 ways to improve this:\r\n1) (have a way to enable) extensive logging on what part of the script is processed, so we can follow the flow and see where the stack trace was caused\r\n\r\nor\r\n\r\n2) Have a way to log the line number or snippet with the stack trace.\r\n\r\nI don't know what possibilities you have in the code / in groovy handling, but it would surely help a lot. Even when I always use the DSL schemes for validation of what I throw at the plugin, I regularly get stack traces and need to strip down my config in order to find what caused the stack trace.  "},"comment":{"url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin/issues/comments/281115653","html_url":"https://github.com/mibexsoftware/bamboo-plan-dsl-plugin/issues/19#issuecomment-281115653","issue_url":"https://api.github.com/repos/mibexsoftware/bamboo-plan-dsl-plugin/issues/19","id":281115653,"user":{"login":"mrueegg","id":206944,"avatar_url":"https://avatars.githubusercontent.com/u/206944?v=3","gravatar_id":"","url":"https://api.github.com/users/mrueegg","html_url":"https://github.com/mrueegg","followers_url":"https://api.github.com/users/mrueegg/followers","following_url":"https://api.github.com/users/mrueegg/following{/other_user}","gists_url":"https://api.github.com/users/mrueegg/gists{/gist_id}","starred_url":"https://api.github.com/users/mrueegg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrueegg/subscriptions","organizations_url":"https://api.github.com/users/mrueegg/orgs","repos_url":"https://api.github.com/users/mrueegg/repos","events_url":"https://api.github.com/users/mrueegg/events{/privacy}","received_events_url":"https://api.github.com/users/mrueegg/received_events","type":"User","site_admin":false},"created_at":"2017-02-20T15:57:45Z","updated_at":"2017-02-20T15:57:45Z","body":"The name is not yet available. But I will try to improve the error message for the next release.\r\n\r\nIf it's a non-shared artifact, have you tried to use an artifact in a job from a job in a different stage I guess?"}}
{"actor":{"display_login":"mrueegg"}}