search

anaconda-graveyard / conda-concourse-ci

Conda-driven Concourse CI for package building
BSD 3-Clause "New" or "Revised" License
13 stars 29 forks source link

c3i_test #87

Open bjlittle opened 6 years ago

bjlittle commented 6 years ago

@msarahan conda-concourse-ci appears to be no longer available from the c3i_test channel... are you guys hosting it from some other channel now?

If so where?

Thanks!

bjlittle commented 6 years ago

Also, are you considering cutting another release soon?

mingwandroid commented 6 years ago

Are you using it? That channel is for the Anaconda Distribution team to do various things with so not somewhere to put packages for any long term storage!

bjlittle commented 6 years ago

@mingwandroid To be honest, I was using it to tap into conda_concourse_ci.compute_build_graph to use the construct_graph and order_build functions.

They are just the glue I was looking for to build conda recipes on top of the Anaconda 5.0 Distribution using conda-build version 3.8.1... as conda-build-all just wasn't cutting it with the new flavour of recipes that include the new Jinja2 templating and compiler tool loveliness.

I can easily snapshot conda-concourse-ci at a relevant master commit and host it in my own channel, but it sure would be kinda nice (from my selfish perspective) to base things from a release tag.

I know from speaking to @msarahan that conda-concourse-ci is really for the Anaconda Distribution guys internal use, but it contains pretty cool functionality that allows you to easily build more than one conda recipe and all it's dependencies, in the right order, for the new style conda recipes.

There's a gap in the functionality between conda-build-all and conda-build and that's conda-concourse-ci.compute_build_graph... shame it's not in conda-build, hence why I'm cheekily using conda-concourse-ci :wink:

Was just wondering, if it's not an issue, whether you guys would consider tagging another release, to capture all the goodness that's been banked in conda-concourse-ci since 0.1.1 back in May last year :smiley:

msarahan commented 6 years ago

Sorry, we just don't have time to tag this, and definitely not to support it. You're free to maintain your own packages, of course. I'll try not to force push unless it's really necessary.