deliver vs check-in
I have a question about the difference between deliver and check-in.
The deliver will deliver my code in my work repository to the stream, and share to others. What does the check-in means? I guess it is the same as deliver? |
8 answers
On Wed, 07 May 2008 13:27:59 +0000, czhuang wrote:
What does the check-in means? I guess it is the same as deliver? Check-in will store changes you made on your local filesystem to your private workspace on the server. Deliver will deliver changesets from your private workspace to a stream which is a mechanism for sharing those changesets with your team. - Dmitry |
|
On Wed, 07 May 2008 16:56:30 +0200, Nando wrote:
As far as i know, automatic check-in is set by default in Team Concert In M6 yes, but not in later versions. If you have Auto-checkin on then you don't need to worry about checking in. - Dmitry |
So when I save a file (via cntr-s) its not automatically saved to my workspace on the jazz server?
|
parrym <parrym> ha scritto:
So when I save a file (via cntr-s) its not automatically saved to my As far as i know, automatic check-in is set by default in Team Concert (see window->preferences->team->jazz source control). -- Nando Apostolo della Prova |
|
Dmitry Karasik <dkarasik> ha scritto:
On Wed, 07 May 2008 16:56:30 +0200, Nando wrote: Sorry for the bad information i gave :) If you have Auto-checkin on then you don't need to worry about checking Of course. -- Nando Apostolo della Prova |
So when I save a file (via cntr-s) its not automatically saved to my workspace on the jazz server? If you have automatic check-ins enabled, then saving a file locally will also check-in this file to your private repository workspace. If you do not have automatic check-ins enabled, then saving a file locally will result in the file being marked as "unresolved" in your Pending Changes view; you can check-in files to an existing or new change-set via a context-menu action on the unresolved Pending Changes file(s). |
I have not raised a bug as I still feel there might be something wrong done, but steps I followed seemed to be perfect.
I modified the process behavior for Source Control "Require Work Item Approval " and added couple of reviewers and approver for a particular role. After getting the required approvals and reviews ok, When I try to deliver the local artifacts to the stream - it still gives me the error in the Team advisor saying " The associated work item (<no>) does not meet the specified approval requirements " The strange part is if I remove the pre-condition on server and apply the same at client it works without any issues. I am at loss as to what is the correct way to do ? if server is correct - what could be possibly wrong Thanks in advance Jagadish |
|
Sorry ...
Instead of raising a new one .. I used this post .. my apologies I have not raised a bug as I still feel there might be something wrong done, but steps I followed seemed to be perfect. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.