Release v0.6.0
Breaking Changes
This release removes .spec.runtime from the Build and BuildRun APIs, which was previously deprecated in v0.5.0.
Features
#883 by @SaschaSchwarze0: Nightly and normal releases now include a sample-strategies.yaml
#858 by @MayukhSobo: The BuildRun status is improved when a BuildRun Pod gets evicted.
#854 by @shahulsonhal: You can now specify annotations and labels in the Build that will be added to the image
#835 by @HeavyWombat: Introduced support for so called bundle images, which contain packaged source code and can be used instead of a Git repository for builds.
#817 by @coreydaley: Developers can now add Environment Variables to the Spec section of their Builds and BuildRuns.The Environment Variables will be added to all Steps of the chosen BuildStrategy, though any conflictswill result in a failed TaskRun.
#816 by @SaschaSchwarze0: The message field of the Succeeded condition of a failed BuildRun now includes the name of the step that has failed
#809 by @gabemontero: Support for cancelling an active BuildRun has been added.
#781 by @qu1queee: Add support for parameters in the strategies, so that users can parameterize their usage.
Fixes
#885 by @SaschaSchwarze0: The -sa suffix from generated service accounts has been removed so that BuildRuns with names longer than 60 characters also work with older Calico versions
#840 by @shahulsonhal: Added validation to make sure that Build and BuildRun names follow the required character limits
#813 by @HeavyWombat: Fixed issue in source retrieval code that led to slow loading times compared to the previous implementation.
API Changes
#871 by @shahulsonhal: You can now see the TaskRun results in BuildRun status
#854 by @shahulsonhal: You can now specify annotations and labels in the Build that will be added to the image
#836 by @imjasonh: Removes the .spec.runtime field that was deprecated in v0.5.0.
#835 by @HeavyWombat: Introduced support for so called bundle images, which contain packaged source code and can be used instead of a Git repository for builds.
#817 by @coreydaley: Developers can now add Environment Variables to the Spec section of their Builds and BuildRuns. The Environment Variables will be added to all Steps of the chosen BuildStrategy, though any conflicts will result in a failed TaskRun.
#809 by @gabemontero: Support for cancelling an active BuildRun has been added.
#781 by @qu1queee: Add support for parameters in the strategies, so that users can parameterize their usage.
Docs
#880 by @SaschaSchwarze0: Correcting the statement about the contextDir which is supported in all sample build strategies
Misc
#848 by @dalbar: Fixed documentation for build and buildStrategies
#839 by @HeavyWombat: Updated Git download step to avoid misleading warnings and messages.
#837 by @HeavyWombat: Improved output messages created by the Git step to be more human readable.