Motivation
In the current version of the build process, the tpd to targetplatform is not automated anymore.
We could add this directly in the jenkinsfile process as it was done in the past , but in that case we lose control of when a new version of a component is introduced.
Proposed Solution
I propose to add a cron that regularly tries to compute the targetplatform from the tpd and is it detects a change, then create a PR with the changes.
This would offer both automation and traceability.
Proposed Implementation
I propose that this action should be implemented as a scheduled github action (daily or weekly basis should be enough)
related issues: #233 #262
related PRs : #259 #263 #293
Motivation
In the current version of the build process, the tpd to targetplatform is not automated anymore.
We could add this directly in the jenkinsfile process as it was done in the past , but in that case we lose control of when a new version of a component is introduced.
Proposed Solution
I propose to add a cron that regularly tries to compute the targetplatform from the tpd and is it detects a change, then create a PR with the changes.
This would offer both automation and traceability.
Proposed Implementation
I propose that this action should be implemented as a scheduled github action (daily or weekly basis should be enough)
related issues: #233 #262
related PRs : #259 #263 #293