snapshot deliver error

Turns out we had 3 locks on our stream, the developer holding the locks removed them and the baseline deliveries are now working again.

For potential readers below are 2 jazz workitems.

Duplicate:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=164671

Primary:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=101094

So, as a test, I duplicated my stream, change my flow target to that new stream and baselines deliver just fine to the duplicated stream.

lets follow up in the work item, it seems as though something has gone wrong with the configuration of the original stream.

thanks,

Ah, so how do people get out of this state, when moving to 3.0 is not an option?

So, as a test, I duplicated my stream, change my flow target to that new stream and baselines deliver just fine to the duplicated stream.

lets follow up in the work item, it seems as though something has gone wrong with the configuration of the original stream.

thanks,

So, as a test, I duplicated my stream, change my flow target to that new stream and baselines deliver just fine to the duplicated stream.

Looks like the stream has the problem. I get the same problem using my new build workspace.

Try showing the baselines of the component in the build workspace. Is the baseline you're trying to deliver in that list?

Yes the baseline is in the workspace component.

Looks like the stream has the problem. I get the same problem using my new build workspace.

Try showing the baselines of the component in the build workspace. Is the baseline you're trying to deliver in that list?

Looks like the stream has the problem. I get the same problem using my new build workspace.

You don't have to deliver those baselines. Maybe someone more familiar with how builds work can chime in on the errors that could occur if you load the build workspace and use it for other tasks. My guess is the build's component is completely replaced with the new baseline. It doesn't have the old baseline and your client view is out of sync. If you refresh, you might see that the baseline is gone or replaced with the build's new baseline.

I wouldn't worry about not being able to deliver it. Your stream still has the change sets that you've delivered. Did you create a new workspace for the build or a new workspace for you to use for development? If you're using the workspace that was used for the build then you can replace the component with the latest from stream (you may want to suspend any outgoing change sets). Or you could create a new development workspace for yourself. It's ok for users to create and use more than one workspace.

Are you using the same workspace for your own development and the build? I would not recommend reusing a workspace like that.

How are the baselines from the build getting to the workspace you have loaded in Pending Changes?

Yes, I use the same id. been doing that for well over a year now. We have discussed creating a new user to handle builds. The baselines come to the pending changes on completion of the build. I am using the Jazz Build Engine. I don't take any action other then attempting to deliever the baseline. I am actually not sure what the net affect is of delivering the baselines, just been my practice.I don't know what can happen if you use the build workspace for non-build related tasks since the build will alter that workspace. It would be best to create a workspace just for the build.

Baselines are useful indicators for notable points in the component's history. It allows users to load configurations at those specific points. The build automatically creates these baselines if there are change sets after the last baseline. I would recommend creating a baseline before delivering to the stream that is used in the build. Then you wouldn't have to deliver the baselines back to the stream.

If you're a small team and only use one stream, you don't have to deliver the baselines created from the build. Then you may create baselines whenever you think is a notable moment (i.e. release/milestone/test build).

Baselines are good and can help users roll back to a certain point in time. It also speeds up comparing workspaces/streams if both have a common baseline (everything after the most recent common baseline would have any differences).

This makes sense, so I've created a new repository workspace, but now what do I do with these baselines that I cannot deliver? I would not call them milestones of any kind and as long as they dont impact the stream I dont really care what happens to them, but my deliveries stopped working last friday, so I'd like to get this working again for comfort on my part. My development system gets built every hour, should I disable the creation of a baseline for every hour? Thanks for you responses.