Projects get out of synch after each build requests
![]()
Amit Kumar (19●5●14)
| asked Jul 03 '16, 3:36 a.m.
edited Jul 07 '16, 8:33 a.m. by David Lafreniere (4.8k●7) Hello Team
Please help me with one of issue which i have observed in RTC. In Automation i need to schedule the builds, and now for build request we do not want any manual intervention.
Can anyone please look into and update me how it can be resolve. ?
FYI, we updates files outside of RTC (It's our requirement) and i have checked these options also. But it did not work
Will appreciate if any one can help me on this!
|
One answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jul 05 '16, 2:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A repository workspace can get out of sync if it is loaded multiple times on disk and someone does SCM changes to one instance. In this case all other instances will be out of sync. So avoid this.
Usually a build does not make any changes to files under SCM. So a build usually only reads the data and then runs on it. So even if you have the same repository workspace loaded multiple times you can't get them out of sync. If a personal build is run, the build system uses the users repository workspace of the user. Because of this it only has read access and can not check anything in. So I don't see how your workspaces can get out of sync if you set this up reasonably clean with a technical build user. Comments Ralph, Thanks for this explanation
"Out of sync" has special meanings in the RTC context. What you described is sometimes the build source lags behind the latest commit. You need to explain how you set this up (streams, workspaces and etc) for us to understand whether this is expected or not.
In addition I still have a hard time understanding the description. The load should be an atomic operation it picks the changes available to accept and then loads the data to disc.
Source doesn't lag behind. what i am trying to say is if i automate the builds , then Build will get success every time and source will also get updated commit.
We don't have commit in RTC.
ok,
Specify the load destination directory. This is the directory on the build machine where workspace files will be loaded. This value is also typically used on other pages in the definition to reference files under source control. You can specify an absolute path on the build machine, or a path relative to the current directory of the build engine process. Properties can be referenced using ${propertyName}.
showing 5 of 8
show 3 more comments
|
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.