-
Notifications
You must be signed in to change notification settings - Fork 1
PR merging is not triggering feedstock creation in pangeo-forge-orchestrator. #203
Comments
@sharkinsspatial it looks like at least the latter one is registered with the backend and triggering the expected recipe run: https://pangeo-forge.org/dashboard/feedstock/95 |
There does appear to a problem with the first of the two feedstocks you link above: https://github.com/pangeo-forge/noaa-atmosphere-climate-cloud-properties-isccp-hgg-basic-feedstock/deployments/activity_log?environment=noaa-atmosphere-climate-cloud-properties-isccp-hgg-basic I'm not certain what specifically caused this yet. |
@cisaacstern l It appears as if the feedstock was also registered correctly for the above recipe ☝️ https://pangeo-forge.org/dashboard/feedstock/94 |
@sharkinsspatial we're discussing the same recipe over at pangeo-forge/noaa-atmosphere-climate-cloud-properties-isccp-hgg-basic-feedstock#2 (comment), correct? I think in part the very long feedstock name (which is also quite close to another recent feedstock) is making it hard for me to be sure. |
@cisaacstern 👍 The names are almost identical (and very long 😆 ) differing by only one letter one is |
Ok thank goodness for a second there I thought I was seeing double 😆 . I'll throw in a +1 for shorter and more clearly differentiated names going forward (if possible). |
I've recently tested an merged both pangeo-forge/staged-recipes#235 and pangeo-forge/staged-recipes#241. The feedstock repositories are being created correctly https://github.com/pangeo-forge/noaa-atmosphere-climate-cloud-properties-isccp-hgh-basic-feedstock but it appears the feedstock registration with https://github.com/pangeo-forge/pangeo-forge-orchestrator and subsequent recipe run don't seem to be triggered.
The text was updated successfully, but these errors were encountered: