I found out why the file didn't exist. It was never created due to a bug. But why did the server logs not complain, but rather suggest that all was as intended?
Den fredag 27 oktober 2017 kl. 11:02:18 UTC+2 skrev Magnus Lyckå: > > In the web UI I get the following message when I click on a link in an > HTML artifact embedded as a tab. > > Artifact 'report/report/gocd.dot.svg' is unavailable as it may have been > purged by Go or deleted externally. > > > This worked a few days ago... > > > With `tail -f go-server.log | grep svg` I get: > > > at 2017-10-27 10:50:53,451 INFO [qtp2081303229-13461323] > ArtifactsController:270 - [Artifact Download] Trying to resolve > 'report/report/gocd.dot.svg' for 'GoCD_Dependency_Report/40/defa > > ultStage/1/defaultJob' > 2017-10-27 10:50:53,464 INFO [qtp2081303229-13461323] > ArtifactsController:288 - [Artifact Download] Successfully resolved > 'report/report/gocd.dot.svg' for 'GoCD_Dependency_Report/40/ > defaultStage/1/defaultJob'. It took: 7ms > > So, successfully resolved, but not successfully delivered to the web > frontend? :-( > > > -- You received this message because you are subscribed to the Google Groups "go-cd" 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.
