[
https://issues.apache.org/jira/browse/SCM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815101#comment-16815101
]
Chris Graham edited comment on SCM-889 at 4/11/19 6:27 AM:
-----------------------------------------------------------
Thank you for responding [~serozaki]!
The code was originally written to honour the pom.xml, and I think that it
should continue to be, as this change will change the existing
workflow/patterns already in place.
I wrote some documentation and suggestions on how to best use the release
plugin with Jazz, read it [Using the Release Plugin with the Jazz SCM
provider|http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/releases.html].
That was 4 years ago (before I was using this in a CI env). In a CI env,
Jenkins or even Jazz's own, I would rename the *BuildWorkspaces to
*ReleaseWorkspaces to make it clearer. If you do have CI in place (and not
Jazz's private builds), then I would have both the *BuildWorkspaces (for the
usual CI SNAPSHOT builds) and the *ReleaseWorkspaces to perform your releases
in.
If you have the flow targets set up correctly, then the changesets commits and
tags should be pushed up to a stream. The Jazz equivalent of a tag is a
Snapshot which is across all components in a repository workspace, which is why
only one component in each *BuildWorkspace (should be renamed
*ReleaseWorkspace).
The concern here about your change is that it relies upon local setup not
captured in the pom, which may lead to non repeatable builds.
In your case, it's clear: the workspace in the pom does not need to be changed.
It simply needs to be the release workspace, not your 'master' which should
probably be a Stream anyway.
I would also caution against direct comparisons with Git, Perforce, ClearCase
or other similar SCM's. Each are different, some radically so. I would
encourage you to think in Jazz terms, not compare against other SCM's.
was (Author: chrisgwarp):
Thank you for responding [~serozaki]!
The code was originally written to honour the pom.xml, and I think that it
should continue to be, as this change will change the existing
workflow/patterns already in place.
I wrote some documentation and suggestions on how to best use the release
plugin with Jazz, read it [Using the Release Plugin with the Jazz SCM
provider|http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/releases.html].
That was 4 years ago (before I was using this in a CI env). In a CI env,
Jenkins or even Jazz's own, I would rename the *BuildWorkspaces to
*ReleaseWorkspaces to make it clearer. If you do have CI in place (and not
Jazz's private builds), then I would have both the *BuildWorkspaces (for the
usual CI SNAPSHOT builds) and the *ReleaseWorkspaces to perform your releases
in.
If you have the flow targets set up correctly, then the changesets commits and
tags should be pushed up to a stream. The Jazz equivalent of a tag is a
Snapshot which is across all components in a repository workspace, which is why
only one component in each *BuildWorkspace (should be renamed
*ReleaseWorkspace).
The concern here about your change is that it relies upon local setup not
captured in the pom, which may lead to non repeatable builds.
In your case, it's clear: the workspace in the pom does not need to be changed.
It simply needs to be the release workspace, not your 'master' which should
probably be a Stream anyway.
> Jazz tag command creates snapshot in wrong workspace
> ----------------------------------------------------
>
> Key: SCM-889
> URL: https://issues.apache.org/jira/browse/SCM-889
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jazz
> Affects Versions: 1.9.5, 1.10.0
> Reporter: Sérgio Ozaki
> Assignee: Chris Graham
> Priority: Major
> Fix For: 1.11.1
>
>
> Jazz provider tag command uses the jazz workspace set int the pom.xml scm
> tag. When in other jazz workspace, the snapshot is not created based on the
> current work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
