Welcome to the Jazz Community Forum
Remove Invalid Baseline from Pending Changes View

Hi All,
I'm using RTC 2 source control + automated builds. In my pending changes view in the outgoing folder I have a baseline to deliver. However, when I do a right click -> Deliver the following error message occurs.
Problem
An error occurred during "Deliver".
Can not update an item that has already been deleted from the configuration. config id = ; item id = ; item name = 'null'
http://img709.imageshack.us/img709/5104/rtcissuebaseline1.png
Uploaded with ImageShack.us
I assume this baseline was created when I started with building up my automated builds. At that time I sometimes removed failed builds.
So how can I remove that baseline from my pending changes?
Additionally, I don't understand when a baseline is created during automated builds. Is it only when changes where delivered to a stream?
Regards,
arens
I'm using RTC 2 source control + automated builds. In my pending changes view in the outgoing folder I have a baseline to deliver. However, when I do a right click -> Deliver the following error message occurs.
Problem
An error occurred during "Deliver".
Can not update an item that has already been deleted from the configuration. config id = ; item id = ; item name = 'null'
Uploaded with ImageShack.us
I assume this baseline was created when I started with building up my automated builds. At that time I sometimes removed failed builds.
So how can I remove that baseline from my pending changes?
Additionally, I don't understand when a baseline is created during automated builds. Is it only when changes where delivered to a stream?
Regards,
arens
One answer

It sounds like you've loaded the build workspace and have been using it for tasks not related to the automated build. http://jazz.net/forums/viewtopic.php?t=16827
It seems to have resulted in putting you in a bad state, which has a workaround. It is described in this work item: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/101094
It seems to have resulted in putting you in a bad state, which has a workaround. It is described in this work item: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/101094