On 29.05.2014, at 18:51, Kevin Burke <[email protected]> wrote: > - The most common actions were not easily available. Specifically, 1) from a > job's homepage, I wanted to view the console output of the latest build, and > 2) I wanted to be able to trigger new builds from any page on a job.
This is easy to add in a plugin. Not saying this is a bad idea, but as users have different needs, this is probably best left to customization IMO; especially as it is much easier added than removed! Right now, you just need to open a -- admittedly difficult to open -- context menu (build list entry and breadcrumb, respectively) to do either, so it's not like it requires navigating away. > - Some things don't have API's. For example, creating a new build doesn't > return the build number, so you need to GET the job list to get the current > build number and just hope the build you created will be the next one. See > for example https://github.com/kevinburke/doony/blob/master/src/theme.js#L274. Well, at that time, there's no build number assigned yet, so it cannot be returned (it does return the queue item that will eventually tell you the resulting build). I elaborated on this in a comment in Jira, with API usage instructions: https://issues.jenkins-ci.org/browse/JENKINS-12827?focusedCommentId=201381&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-201381 > Similarly, there's no API for retrieving the console output. /job/foo/42/consoleText returns the full log output (unless the build still runs, when it only returns the first 10k lines IIRC). .../progressiveText returns an arbitrary chunk specified by the ?start=<offset> parameter. It sets headers with length printed and whether there's more. Can't you use these? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
