Closed jdblischak closed 5 months ago
I assume this change in behavior was introduced with the new schemas in https://github.com/conda-forge/conda-smithy/pull/1756
build_id
is only needed for the README and can be calculated, so maybe you don't need it:
user_or_org
is explicitly excluded from the schema 🤔 Do you remember why this needed to be excluded, @isuruf?
Note it can also be added via the github
key (assuming they are the same).
@jaimergp thanks for your help investigating! Today I tested what I would get if I completed removed build_id
, user_or_org
, and project_name
.
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
Note it can also be added via the
github
key (assuming they are the same).
The org is correct in this case because we do set it within github
, but I don't think it should be required to have the same org name in GitHub and Azure
build_id
is only needed for the README and can be calculated, so maybe you don't need it:
The build_id
may be getting calculated, but it currently is not being inserted into the Azure URLs in the README
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 project_name
in? I don't think that breaks the schema.
What happens if you only leave
project_name
in? I don't think that breaks the schema.
Confirmed. I tested that I could edit project_name
and the new value was inserted into the README Azure URLs.
So the to-do's to close this Issue are:
user_or_org
(turns out this worked; the problem was the description; fixed in #1871)build_id
(added back in #1871)While it would be a nice new behavior to automatically calculate and insert the build_id
into the URLs, my immediate need is to restore the previous behavior. I have many feedstocks that use Azure/build_id
, and if possible I'd prefer to not have to update all of them.
Closed by #1871 Thanks @isuruf!
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