{"action":"created","issue":{"url":"https://api.github.com/repos/svanoort/pyresttest/issues/43","labels_url":"https://api.github.com/repos/svanoort/pyresttest/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/svanoort/pyresttest/issues/43/comments","events_url":"https://api.github.com/repos/svanoort/pyresttest/issues/43/events","html_url":"https://github.com/svanoort/pyresttest/issues/43","id":75177837,"number":43,"title":"Jenkins / pytest integration","user":{"login":"nirsegev","id":7397011,"avatar_url":"https://avatars.githubusercontent.com/u/7397011?v=3","gravatar_id":"","url":"https://api.github.com/users/nirsegev","html_url":"https://github.com/nirsegev","followers_url":"https://api.github.com/users/nirsegev/followers","following_url":"https://api.github.com/users/nirsegev/following{/other_user}","gists_url":"https://api.github.com/users/nirsegev/gists{/gist_id}","starred_url":"https://api.github.com/users/nirsegev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nirsegev/subscriptions","organizations_url":"https://api.github.com/users/nirsegev/orgs","repos_url":"https://api.github.com/users/nirsegev/repos","events_url":"https://api.github.com/users/nirsegev/events{/privacy}","received_events_url":"https://api.github.com/users/nirsegev/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/svanoort/pyresttest/labels/enhancement","name":"enhancement","color":"009800"},{"url":"https://api.github.com/repos/svanoort/pyresttest/labels/needs%20more%20information","name":"needs more information","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-05-11T10:45:58Z","updated_at":"2015-05-12T11:25:41Z","closed_at":null,"body":"Hi, \r\nI would like to use pyresttest in our CI. is there currently a suuport for xml test results generation?\r\nThanks"},"comment":{"url":"https://api.github.com/repos/svanoort/pyresttest/issues/comments/101244991","html_url":"https://github.com/svanoort/pyresttest/issues/43#issuecomment-101244991","issue_url":"https://api.github.com/repos/svanoort/pyresttest/issues/43","id":101244991,"user":{"login":"svanoort","id":5400948,"avatar_url":"https://avatars.githubusercontent.com/u/5400948?v=3","gravatar_id":"","url":"https://api.github.com/users/svanoort","html_url":"https://github.com/svanoort","followers_url":"https://api.github.com/users/svanoort/followers","following_url":"https://api.github.com/users/svanoort/following{/other_user}","gists_url":"https://api.github.com/users/svanoort/gists{/gist_id}","starred_url":"https://api.github.com/users/svanoort/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/svanoort/subscriptions","organizations_url":"https://api.github.com/users/svanoort/orgs","repos_url":"https://api.github.com/users/svanoort/repos","events_url":"https://api.github.com/users/svanoort/events{/privacy}","received_events_url":"https://api.github.com/users/svanoort/received_events","type":"User","site_admin":false},"created_at":"2015-05-12T11:25:41Z","updated_at":"2015-05-12T11:25:41Z","body":"@mariusmagureanu Yes, that is a good idea and along the lines I was thinking -- one notion is to use a listener API that is invoked at each step of the test execution/benchmark pipline.  This is somewhat linked to a longer-term goal of refactoring test/benchmark components into a set of composable, pluggable steps.\r\n\r\nI'm also toying the idea of offering some sort of Jenkins plugin for integration in the future -- due to job changes, I expect to have a great deal of experience with this in the near future. "}}