[
https://issues.apache.org/jira/browse/SCM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525770#comment-14525770
]
ASF GitHub Bot commented on SCM-775:
------------------------------------
GitHub user ChrisGWarp opened a pull request:
https://github.com/apache/maven-scm/pull/33
Scm 775
This pull requests implements the SCM-775 functionality needed to support
workItem/Tasks for scm deliver operations. Currently implemented for Jazz, the
base work applied, will allow TFS, ClearCase and others to access work items.
There is also a corresponding patch attached to MRELEASE-909.
All feedback welcome.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChrisGWarp/maven-scm SCM-775
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-scm/pull/33.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #33
----
commit b1ab76eba177ea64e824dc23bca82303497ccb3e
Author: ChrisGWarp <[email protected]>
Date: 2015-04-04T10:33:44Z
Change: Added consume
commit df117ec3b5867613a221ecc2099143d679e80b09
Author: <[email protected]>
Date: 2015-04-28T12:56:24Z
Changed: Implemented changes necessary to support SCM-775, the adoption
of workItem support for Jazz, and the basis for other SCMs.
commit cf0fea2993ea87d59acae81f512af1ea918879e3
Author: ChrisGWarp <[email protected]>
Date: 2015-04-29T11:29:58Z
Updated Javadoc.
commit cc1a08d6a8cd008f5077127bc72e3b2e291a1771
Author: Chris Graham <[email protected]>
Date: 2015-05-01T02:10:17Z
Changed: Fixed the failing changeset associate test (on unix).
commit 88e75c5fcfa5b8ca47d1432d05b91c63398fb39a
Author: Chris Graham <[email protected]>
Date: 2015-05-02T12:49:07Z
Changed: Added support for multiple changesets.
Changed: Added status calls where necessary to pick up change set
aliases as well as workspace/stream names and aliases.
Changed: Added additional StatusConsumer test cases.
----
> Add workItem and changeset associate support for scm deliver
> ------------------------------------------------------------
>
> Key: SCM-775
> URL: https://issues.apache.org/jira/browse/SCM-775
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-jazz
> Affects Versions: 1.9.1
> Reporter: AShit Shah
> Assignee: Chris Graham
> Fix For: 1.9.5
>
>
> Maven {{release:prepare}} command is failing with below error while
> delivering updated pom.xml to the stream due to Preconditions configured in
> RTC to have comments and associated work item with every delivery.
> {noformat}
> [ERROR] Name: Deliver
> [ERROR] Participant Reports:
> [ERROR] Name: Require Work items and Comments
> [ERROR] A work item must be associated with the change set.`
> [ERROR] At least one of the associated work items must specify that the work
> is planned for the current iteration.
> [ERROR] At least one of the associated work items must be assigned to you.
> [ERROR] Problem running 'deliver':
> [ERROR] 'Deliver' failed. Preconditions have not been met: A work item must
> be associated with the change set.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli)
> on project junit-ext: Unable to commit files
> Provider message:
> Error code for Jazz SCM deliver command - 17
> {noformat}
> I can not find any optional parameters on
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html
> for release:prepare command which I can use and pass the RTC workitem number
> on command line.
> Suggestion:
> It will be great if you can provide optional parameters like "workItem" which
> I can use and pass RTC workitem number with release:prepare at command line.
> Example: {{mvn -PmyProfile release:prepare -DworkItem=123456}}
> So build process should associate change sets created by {{release:prepare}}
> with work item 123456 and deliver change sets to the stream.
> As of now I have to use "{{-DpushChanges=false}}" parameter to block delivery
> process and I have to manually find the change sets, associate them with work
> item and deliver them before I run {{release:perform}}.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
