on 11-14-2013 7:49 PM
Hello Suhaas,
the DCs have a relationship to other DCs and somehow it results into a construct like a Tree. Your Own DCs are basically on the lowest level as they inherit their "code" from the DCs.
There are three main possibilities
Now the question. As we have this tree like relationship model, did you follow up all the paths to the DC, which is broken but has actually green lights on all paranet DCs?
I guess it is still the same project since you started to become active in this community, hence it was probably working once and just recently became broken? If your project does build locally, then i would check with all involved developers if their activities are all correctly checked in and activated. Once a activity is activated in, the CBS will try to build and turns the green lights to red if it fails. Which also often happens is (if you forgot to logon to the SLD/NWDI first), that you create new files locally, but they never were added to a activatiy. Maybe you have to check, if this is the case. If you have a lots of files in folders, then use the Team => "Add all..." on the root folder of your DC. This will locate those files. As you have to do by DC and I have not figured out a faster way, you might need some time to do it. In this case you are faster finding the actual source of the broken DC in the CBS and narrow down the DCs you have to check locally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Suhaas
Which error you have on Build Service logs?
Cheers,
D.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.