Investigate garmr Jenkins job

Question

Investigate garmr Jenkins job

Closed this issue 10 years ago · 7 comments

The job appears as unstable and there seems to be a failure. Job link

This is the failure: "No X-Content-Security-Policy or X-Content-Security-Policy-Report-Only in headers" and it seems to be from https___addons-dev.allizom.org

ping @stephendonner

Answer 1 · 2014-05-14T13:24:56.000Z

I am not owning this repo, even though I wrote most of the code :P
I fixed it a few hours ago in my fork: freddyb@270f84a

Answer 2 · 2014-05-14T13:30:42.000Z

@mozfreddyb could you submit a pull request so we can merge this in?

Answer 3 · 2014-05-14T13:55:02.000Z

The commit history seems to be bogus, sorry.
I suggest you take this patch file instead http://dpaste-bkero.paas.allizom.org/PrcX

Answer 4 · 2014-05-14T14:12:34.000Z

@mozfreddyb it looks like a lot of your previous changes were squashed into 86668d9. You could probably rebase your fork to restore your commit history. For now let's see if I can cherry-pick your fix.

Answer 5 · 2014-05-14T14:20:26.000Z

I've opened pull #8 with @mozfreddyb's changes. I don't have access anymore to push directly. Perhaps @stephendonner can grant the automation team access to this repo? Otherwise, please can someone merge this?

Answer 6 · 2014-05-14T14:38:07.000Z

Thanks to @AutomatedTester this is now merged.

Answer 7 · 2014-05-14T14:38:47.000Z

..and the Garmr build in Jenkins is passing again.