update cirlceci

[nick-youngblut]

@conda-forge-admin, please update circle

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I just wanted to let you know that I updated the circle-ci deploy key and followed the project.

[nick-youngblut]

@conda-forge-admin, please rerender

[bgruening]

I think it needs to be the issue header.

[nick-youngblut]

@bgruening do you mean for "conda-forge-admin, please update circle", because you use "conda-forge-admin, please rerender" within Issue#1 in for the r-picanted-feedstock

[bgruening]

Oh no, I created conda-forge/r-picante-feedstock#2 later on.

[nick-youngblut]

Oh yeah, I definitely missed that. Thanks for the heads up!

[bgruening]

Thanks Nick!

[djsutherland]

@nick-youngblut, not sure if you've realized this since but because I'm clearing out old github notifications:

• "update circle" doesn't trigger a rebuild on CircleCI; it updates some metadata information that occasionally expires. You shouldn't need it unless CircleCI isn't running builds at all.
• You can force a rebuild either through the web UI (Explaining how to restart CircleCI conda-forge.github.io#595) or by pushing an empty commit git commit --allow-empty -m "empty commit to rebuild"; this will trigger a rebuild on all platforms).
• You should be able to trigger a rerender within an issue as well; I just double-checked in merge with shogun-cpp recipe shogun-feedstock#10 (comment). Don't know why it didn't work here; might have been a transient failure, might have been a webservices bug....

[nick-youngblut]

Thanks @dougalsutherland for the clarification! Is that information in the conda-forge docs? I don't remember reading it.