Future plans ...

[bjlittle]

@msarahan Thanks for conda-concourse-ci!

I'm tapping into compute_build_graph.construct_graph and compute_build_graph.order_build to determine the order to build multiple conda packages using conda 4 and conda-build 3... effectively replacing conda-build-all.

So what are the plans for conda-concourse-ci?

I see there is interest from conda-forge to replace the use of conda-build-all with a wrapper around construct_graph, as per PR 5274. How stable is compute_build_graph and will it be vendored elsewhere for the community to use standalone?

Also, conda-concourse-ci is available from c3i_test and your channel msarahan (but not as up to date as c3i_test) on Anaconda Cloud ... is c3i_test the most stable channel to pull updates from? Does c2i_test offer the latest master from https://github.com/conda/conda-concourse-ci ? And what's it's relationship with your offering from msarahan?

Also, are there plans for conda-concourse-ci to make it into https://repo.continuum.io/pkgs/main/linux-64/ ?

Apologies for all the questions.

Many thanks and regards

[msarahan]

In the medium-term, the graph stuff here will be split out and merged into conda-build.

I'm hesitant to recommend vendoring (ever), but if that's an interim necessity, so be it.

Actual packages of conda-concourse-ci (c3i for short) aren't really available because we're not really providing it as a fully-supported, user-facing tool. It's a very new thing that has grown around our needs for an internal package build system. It's very exciting to us that it's now becoming more useful than that initial purpose, but it means that we need to shift some of our current software development practices - like actually tagging versions rather than always just using master locally, and publishing packages of those tags.

Your best bet right now is to use the packages on c3i_test - those are built by the internal CI system after each merge to master here. Packages on msarahan are just whatever I'm testing, and I have no idea if they're safe to use. I'd generally avoid my personal channel, if I were you. I think I should change the image on anaconda.org to be a biohazard symbol.

As for putting c3i on the defaults channel - I'm not sure. I think our time is probably better spent working on getting the graph stuff moved over into conda-build. If you or anyone else wants to help start that migration with a PR to conda-build, I'd be happy to work with you on it.

[bjlittle]

@msarahan Thanks for the quick response, much appreciated.

I agree. Glad you're against vendoring. For me the home for the concourse graphing is firmly within conda-build itself.

I'll continue to use c3i_test and avoid your biohazard channel 😄

Also, it might be in our (the team I work with) best interests to try to push the graphing into conda-build ... I'll see if I can push that forward from our end and touch base with you. It's an obvious win for the whole conda community!

And feel free to close this issue.

Many thanks again 👍