Hi @Hubert Heijkers,
A few details are in order :) :
Step 4: GitPull from the PA instance => Right-click > Update the model from the Repository
Step 5: once the source branch has been selected (main), PA performs an analysis to detect the files to be [Copy, Update, Create, Skip], by "deploying", launch the actual delivery of objects physically to the instance (GitPull)
Then, the step 5 failed with a message related to the Chore containing a sub-process with a Chore having a sub-process with a missing parameter
Regards,
------------------------------
Bilal KACEL
------------------------------
Original Message:
Sent: Mon January 22, 2024 03:14 AM
From: Hubert Heijkers
Subject: [GitHub] Loss of }git.ctx file content
Hi Bilal,
Just so it is clear to me, in step 4 where you update the instance from MAIN branch, does that operation succeed? I guess I'm confused as to what you mean with "At deployment time" in step 5. Is that still part of the GitPull of the update or is that when you execute the Chore AFTER the update?
------------------------------
Hubert Heijkers
STSM, Program Director TM1 Functional Database Technology and OData Evangelist
Original Message:
Sent: Fri January 19, 2024 05:17 AM
From: Bilal KACEL
Subject: [GitHub] Loss of }git.ctx file content
Hello team,
I noticed an anomaly today between Planning Analytics and GitHub (Enterprise).
Here are the actions:
1. Update a Chore (DEV environment)
2. Push Chore to GitHub (on DEV branch)
3. Merge contents of DEV branch into MAIN branch
4. From PA instance: update instance from MAIN branch
5. At deployment time, PA detects that a parameter is missing in a sub-process called in the Chore, which is true.
Result:
- Error generated at deployment time
- However, I've noticed that the }git.ctx file under the Data directory has been emptied, contains only the coded lines but no instance objects.
Symptom:
- The correction has been made on the end-to-end task, from the corresponding DEV, GitHub and branches instance.
- The problem is that the PA pre-deployment analysis detected that all objects were to be updated (status: Update). As a result, it redeployed all objects with a new date.
Would you have an idea/how to prevent the }git.ctx file from not being modified if there is a conflict when deploying from GitHub?
Thanks a lot
Have a nice day
------------------------------
Bilal KACEL
Tech' Lead
IBM
------------------------------