Possible problem with environment section in yml?

Rich's Avatar

Rich

27 Apr, 2022 08:16 PM

Hi,
I have a build that was working and just failed on a pull request. The problem seems to be that environment variables are not beiing set.
Here is the successful one
https://ci.appveyor.com/project/bellrichm/weewx-mqttsubscribe-master/builds/43103298/job/2utg4r6l1fp73aeo
And the failure
https://ci.appveyor.com/project/bellrichm/weewx-mqttsubscribe-master/build/job/wt9s71y26r4efc15
Here is the yml
https://github.com/bellrichm/WeeWX-MQTTSubscribe/blob/master/appveyor.master.yml
I have not fully dug into it, but I think the SKEY and COVERALLS_REPO_TOKEN are not set. I was just wondering if I missed a change that caused this change in behavior.
Thanks. rich

  1. Support Staff 1 Posted by Feodor Fitsner on 27 Apr, 2022 11:30 PM

    Feodor Fitsner's Avatar

    Yes, public projects do not set secure variables in PR builds - for security reasons. The only option to enable them is "Enable secure variables in Pull Requests from the same repository only" on General tab of project settings. It's still impossible to allow them for PRs sent from forks.

  2. 2 Posted by Rich on 28 Apr, 2022 01:02 AM

    Rich's Avatar

    Thanks. That sounds familiar and makes perfect sense.
    Sorry to have troubled you. rich

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac