Skip to content
This repository has been archived by the owner on Dec 9, 2022. It is now read-only.

Auto cf #256

Closed
wants to merge 5 commits into from
Closed

Auto cf #256

wants to merge 5 commits into from

Conversation

CJ-Wright
Copy link
Collaborator

@CJ-Wright CJ-Wright commented Jan 19, 2018

Closes #255
@jrmlhermitte @danielballan
I think this should work, it worked on my local. Once everyone is happy with this they should:

  1. turn the totally_not_a_travis.yaml file into a valid .travis.yaml
  2. Run doctr to get the keys setup properly
  3. Figure out which branch to push to so we don't end up with recursive things (one may consider separating the branches/repos which hold the recipes for general PRing and the branches/repos which hold the recipes for the internal server to read/build) (one could also consider putting this script in a separate repo, cloning this repo, updating everything, and then pushing back to this repo.
  4. Turn on travis

@tacaswell
Copy link
Member

Can this be done with plain python or plain bash?

@CJ-Wright
Copy link
Collaborator Author

Probably, PRs welcome.

@danielballan
Copy link
Contributor

We have no xonsh users on staff, so we are not really able to maintain this as is. As you speak xonsh, would you be willing to translate it for us?

@CJ-Wright
Copy link
Collaborator Author

I won't be able to translate this right now. I may be able to later in the week. If there is some interest in learning xonsh here are the docs:

Xonsh is fairly intuitive, the deps are very light, and the devs are very responsive.

Copy link
Member

@tacaswell tacaswell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove xonsh usage.

@danielballan
Copy link
Contributor

I really love xonsh; I hope it takes over the world; I agree with @tacaswell that this is not a good enough reason to add yet-another-thing that some onboarding member of staff would have to learn in order to maintain our already-complex build stack.

Sorry for the thanks-for-the-milk-can-we-have-a-cookie nature of this request, but some help translating this would be great when you have the time!

@CJ-Wright
Copy link
Collaborator Author

@mrakitin this is the PR with auto conda-forge updating.

@mrakitin
Copy link
Member

mrakitin commented Jan 3, 2019

@CJ-Wright, thanks, but I'm not sure how we can use it with our current building approach. Can you explain?

@CJ-Wright
Copy link
Collaborator Author

This would issue PRs into lightsource2-recipes with updates from the conda-forge recipes which are in lightsource2. Those PRs could be merged and then building would continue as normal. The main benefit of this is that new versions/updates to recipes from the community would be PRed over to lightsource2-recipes automatically.

A potential extension of this would be to build a graph and check that all deps are on lightsource2-recipes or defaults, but that could be done later.

@mrakitin mrakitin added this to the nsls-ii-forge milestone Mar 15, 2019
@CJ-Wright CJ-Wright closed this Jul 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Auto pull recipes from conda forge
4 participants