Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep (at least a few) old versions in the apt repository #6824

Closed
ghost opened this issue Dec 3, 2018 · 4 comments
Closed

Keep (at least a few) old versions in the apt repository #6824

ghost opened this issue Dec 3, 2018 · 4 comments
Assignees
Labels
P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: process

Comments

@ghost
Copy link

ghost commented Dec 3, 2018

Description of the problem / feature request:

Please keep at least a few older releases available in the apt repository.

Feature requests: what underlying problem are you trying to solve with this feature?

AFAICT, bazel only maintains the latest release in the apt repository. This means that if bazel updates with a breaking change and some users in your company have it installed via apt, then they will be irreversibly updated to the latest bazel version on an apt upgrade. This gives you zero time to roll out any fixes you need to update against breaking changes before they break peoples builds.

If bazel kept a few (maybe four or so) older releases in the apt repository, then you could simply tell affected users to downgrade their installation to one that works while a fix for your build files are worked on, then let them know they can safely upgrade when the fixes are out. This would make working with bazel so much smother across the organisation.

I like the fact that people installing from apt will, by default, get the latest and greatest as it comes out. But it can be very frustrating when the latest and greatest gives me zero time to roll out updates to our build configuration with no easy way for users to temporarily downgrade to a working version.

@iirina iirina added untriaged team-Bazel General Bazel product/strategy issues labels Dec 4, 2018
@kamahen
Copy link

kamahen commented May 4, 2019

It's easy to make a mistake and upgrade Bazel even when I know the latest version is broken, because the typical way of upgrading is

$ sudo apt-get update && sudo apt-get --with-new-pkgs upgrade 

and it's easy to not notice that bazel is in the list of upgraded packages.

And there's only one version in the PPA:

$ apt list -a bazel
Listing... Done
bazel/unknown,now 0.25.0 amd64 [installed]

@dslomov dslomov added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website and removed team-Bazel General Bazel product/strategy issues labels Jul 19, 2019
@philwo philwo added P2 We'll consider working on this in future. (Assignee optional) type: process and removed untriaged labels Jul 29, 2019
@philwo philwo self-assigned this Jul 29, 2019
@philwo philwo added P1 I'll work on this now. (Assignee required) and removed P2 We'll consider working on this in future. (Assignee optional) labels Oct 23, 2019
@philwo
Copy link
Member

philwo commented Oct 23, 2019

I'm working on fixing this right now. We will provide all older Bazel versions in our apt-get repository in addition to the latest one and probably also make it possible to install versions in parallel (e.g. Bazel 0.29.1 can be installed side-by-side as /usr/bin/bazel-0.29.1).

Comments on the latter idea are welcome, whether that would be useful for you.

@ghost
Copy link
Author

ghost commented Oct 23, 2019

For the moment this is no longer an issue for my team, as we're using bazelisk to manage versions now.

However I still think this is worth fixing (and the side-by-side install support also makes sense to me)

@philwo
Copy link
Member

philwo commented Nov 25, 2019

@meteorcloudy fixed this in 3162705. :) Our apt repository now contains all stable version released since 1.0.0 and will continue to do so in the future

@philwo philwo closed this as completed Nov 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: process
Projects
None yet
Development

No branches or pull requests

4 participants