Remove bleeding edge builds from production Debian repo.
Description
If we sync S3 after bumping the version number after a build, the bleeding edge version will get pushed to S3 and will show as the latest version. Create two folders on the integration server. One for the bleeding edge release and one for stable. Run the repo task on both, but only place stable deb files in the stable folder. The stable folder is what gets pushed to S3.
Gliffy Diagrams
Activity
Show:
Brad Wood January 7, 2016 at 12:51 AM
There are now debs-stable and RPMS-stable folders on the integration server. The "normal' debs and RPMS folders are populated on every commit with the bleeding edge builds. The *-stable folders are only added to if the commandbox.version and commandbox.stableVersion properties in the build match, meaning this is a stable build. Only the *-stable folders are synced to S3 so when you install from the stable source lists, you get the last stable version.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
If we sync S3 after bumping the version number after a build, the bleeding edge version will get pushed to S3 and will show as the latest version. Create two folders on the integration server. One for the bleeding edge release and one for stable. Run the repo task on both, but only place stable deb files in the stable folder. The stable folder is what gets pushed to S3.