Do we have any options for storage/access of the output of CI runs other than the Jenkins UI?
It'd be nice to enable some sort of semi-permanent static links for stuff like html-formatted output that some tools offer. I'm not sure jenkins allows that without publishing to en external host but if I'm mistaken here, pointers to links would be appreciated.
Tim
On Thu, 18 Jul 2019 11:29:56 -0600 Tim Flink tflink@redhat.com wrote:
Do we have any options for storage/access of the output of CI runs other than the Jenkins UI?
It'd be nice to enable some sort of semi-permanent static links for stuff like html-formatted output that some tools offer. I'm not sure jenkins allows that without publishing to en external host but if I'm mistaken here, pointers to links would be appreciated.
Of course I stumble upon a plugin which enables HTML hosting almost as soon as I sent this.
https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin
That being said, I'd rather not add dependencies to yet another plugin if there's a way to work around it. From the changelog, it looks like there have been changes in how the links work to address security issues in the past and the plugin itself requires changes to Jenkins' security policy.
Tim
Hello,
In the systemd project I make use of the "Archive the artifacts" post-build action, which results in a semi-permanent link to the artifacts themselves. So, after each run, I generate an HTML page using the tree(1) utility, which is then accessible from the artifacts page as a standalone HTML page[0].
Other possible solution could be copying the artifacts over to the storage box[1], which is accessible over HTTP from the outside.
Frantisek
[0] https://ci.centos.org/view/systemd/job/systemd-pr-build/lastSuccessfulBuild/... [1] https://wiki.centos.org/QaWiki/CI/GettingStarted#head-a46ee49e8818ef9b50225c...
On 7/18/19 7:29 PM, Tim Flink wrote:
Do we have any options for storage/access of the output of CI runs other than the Jenkins UI?
It'd be nice to enable some sort of semi-permanent static links for stuff like html-formatted output that some tools offer. I'm not sure jenkins allows that without publishing to en external host but if I'm mistaken here, pointers to links would be appreciated.
Tim
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
And a small correction - I somehow thought the original mail came from the CentOS CI mailing list, thus the second solution is kind of useless. However, the first one should be usable with other Jenkins instances as well.
Sorry for the noise!
Frantisek
On 7/19/19 4:54 PM, František Šumšal wrote:
Hello,
In the systemd project I make use of the "Archive the artifacts" post-build action, which results in a semi-permanent link to the artifacts themselves. So, after each run, I generate an HTML page using the tree(1) utility, which is then accessible from the artifacts page as a standalone HTML page[0].
Other possible solution could be copying the artifacts over to the storage box[1], which is accessible over HTTP from the outside.
Frantisek
[0] https://ci.centos.org/view/systemd/job/systemd-pr-build/lastSuccessfulBuild/... [1] https://wiki.centos.org/QaWiki/CI/GettingStarted#head-a46ee49e8818ef9b50225c...
On 7/18/19 7:29 PM, Tim Flink wrote:
Do we have any options for storage/access of the output of CI runs other than the Jenkins UI?
It'd be nice to enable some sort of semi-permanent static links for stuff like html-formatted output that some tools offer. I'm not sure jenkins allows that without publishing to en external host but if I'm mistaken here, pointers to links would be appreciated.
Tim
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
ci@lists.stg.fedoraproject.org
-
František Šumšal -
Tim Flink