Verify dependencies aren't Integration Builds as first step of release

Letractively / jcatapult

Automatically exported from code.google.com/p/jcatapult

0 stars 0 forks source link

Verify dependencies aren't Integration Builds as first step of release #14

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

1.  Project has dependency on an integration build (ex: 1.0-A1-{integration})
2.  Perform a full or tag-only release
3.  release scripts will tag release and then fail during publishing.

Suggested Fix:
Integration check should happen before tagging occurs.

Original issue reported on code.google.com by leafkn...@gmail.com on 14 Feb 2008 at 11:33

GoogleCodeExporter commented 8 years ago

Original comment by bpontare...@gmail.com on 18 Mar 2008 at 3:54

Added labels: Component-Ant, Milestone-1.0-M2

GoogleCodeExporter commented 8 years ago

Original comment by bpontare...@gmail.com on 18 Mar 2008 at 4:17

GoogleCodeExporter commented 8 years ago

This shouldn't re-order the release as suggested in description, but instead 
should
add a new Ant task to Savant that allows IB checks.

Original comment by bpontare...@gmail.com on 18 Mar 2008 at 6:18

Changed title: Verify dependencies aren't Integration Builds as first step of release

GoogleCodeExporter commented 8 years ago

Added a new task to check integration builds to Savant and updated the 
release-svn
plugin to use it. This required a new macrodef that checks the project prior to
release to ensure it is ready to go.

Forgot to include the issue in the commit, so the changeset is 495 and all 
changes
were in Savant and JCatapult-Ant.

Original comment by bpontare...@gmail.com on 19 Mar 2008 at 2:11

Changed state: Fixed