Remove custom workflow [ci skip]

[jaimergp]

Please remove this workflow. This is not allowed as per https://conda-forge.org/docs/maintainer/infrastructure.html#third-party-use-of-our-ci-services. The associated branch (development) should also go.

Thank you for understanding!

[looooo]

So what is the solution for building the library twice a week?

[jaimergp]

My current understanding (others from @conda-forge/core please feel free to chime in) is that conda-forge is not really meant as a "nightlies" publication channel. An RC here and there is ok as a pre-release, but that kind of ongoing snapshots should be done in a separate infrastructure. You can use conda-smithy to reasonably set up your own feedstock in your own organization, which can post to your custom Anaconda.org channel as often as you want.

Some guides to make this happen:

1. Clone this feedstock to a separate organization. I did say "clone" because if you "fork" all the PRs you open there will point to conda-forge org by default and it is a bit annoying :D
2. Edit conda-forge.yml so it uses Github Actions as the CI:

provider:
  win: github_actions
  osx: github_actions
  linux: github_actions

3. Add the channels to recipe/conda_build_config.yaml:

channel_targets:
  # syntax: channel_name label
  - my-custom-channel dev
channel_sources:
  - conda-forge

4. Rerender locally with conda-smithy rerender.
5. Edit your workflow as needed to add a cronjob, and/or add the automation you have here.
6. Create the Anaconda.org channel mentioned in conda_build_config.yaml if you don't have it yet, and generate a channel token.
7. Set the secrets required by the workflow (mostly the Anaconda.org token, I think?).

Let me know if you have questions!

[adrianinsaval]

@looooo could you contact me via pm on the forum? I can make it work on our own repo but I would like to make the uploads on the org account on anaconda rather than simply my personal account

[looooo]

I would first like to know if there is really no other option for this or compromise. In my mind uploading to the conda-forge anaconda channel would be a big improvement as we could store more packages than with the personal channel. And also I saw other organisations doing similar things with pre_releases.

[beckermr]

The conda-forge anaconda.org channel storage is provided as a resource to the community by Anaconda inc. at no charge to conda-forge. I understand it is bigger than a personal channel. However, we have to use this resource responsibly.

[adrianinsaval]

Do we need that much storage? it might be possible to automate cleanup of older dev packages, or if the pricing is reasonable and we do need the extra storage we could ask for funding to the FPA.

[looooo]

No it's not mandatory. In the past I always deleted the old packages manually.