[
https://jira.codehaus.org/browse/SCM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated SCM-775:
-------------------------------
Description:
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.
was:
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.
[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
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.
> Request for new optional parameter RTC (workItem) with release:prepare to
> associate workitem with changesets got created during build process
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SCM-775
> URL: https://jira.codehaus.org/browse/SCM-775
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-jazz
> Affects Versions: 1.9.1
> Reporter: AShit Shah
>
> 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.1.6#6162)
