v1.4.3

This version contains some security patches, additional testing, small adjustments to documentation and checks on whether a port has been specified for testing/healthchecks.

• Not specifying a port for a job or a healthcheck now raises an error
• Bump the docker version to address CVE-2024-41110 (again)
• Add testing for job.RunCommitByOffset
• Add documentation to job.RunCommitBy(Offset|Hash) to clarify whether the job as to have been initialized already or not

Full Changelog: v1.4.2...v1.4.3

v1.4.2

This version contains some security patches, additional testing and a small change to how failing healthchecks are treated.

• Failing healthchecks are now treated as a broken build, instead of returning an error
• Bump the docker version to address CVE-2024-41110
• Add testing for broken commits
• The testing pipeline now no longer fails if the codecov upload doesn't succeed

Full Changelog: v1.4.1...v1.4.2

v1.4.1

This version includes two small fixes.

• Fixes job not being stopped when finishing RunCommitByHash
• Fixes a semaphore not being released if a docker image build fails, possibly leading to a deadlock

Full Changelog: v1.4.0...v1.4.1

v1.4.0

This version contains new features, fixes and some QOL improvements.

• Adds the RunCommitByHash and RunCommitByOffset functions, allowing users of the Go package to spin up a replica of a job, running a certain commit
• Adds the possibility of defining a host parameter, to which container ports should be exposed to
• Changes default container host to be 127.0.0.1, leading to container ports not being publicly exposed by default
• Adds graceful shutdown to the CLI on interrupts and panics
• Fix replacements file argument being ignored
• Adds a prefix to the created tmp directories
• Forces image removal on cleanup
• Sets GIN_MODE to release on release binaries, without which the CLI would run a debug version of the web server

Full Changelog: v1.3.0...v1.4.0

v1.3.0

This release contains some QOL improvements.

• Adds another field to the OffendingCommits to show possible aliases of the offending commit, if some builds failed
• Switches out a dependency to allow biscepter to be built on systems other than linux/amd64
• Improves error logging and reporting, displaying the output of failed commands
• Adds a workflow for building release binaries

Full Changelog: v1.2.2...v1.3.0

v1.2.2

This release contains some QOL improvements.

• Running the clean subcommand now prunes all image children as well
• Docker containers and images are now identified through a tag, instead of by name

Full Changelog: v1.2.1...v1.2.2

v1.2.1

This release includes a bugfix and some QOL improvements.

• Fixed a bug which would sometimes cause a stack overflow if a bisection was started on a job that already has commit replacements
• Biscepter now prints a rough estimate of how many runs are left for complete bisection
• Removed the completion command, autogenerated by cobra-cli

Full Changelog: v1.2.0...v1.2.1

v1.2.0

With this version, biscepter now remembers and avoids commits that break the build of the system being tested!

Full Changelog: v1.1.0...v1.2.0

v1.1.0

This release adds some new features and fixes a few bugs.

• Added the clean command, allowing easy cleanup of the artifacts biscepter created
• Added the option of specifying the max amount of concurrent running replicas
• Added more exhaustive logging during job starting
• Ensured that changing the Dockerfile for a job doesn't result in biscepter reusing builds of older Dockerfiles for the same job
• Fixed the way the commit offset was calculated for determining the next commit to build

Full Changelog: v1.0.0...v1.1.0

v1.0.0

This marks biscepter's first release!

This version includes features such as:

• Concurrent bisecting
• Commit build caching
• Choosing nearby built commits instead of the middle one to save on build cost
• Go package
• RESTful HTTP API

I hope you find biscepter to prove useful!