[closed] How can I pre-validate a stream-to-stream delivery using Java API or lscm?
Andy Jewell (242●3●61●74)
| asked Oct 16 '14, 7:00 p.m.
closed Oct 17 '14, 5:22 a.m. by Ralph Schoon (63.1k●3●36●46)
We use multiple streams to manage our promotion between development, test, and production environments. E.g.:
Dev Stream → Test Stream → Production Stream
Our whole organization has this addiction to cherry picking work items. So we get 30 or 40 different changesets against 10 or 20 different work items and then they choose 5-15 they want to promote.
When we try to promote (deliver) that subset of changesets we often get either the "can't promote changeset x because doing so would create a version gap" error or the "can't promote changeset x because this would cause a conflict. Use a workspace instead and resolve the conflicts first" error.
Can anyone suggest a way to prevalidate that any given set of changesets would be "ok" to deliver -- before actually delivering?
|
Comments
Closed as duplicate. See https://jazz.net/forum/questions/165776/how-can-i-pre-validate-a-stream-to-stream-delivery-using-java-api-or-lscm