[ 
https://issues.jenkins-ci.org/browse/JENKINS-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161587#comment-161587
 ] 

Devin Linnington commented on JENKINS-13447:
--------------------------------------------

The work around for this is to use the PROMOTED_* variables to figure out where 
the main jobs archive is, then move whatever files there:

{code:java}
archive_dir="${jenkins_dir}/${PROMOTED_JOB_NAME}/builds/${PROMOTED_NUMBER}/archive/"
if [ -d "$archive_dir" ]; then
        mv test_results $archive_dir
else
        echo "#### Error: archive directory does not exist"
fi
{code}

This is actually better for my users than the original idea, so feel free to 
close this if you wish.

-Devin
                
> Show link to promotion jobs archived artifacts
> ----------------------------------------------
>
>                 Key: JENKINS-13447
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13447
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: promoted-builds
>    Affects Versions: current
>            Reporter: Devin Linnington
>            Assignee: Peter Hayes
>              Labels: archive, artifact
>         Attachments: promote_builds.png
>
>
> I have a script that copies some QA test results (simple txt files) to the 
> local workspace, and then I have a build action that archives these txt files.
> !promote_builds.png|width=900!
> The only way I can view these archived artifacts is to manually enter 
> 'artifact/' on the end of the promoted job url, like so:
> http://jenkins/view/job_view/job/job_name/77/promotion/QA%20Fail/promotionBuild/1/artifact/test_results/
> Right now the default page is just the console log, would it be possible to 
> add multiple job-related links the left-hand side, similar to the parent job 
> that was promoted? This would make it a heck of a lot easier to find the 
> artifacts for each promoted build.

--
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

        

Reply via email to