[
https://issues.apache.org/jira/browse/SCM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962963#comment-17962963
]
ASF GitHub Bot commented on SCM-775:
------------------------------------
jira-importer commented on issue #982:
URL: https://github.com/apache/maven-scm/issues/982#issuecomment-2964637418
**[Eric
B](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=benze)**
commented
I'm running into the same issue as well with RTC 4.0.2. I figure that there
are a few different ways of handling this:
1) Specify a WI # as a -D parameter (comma delimited maybe even if multiple
WIs?)
2) Specify WI # as pom parameters
3) Perform a query for a WI given some fairly specific criteria (user,
title, etc). I'm not entirely sure that this is even feasible using 'scm'.
My biggest concern with all these options is that the behaviour should be
consistent with the scm plugin; having jazz provider specific parameters isn't
ideal. However, I don't see any notion of issues/workItems/etc in the scm docs
and/or the release plugin.
I would be very curious to know how other providers have implemented this,
if at all. I took a quick look at the docs for the different providers and
haven't seen anything there.
> Add workItem and changeset associate support for scm deliver
> ------------------------------------------------------------
>
> Key: SCM-775
> URL: https://issues.apache.org/jira/browse/SCM-775
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-jazz
> Affects Versions: 1.9.1
> Reporter: AShit Shah
> Assignee: Chris Graham
> Priority: Major
> 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
(v8.20.10#820010)
