[
https://issues.jenkins-ci.org/browse/JENKINS-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mcrooney closed JENKINS-9099.
-----------------------------
Resolution: Won't Fix
I agree this would be cool, though HTML Publisher is a post-build plugin, and
its fundamental architecture is copying reports once post-build, so it isn't as
simple as providing the URL earlier.
If you want to achieve this behavior, you could simply add a build step at the
beginning of your job that symlinks the workspace report dir into
$JENKINS_HOME/userContent, which is web-accessible, and bookmark it, use the
Sidebar Links plugin, or put a link to it in your job's description!
> Early Artifact URLs
> -------------------
>
> Key: JENKINS-9099
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9099
> Project: Jenkins
> Issue Type: New Feature
> Components: htmlpublisher
> Reporter: Paul Hammant
> Assignee: mcrooney
> Priority: Minor
>
> Context: JBehave writes JSON to a target directory as the job runs. In fact
> after each story is executed (story is like a test). When run from the
> command line, one can go into the page to see the JSON after the first of
> many stories has been completed. One can track progress by hitting refresh
> (may be automatic in subsequent versions).
> But in Jenkins the resulting artifacts are not available by URL until after
> the job has finished:
>
> http://myjenkins/job/MyJob/1234/artifact/foo/target/jbehave/view/storynavigator.html
> New Feature Request: It would be nice if the URL was available *during* the
> progressing of the job.
> If you want to see what story navigator looks like, go here:
> http://paul-hammant.github.com/StoryNavigator/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
