Summary

Auto-enable Power Pack and force it to enable on upgrade.

Review Request #15079 — Created May 27, 2026 and submitted May 27, 2026, 3:14 p.m.

Information

Owner

chipx86

Repository

Review Board

Branch

release-8.x

Bugs

Depends On

Reviewers

Groups

reviewboard

People

Description

Power Pack is now a key component of Review Board, and we want to enable
it by default just like we do with rbintegrations. This change adds it
to the auto-enable list so new installs will have it by default.

Older installs may have once had it but have disabled it. For these
installs, we'll need to auto-enable it on upgrade.

The Power Pack dependency and auto-enable in the Dockerfile has also been
removed from the Docker image, since that's taken care of now by the package
dependency and rb-site.

Testing Done

Created a local install and verified Power Pack was enabled. Disabled it
and upgraded, and verified it was re-enabled.

Conducted the same test within Docker using production-built packages.
Same results.

Commits

Summary	ID
Auto-enable Power Pack and force it to enable on upgrade. Power Pack is now a key component of Review Board, and we want to enable it by default just like we do with rbintegrations. This change adds it to the auto-enable list so new installs will have it by default. Older installs may have once had it but have disabled it. For these installs, we'll need to auto-enable it on upgrade.	dadfbb92ee72db62dea2493b52da0b3ab5268942

Issues

Description	From	Last Updated
Maybe "an error occurred during setup of an extension"?	david	May 27, 2026, 3:08 p.m.
console.progress_step() has its own try/catch, meaning if we catch this here we'd end up with: Setting up integrations ... ERROR: …	david	May 27, 2026, 2:59 p.m.
Do we want to wrap this is console.progress_step here? (esp. if we rely on it for error handling)	david	May 27, 2026, 3 p.m.

flake8 passed.

JSHint passed.

Testing Done:: +
Created a local install and verified Power Pack was enabled. Disabled it
+ and upgraded, and verified it was re-enabled.
+
+
Conducted the same test within Docker using production-built packages.
+ Same results.

reviewboard/cmdline/rbsite.py (Diff revision 1)

The issue has been resolved. Show all issues

console.progress_step() has its own try/catch, meaning if we catch this here we'd end up with:

Setting up integrations ...
ERROR: Unexpected error setting up Power Pack: err
OK

reviewboard/cmdline/rbsite.py (Diff revision 1)

The issue has been resolved. Show all issues

Do we want to wrap this is console.progress_step here? (esp. if we rely on it for error handling)

Change Summary:


Simplified extension setup and removed the error handling, leaving it to callers.
Wrapped extension setup in a console.progress_step() during upgrade.

Commits:

	Summary	ID
	Auto-enable Power Pack and force it to enable on upgrade. Power Pack is now a key component of Review Board, and we want to enable it by default just like we do with rbintegrations. This change adds it to the auto-enable list so new installs will have it by default. Older installs may have once had it but have disabled it. For these installs, we'll need to auto-enable it on upgrade.	98c645a188e97f2c84729c961082c9e72edf94fc
	Auto-enable Power Pack and force it to enable on upgrade. Power Pack is now a key component of Review Board, and we want to enable it by default just like we do with rbintegrations. This change adds it to the auto-enable list so new installs will have it by default. Older installs may have once had it but have disabled it. For these installs, we'll need to auto-enable it on upgrade.	dadfbb92ee72db62dea2493b52da0b3ab5268942

Diff:

Revision 2 (+54 -32)

Show changes

	contrib/docker/Dockerfile
	contrib/docker/scripts/docker-entrypoint.sh
	reviewboard/settings.py
	reviewboard/cmdline/rbsite.py

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Ship it!

reviewboard/cmdline/rbsite.py (Diff revisions 1 - 2)
The issue has been resolved. Show all issues
```
Maybe "an error occurred during setup of an extension"?
```

Status:: Completed
Change Summary:: Pushed to release-8.x (d7a0d13)

	+	Created a local install and verified Power Pack was enabled. Disabled it
	+	and upgraded, and verified it was re-enabled.
	+
	+	Conducted the same test within Docker using production-built packages.
	+	Same results.