Skip to content

Conversation

tylerjereddy
Copy link
Collaborator

  • attempt to encrypt the OPENBLAS_LIBS_STAGING_UPLOAD_TOKEN
    as a project "collaborator" & then open PR from a feature
    branch within the repo proper, to see if this allows
    accessing the secure token in Appveyor

@tylerjereddy
Copy link
Collaborator Author

PRs now seem to be using the most recent appveyor webhook, which points to my own newly-created appveyor instance/project for openblas-libs. Since I also encrypted the variable when logged in as the same user this should work, but let's see in a few hours...

* OPENBLAS_LIBS_STAGING_UPLOAD_TOKEN is now encrypted
directly in the appveyor UI at:
https://ci.appveyor.com/project/tylerjereddy/openblas-libs/settings/environment

* this approach is used instead of pasting an
encrypted env variable directly in the yml
file, which seems to have stricter requirements
in terms of ownership of the associated
GitHub project
@tylerjereddy tylerjereddy force-pushed the treddy_appveyor_token_test branch from 173a6c0 to 7fc3350 Compare February 24, 2020 01:33
@tylerjereddy
Copy link
Collaborator Author

Updated to use OPENBLAS_LIBS_STAGING_UPLOAD_TOKEN encryption directly in the Appveyor settings UI instead of encrypting + pasting in the yml file directly. From what I can find online, this should work with "collaborator" permissions, but only the CI result will tell...

@tylerjereddy tylerjereddy changed the title DEBUG: collab token update WIP, MAINT: encrypt upload token directly in Appveyor UI Feb 24, 2020
@tylerjereddy
Copy link
Collaborator Author

Close/reopen after removing the webhook to Matthew's appveyor account, which was still taking precedence.

@tylerjereddy
Copy link
Collaborator Author

The "pr" appveyor run is pointing to my appveyor accout, so that should upload. The "branch" run still points to Matthew's for whatever reason.

@tylerjereddy tylerjereddy changed the title WIP, MAINT: encrypt upload token directly in Appveyor UI MAINT: encrypt upload token directly in Appveyor UI Feb 24, 2020
@tylerjereddy
Copy link
Collaborator Author

All 14 release artifacts are visible at: https://anaconda.org/multibuild-wheels-staging/openblas-libs/files

The Appveyor "pr" entry seems to behave as intended. The "branch" entry may be leftover from the old appveyor commit hook. Anyway, PRs from branches within the repo are likely to be the minority.

The Travis CI "pr" entry also looks good. The Travis "push" entry can likely be ignored---I've not adjusted Travis here anyway.

@tylerjereddy tylerjereddy merged commit af2d53d into master Feb 24, 2020
@tylerjereddy tylerjereddy deleted the treddy_appveyor_token_test branch February 24, 2020 16:54
@ogrisel
Copy link
Contributor

ogrisel commented Feb 25, 2020

The github status display is still misleading because @matthew-brett's appveyor account is still active and probably overriding the MacPython/openblas-libs results.

For instance:

https://ci.appveyor.com/project/matthew-brett/openblas-libs/builds/31004859/job/gjlhcu2bb4gy0x0c

that does not have access to the secret variable, has overridden:

https://ci.appveyor.com/project/tylerjereddy/openblas-libs/builds/31004854/job/8iw5pusdtod3k0h4

which was successful.

@matthew-brett could you please delete the https://ci.appveyor.com/project/matthew-brett/openblas-libs account now that @tylerjereddy's account works as expected?

@matthew-brett
Copy link
Contributor

matthew-brett commented Feb 26, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants