You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #1453 but more specific. Travis is probably sufficient at this point for the purposes of general community CI, but I want even more control. In order to maintain our stability promises when making feature and API changes we will want a way to run experiments on a broad base of packages, against arbitrary revisions of Rust (e.g. before commiting to nightly/beta).
This does have a lot of overlap with general Travis support since cargo packages will want to be able to test against all release channels. I'm not sure whether this integrates with Travis or is a separate tool.
I would guess that we maybe able to discover packages through travis, but we may not be able to custom build them all on travis. It may be worth talking to some of the travis folks about this, though.
Related to #1453 but more specific. Travis is probably sufficient at this point for the purposes of general community CI, but I want even more control. In order to maintain our stability promises when making feature and API changes we will want a way to run experiments on a broad base of packages, against arbitrary revisions of Rust (e.g. before commiting to nightly/beta).
This does have a lot of overlap with general Travis support since cargo packages will want to be able to test against all release channels. I'm not sure whether this integrates with Travis or is a separate tool.
cc @alexcrichton @aturon @nikomatsakis
The text was updated successfully, but these errors were encountered: