Hi Holger, Quoting Holger Levsen (2015-01-03 16:19:59) > So now https://jenkins.debian.net/view/d- > i_misc/job/dpkg_sid_find_trigger_cycles/19/console has this issue: > > curl: (5) Could not resolve proxy: $http_proxy > > I'll look into this now...
this seems to be solved! Thanks \o/ The remaining problem seems to be how to get the build artifacts out of the schroot. On IRC you said "cp $file /srv/workspace/$path". I still don't know jenkins well, so what shall the "$path" part be, here? Shall I: $ mkdir -p /srv/workspace/dpkg_sid_find_trigger_cycles $ cp result-file result-explicit /srv/workspace/dpkg_sid_find_trigger_cycles Or shall it just be: $ cp result-file result-explicit /srv/workspace/ And is it better to create a build artifact like that or would it be better to just cat(1) the files in the script so that their content can be looked at in the log? Thanks! cheers, josch -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150104033138.15300.70084@hoothoot
