-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3.32.0 cannot rerender feedstocks with custom Azure project configuration #1864
Comments
I assume this change in behavior was introduced with the new schemas in #1756 |
conda-smithy/conda_smithy/azure_ci_utils.py Lines 270 to 287 in 44acb93
conda-smithy/conda_smithy/schema.py Lines 206 to 212 in 44acb93
Note it can also be added via the conda-smithy/conda_smithy/configure_feedstock.py Lines 2136 to 2137 in 44acb93
|
@jaimergp thanks for your help investigating! Today I tested what I would get if I completed removed Here is an example URL that was properly constructed by conda-smithy 3.31.0 with the following settings: azure:
build_id: 44
user_or_org: TileDB-Inc
project_name: CI https://dev.azure.com/TileDB-Inc/CI/_build/latest?definitionId=44&branchName=main When I comment out the above, then I get the following URL from conda-smithy 3.32.0: https://dev.azure.com/TileDB-Inc/feedstock-builds/_build/latest?definitionId=&branchName=main
The org is correct in this case because we do set it within
The And the biggest problem is the Azure project name. Ours is "CI", not the conda-forge default of "feedstock-builds" |
Yes, we need to amend a couple details here, and we'll do so shortly. I was suggesting possible workarounds in the meantime. Thanks for looking into it! What happens if you only leave |
Confirmed. I tested that I could edit So the to-do's to close this Issue are:
While it would be a nice new behavior to automatically calculate and insert the |
Added #1871 |
Solution to issue cannot be found in the documentation.
Issue
The TileDB-Inc GitHub org maintains independent feedstocks that we run in our own Azure org. In order to properly render the Azure status badges in the README, we add the fields
build_id
,project_name
, anduser_or_org
underneathazure
. This worked perfectly with conda-smithy <3.32.0.Here is an example:
Below is a reprex:
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: