Project

General

Profile

Bug #16027

Jenkins web interface has broken artifact links

Added by anonym 12 months ago. Updated 1 day ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Continuous Integration
Target version:
-
Start date:
10/03/2018
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

See e.g.: https://jenkins.tails.boum.org/job/build_Tails_ISO_stable/2338/

The latest.iso.shasum link is broken; one has to expand build-artifacts to then find tails-build-artifacts.shasum which works. Ideally we'd only get the build-artifacts, where the real files are, with informative filenames and all.

I wasted quite a lot of time trying to find the SHAAAA (it's required by the release process) first ending up with #16026, then realizing I had access to the Jenkins machine where I found the ISO. Only later did I see the expander...


Related issues

Related to Tails - Bug #16959: Gather usability data about our current CI Confirmed

History

#1 Updated by intrigeri 11 months ago

  • Assignee deleted (intrigeri)

#2 Updated by intrigeri 11 months ago

Thanks for your report. I think it's very valuable to collect the list of known issues / pain points with our current setup ⇒ we'll be in a better position to integrate improvements into our roadmap/budget :)

#3 Updated by intrigeri 14 days ago

  • Related to Bug #16959: Gather usability data about our current CI added

#4 Updated by intrigeri 1 day ago

  • Status changed from Confirmed to Resolved

This was incidentally fixed by https://git.tails.boum.org/puppet-tails/commit/files/jenkins/master/clean_old_jenkins_artifacts?id=057b1f97882e6b595f3b39c9adf6ccc59cf8ed4a: we don't create latest.iso.shasum links anymore.

The other latest.* links seem to work just fine so I'm closing this ticket. Please reopen if something is still broken :)

Also available in: Atom PDF