Releases: AdamNowotny/BuildReactor
v5.0.0
- rewrite options UI from angular 1 to React
- update bootstrap to v5
- remove angular and webpack
- separate manifest.json for Chrome/Edge and Firefox (fixes warning in Chrome)
- remove "collapse groups" options - always true for more compact dashboard
- move static assets to public/ so vite works fine in DEV mode as well
npm run dev:mock
to develop outside of extension environment- update documentation for new API for services and dashboard UI
- remove font-awesome and replace with unplugin-icons
v4.0.0
- Rewrite for manifest v3 - switch from background page to service worker, remove RxJS from adapters (promise based)
- Dashboard/popup rewrite using React
- New API for CI server integrations and dashboards
- Switch from webpack to vite (settings page still pending)
- Add devcontainer.json for easier local setup
3.0.1
remove "tags" permission from manifest
3.0.0
- BREAKING: remove option to hide notifications when dashboard active (removes tabs permission, notifications can be disabled in settings)
- BuildKite: allow specifying branch to monitor
- Travis: show cancelled tag
- Travis: query only for git push events
- Settings page: remove old links in topnav
- fix badge counter
- fix drag&drop for service and builds list
- use chrome.notifications (fixes Firefox)
- update all dependencies
- use Webpack 5.x for build
- support for TypeScript
- README points to GitLab build badge
2.0.0
1.2.0
- all services moved to new API
- remove support for Snap
- teamcity plugin rewrite, reduce amount of requests needed
- jenkins support for WorkflowMultiBranchProjects (thanks to @ericweinberg)
- sort project groups on settings screen
- fix routing issues when service name contains "/"
- remove dependency on jQuery
1.1.1
Bring back branch selection for teamcity
1.1.0
Travis-CI update
Looks like Travis support has been broken for while as the APIs changed.
Support for this service has been rewritten and should now support public as well as private repositories and custom URLs.
Sorting
The last update broke custom sort order that you might have set up and always shown builds sorted by their ID.
This should be fixed now and the order will follow the one in set in projects
property in configuration of a service (you can check that on the "configuration" tab) . Also the drag&drop ordering will now work for services on the left side as well as monitored builds for a specific service.
API change
fields
property added to service information to specify which fields should show up on the configuration UI. It is optional and by default old behaviour will be used so old services should be compatible. More information at https://github.com/AdamNowotny/BuildReactor/blob/master/docs/adding-new-services.markdown
1.0.0
It's been over a year since last release, so much for "continuous deployment" 🥇
There has been however a lot of code improvements internally with big part of the code base rewritten and new releases should happen more often now.
The build process now uses Webpack and Babel to support ES6.
Most dependencies have been upgraded to latest versions (RxJS 4.1, Angular 1.5.8).
With the amount of changes and new simplified API for creating new services (read more at https://github.com/AdamNowotny/BuildReactor/blob/master/docs/adding-new-services.markdown) it seemed that it's about time for version 1.0.0
There's been quite a few new features which you can read about in the rest of the notes. Most should have reasonable defaults but can be configured or disabled on the settings page if it works better in your case.
BuildKite support
In previous versions you could use cctray to connect to BuildKite, but it has it's drawbacks - for example not being able to see the commit messages.
BuildReactor now supports BuildKite using it's native API.
To use the new integration you need to create access token at https://buildkite.com/user/api-access-tokens with the following permissions:
- read_builds
- read_organizations
- read_pipelines
You can find the code at https://github.com/AdamNowotny/BuildReactor/tree/master/src/services/buildkite/buildkite.js
Jenkins 2.x support
Jenkins integration has been rewritten and supports both Jenkins 1.x and 2.x.
You can now enter a URL that is pointing to a Jenkins view, not just the location of the server.
At the same time the dropdown to select Jenkins view has been removed as it's no longer needed.
You can find the code at https://github.com/AdamNowotny/BuildReactor/blob/master/src/services/jenkins/jenkins.js
Firefox compatibility
The extension is now compatible with Firefox. From now on new versions will be published on Mozilla add-ons and Chrome store.
The Firefox version can be installed at https://addons.mozilla.org/en-US/firefox/addon/buildreactor-extension/
Improved notifications
There is now a new "Notifications" page where you can enable or disable notifications completely or select which ones you'd like to see.
Enabling the new "Build started" and "Build finished" options allows to get notifications about each build, not only when it breaks of is fixed.
This might not be the best idea if you have a lot of builds, but if not then it's a good way to see what commits go into repositories you are interested in. This works best with services that report who made changes and what the message was as this information will be shown in each notification popup (cctray generally doesn't support this, some implementations show who broke the build only).
Show commit messages only for broken builds
With a lot of builds all showing last commit message the dashboard can look quite crowded. An option to hide these messages for successful builds has been added so only the ones that are broken will show who is responsible for fixing it.
Color-blind mode
The current red and green color are impossible to distinguish for people with color blindness so BuildReactor will now display visual indicators for broken builds and the ones that cannot be connected to.
This option is on by default.
v0.7.3 (10/07/2013)
- jenkins: increase timeout for getting project list
- notifications: bring them back, don't show if dashboard is active
- new permission required - tabs