Book a Demo

Author Topic: Problem to check-in to PTC  (Read 22498 times)

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Problem to check-in to PTC
« Reply #15 on: May 24, 2017, 06:31:03 am »
You would need to do that with a script. The checkout is available via ProjectInterface.ExportPackageXMI. Once the file is on disc you can pipe it through the script and then check it into your dreaded PTC. Afterwards you might need to call Repository.VersionControlResynchPkgStatuses. Defintely a place for some experiments.

q.

Oliver F.

  • EA User
  • **
  • Posts: 573
  • Karma: +2/-1
  • Aren´t we all in the model business ?
    • View Profile
    • Karl Storz homepage
Re: Problem to check-in to PTC
« Reply #16 on: May 24, 2017, 08:32:58 pm »
Somehow I failed to get the problem as a whole.

It would be great if you could describe the workflow between PTC and EA which you are attempting to set up.
I am having a similar need here and it would be helpful to see how people are attempting to solve that issue and to be able to help you with yours.

Thanks in advance.

Best regards,

Oliver

ngong

  • EA User
  • **
  • Posts: 275
  • Karma: +2/-2
    • View Profile
Re: Problem to check-in to PTC
« Reply #17 on: May 25, 2017, 09:06:06 pm »
thank you, qwerty - a colleague of mine is fluent in scripting EA, will ask him.

@Oliver, PTC Source Integrity has an unresolved issue:

https://www.ptcusercommunity.com/thread/40277
and PTC refuses to change that in a timely manner.

I know of two tools that have problems with that one: EA and VectorCAST.
In general all tools using the XML specification to the extend having lines longer than 16k characters without a new-line.
With source files PTC reads lines, not characters, and cannot accept lines longer than 16k.

EA exports xml files as configurable items for version control. Sometimes they come with lines longer than 16k. I have seen ~150k, but that model is far from ready. I expect even longer lines.
One work-around would be to check-in the xml files as binaries into PTC. This has a bad influence on size and performance of the PTC database for very big files. Exporting an EA package could grow too big.

The other solution that I am taking is, to break long lines by inserting newline characters at places where not only XML but also EA accepts them. A good place is at sub-strings "},{" after the comma. I am inserting as few as possible.

In one post above I am detailing the steps to be taken manually when checking such packages into PTC.
Now I am going to automate this in order to hide this inconvenience from users in other teams.

Best Regards

Rolf
Rolf

Oliver F.

  • EA User
  • **
  • Posts: 573
  • Karma: +2/-1
  • Aren´t we all in the model business ?
    • View Profile
    • Karl Storz homepage
Re: Problem to check-in to PTC
« Reply #18 on: May 26, 2017, 05:32:16 pm »
Hi Rolf,
correct me if I am wrong but my impression was that you managed to exchange/sync information between EA and PTC Integrity, eg. requirements, a use case which I am also looking after.
So any hints or pointers regarding the workflow you have set up here would be appreciated. Sorry for the OT.

Thanks,

Oliver