Not receiving 'incoming' from repository workspace
Hi,
I am in the JazzUsers group of a repository with a contributor license.
I have loaded the source code into projects in the RTC client by loading
the components from a repository workspace - actually its the continuous
build repository workspace for the project area. So the repository
workspace is flowed to from the (only) stream.
However, when there are changes in the repository workspace because they
flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace to get
notified? (I can't because as a contributor I can't create a repository
workspace).
Thanks,
Jeremy
I am in the JazzUsers group of a repository with a contributor license.
I have loaded the source code into projects in the RTC client by loading
the components from a repository workspace - actually its the continuous
build repository workspace for the project area. So the repository
workspace is flowed to from the (only) stream.
However, when there are changes in the repository workspace because they
flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace to get
notified? (I can't because as a contributor I can't create a repository
workspace).
Thanks,
Jeremy
7 answers
Repository workspaces can only be manipulated by administrators & the
owner of a workspace. You require a Developer license to create a
repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
owner of a workspace. You require a Developer license to create a
repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor license.
I have loaded the source code into projects in the RTC client by loading
the components from a repository workspace - actually its the continuous
build repository workspace for the project area. So the repository
workspace is flowed to from the (only) stream.
However, when there are changes in the repository workspace because they
flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace to get
notified? (I can't because as a contributor I can't create a repository
workspace).
Thanks,
Jeremy
As contributor, I don't feel the need to create a repository workspace.
There is already one I can load the source from. Does 'being notified
(blue incoming arrows) and receiving updates from a repository workspace
to my local eclipse workspace' count as manipulating the workspace? If
so then I can see why I'm not able to achieve what I'm trying. I'm not
looking to alter source code, just get notified when there are changes.
I think I have a valid user story here though: A user with a contributor
license wishes to extract the source, compile it in eclipse, then
construct a patch for a problem he's having and post it to a work item
for a user with a developer license to try out and potentially check-in.
While the contributor is doing this, the code in the stream flowing into
the repository workspace changes, and the contributor should be notified
of this with blue incoming arrows (which from my experience isn't
happening) so that he can adjust his patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
There is already one I can load the source from. Does 'being notified
(blue incoming arrows) and receiving updates from a repository workspace
to my local eclipse workspace' count as manipulating the workspace? If
so then I can see why I'm not able to achieve what I'm trying. I'm not
looking to alter source code, just get notified when there are changes.
I think I have a valid user story here though: A user with a contributor
license wishes to extract the source, compile it in eclipse, then
construct a patch for a problem he's having and post it to a work item
for a user with a developer license to try out and potentially check-in.
While the contributor is doing this, the code in the stream flowing into
the repository workspace changes, and the contributor should be notified
of this with blue incoming arrows (which from my experience isn't
happening) so that he can adjust his patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
Repository workspaces can only be manipulated by administrators & the
owner of a workspace. You require a Developer license to create a
repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor
license. I have loaded the source code into projects in the RTC client
by loading the components from a repository workspace - actually its
the continuous build repository workspace for the project area. So the
repository workspace is flowed to from the (only) stream.
However, when there are changes in the repository workspace because
they flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace to
get notified? (I can't because as a contributor I can't create a
repository workspace).
Thanks,
Jeremy
I think part of the confusion may be that the incoming arrows are not an indication of differences between your Eclipse Local Workspace and the Repository Workspace that you loaded from, but rather those arrows are incoming/outgoing between the Repository Workspace and whichever Stream it is collaborating with.
Usually, your Eclipse Local Workspace is in sync with a mirrored Repository Workspace that you own, and thus blue incoming arrows from streams is meaningful to both your local workspace and repository workspace. When you accept, you are updating your Repository Workspace AND in the same action, the client also downloads it to your local workspace to keep them in sync at the same time.
So, technically, I think you should be able to see incoming of whenever the Continuous Build Workspace has differences with the Continuous Stream; however, I think the build system always tries to keep those two up to date as possible but since you're not the one invoking the accept (since you don't own it), what you've loaded will surely become out of sync with the Repository Workspace without notification.
Usually, your Eclipse Local Workspace is in sync with a mirrored Repository Workspace that you own, and thus blue incoming arrows from streams is meaningful to both your local workspace and repository workspace. When you accept, you are updating your Repository Workspace AND in the same action, the client also downloads it to your local workspace to keep them in sync at the same time.
So, technically, I think you should be able to see incoming of whenever the Continuous Build Workspace has differences with the Continuous Stream; however, I think the build system always tries to keep those two up to date as possible but since you're not the one invoking the accept (since you don't own it), what you've loaded will surely become out of sync with the Repository Workspace without notification.
As contributor, I don't feel the need to create a repository workspace.
There is already one I can load the source from. Does 'being notified
(blue incoming arrows) and receiving updates from a repository workspace
to my local eclipse workspace' count as manipulating the workspace? If
so then I can see why I'm not able to achieve what I'm trying. I'm not
looking to alter source code, just get notified when there are changes.
I think I have a valid user story here though: A user with a contributor
license wishes to extract the source, compile it in eclipse, then
construct a patch for a problem he's having and post it to a work item
for a user with a developer license to try out and potentially check-in.
While the contributor is doing this, the code in the stream flowing into
the repository workspace changes, and the contributor should be notified
of this with blue incoming arrows (which from my experience isn't
happening) so that he can adjust his patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
Repository workspaces can only be manipulated by administrators & the
owner of a workspace. You require a Developer license to create a
repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor
license. I have loaded the source code into projects in the RTC client
by loading the components from a repository workspace - actually its
the continuous build repository workspace for the project area. So the
repository workspace is flowed to from the (only) stream.
However, when there are changes in the repository workspace because
they flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace to
get notified? (I can't because as a contributor I can't create a
repository workspace).
Thanks,
Jeremy
I agree with your user story ... however, RTC does not have this support
yet.
Thanks
JohnC
Jeremy Hughes wrote:
yet.
Thanks
JohnC
Jeremy Hughes wrote:
As contributor, I don't feel the need to create a repository workspace.
There is already one I can load the source from. Does 'being notified
(blue incoming arrows) and receiving updates from a repository workspace
to my local eclipse workspace' count as manipulating the workspace? If
so then I can see why I'm not able to achieve what I'm trying. I'm not
looking to alter source code, just get notified when there are changes.
I think I have a valid user story here though: A user with a contributor
license wishes to extract the source, compile it in eclipse, then
construct a patch for a problem he's having and post it to a work item
for a user with a developer license to try out and potentially check-in.
While the contributor is doing this, the code in the stream flowing into
the repository workspace changes, and the contributor should be notified
of this with blue incoming arrows (which from my experience isn't
happening) so that he can adjust his patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
Repository workspaces can only be manipulated by administrators & the
owner of a workspace. You require a Developer license to create a
repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor
license. I have loaded the source code into projects in the RTC
client by loading the components from a repository workspace -
actually its the continuous build repository workspace for the
project area. So the repository workspace is flowed to from the
(only) stream.
However, when there are changes in the repository workspace because
they flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace to
get notified? (I can't because as a contributor I can't create a
repository workspace).
Thanks,
Jeremy
OK. Should I open a work item for it? Would there be interest in
implementing it?
Thanks,
Jeremy
On 17/10/2008 01:01, John Camelon wrote:
implementing it?
Thanks,
Jeremy
On 17/10/2008 01:01, John Camelon wrote:
I agree with your user story ... however, RTC does not have this support
yet.
Thanks
JohnC
Jeremy Hughes wrote:
As contributor, I don't feel the need to create a repository
workspace. There is already one I can load the source from. Does
'being notified (blue incoming arrows) and receiving updates from a
repository workspace to my local eclipse workspace' count as
manipulating the workspace? If so then I can see why I'm not able to
achieve what I'm trying. I'm not looking to alter source code, just
get notified when there are changes.
I think I have a valid user story here though: A user with a
contributor license wishes to extract the source, compile it in
eclipse, then construct a patch for a problem he's having and post it
to a work item for a user with a developer license to try out and
potentially check-in. While the contributor is doing this, the code in
the stream flowing into the repository workspace changes, and the
contributor should be notified of this with blue incoming arrows
(which from my experience isn't happening) so that he can adjust his
patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
Repository workspaces can only be manipulated by administrators & the
owner of a workspace. You require a Developer license to create a
repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor
license. I have loaded the source code into projects in the RTC
client by loading the components from a repository workspace -
actually its the continuous build repository workspace for the
project area. So the repository workspace is flowed to from the
(only) stream.
However, when there are changes in the repository workspace because
they flowed from the stream, I'm not getting any indication that the
repository workspace has changes that I should bring into my RTC
client.
What am I doing wrong? Do I have to own the repository workspace to
get notified? (I can't because as a contributor I can't create a
repository workspace).
Thanks,
Jeremy
Sure, open a work item. I cannot guarantee that it will be addressed
in the next release though.
Thanks
JohnC
Jeremy Hughes wrote:
in the next release though.
Thanks
JohnC
Jeremy Hughes wrote:
OK. Should I open a work item for it? Would there be interest in
implementing it?
Thanks,
Jeremy
On 17/10/2008 01:01, John Camelon wrote:
I agree with your user story ... however, RTC does not have this
support yet.
Thanks
JohnC
Jeremy Hughes wrote:
As contributor, I don't feel the need to create a repository
workspace. There is already one I can load the source from. Does
'being notified (blue incoming arrows) and receiving updates from a
repository workspace to my local eclipse workspace' count as
manipulating the workspace? If so then I can see why I'm not able to
achieve what I'm trying. I'm not looking to alter source code, just
get notified when there are changes.
I think I have a valid user story here though: A user with a
contributor license wishes to extract the source, compile it in
eclipse, then construct a patch for a problem he's having and post it
to a work item for a user with a developer license to try out and
potentially check-in. While the contributor is doing this, the code
in the stream flowing into the repository workspace changes, and the
contributor should be notified of this with blue incoming arrows
(which from my experience isn't happening) so that he can adjust his
patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
Repository workspaces can only be manipulated by administrators &
the owner of a workspace. You require a Developer license to create
a repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor
license. I have loaded the source code into projects in the RTC
client by loading the components from a repository workspace -
actually its the continuous build repository workspace for the
project area. So the repository workspace is flowed to from the
(only) stream.
However, when there are changes in the repository workspace because
they flowed from the stream, I'm not getting any indication that
the repository workspace has changes that I should bring into my
RTC client.
What am I doing wrong? Do I have to own the repository workspace to
get notified? (I can't because as a contributor I can't create a
repository workspace).
Thanks,
Jeremy
Thanks. I created:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=63135
Cheers,
Jeremy
On 20/10/2008 21:05, John Camelon wrote:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=63135
Cheers,
Jeremy
On 20/10/2008 21:05, John Camelon wrote:
Sure, open a work item. I cannot guarantee that it will be addressed
in the next release though.
Thanks
JohnC
Jeremy Hughes wrote:
OK. Should I open a work item for it? Would there be interest in
implementing it?
Thanks,
Jeremy
On 17/10/2008 01:01, John Camelon wrote:
I agree with your user story ... however, RTC does not have this
support yet.
Thanks
JohnC
Jeremy Hughes wrote:
As contributor, I don't feel the need to create a repository
workspace. There is already one I can load the source from. Does
'being notified (blue incoming arrows) and receiving updates from a
repository workspace to my local eclipse workspace' count as
manipulating the workspace? If so then I can see why I'm not able to
achieve what I'm trying. I'm not looking to alter source code, just
get notified when there are changes.
I think I have a valid user story here though: A user with a
contributor license wishes to extract the source, compile it in
eclipse, then construct a patch for a problem he's having and post
it to a work item for a user with a developer license to try out and
potentially check-in. While the contributor is doing this, the code
in the stream flowing into the repository workspace changes, and the
contributor should be notified of this with blue incoming arrows
(which from my experience isn't happening) so that he can adjust his
patch accordingly before posting it.
Thanks,
Jeremy
On 15/10/2008 21:15, John Camelon wrote:
Repository workspaces can only be manipulated by administrators &
the owner of a workspace. You require a Developer license to
create a repository workspace.
Sorry
JohnC
SCM Server
Jeremy Hughes wrote:
Hi,
I am in the JazzUsers group of a repository with a contributor
license. I have loaded the source code into projects in the RTC
client by loading the components from a repository workspace -
actually its the continuous build repository workspace for the
project area. So the repository workspace is flowed to from the
(only) stream.
However, when there are changes in the repository workspace
because they flowed from the stream, I'm not getting any
indication that the repository workspace has changes that I should
bring into my RTC client.
What am I doing wrong? Do I have to own the repository workspace
to get notified? (I can't because as a contributor I can't create
a repository workspace).
Thanks,
Jeremy