Delta only validation CI jobs
Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .
The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.
Joe Wildey commented
Could GearSet look at the artifacts included in the Pull Request driving the CI validation and automatically adjust the metadata filter to only include those items?
We have thought about this request and have responded in the documentation (https://docs.gearset.com/en/articles/5069914-delta-ci?location=conversation#h_c386626adc) as follows:
Delta CI jobs deploy everything in the source git branch that has changed since the most recent successful deployment from that branch.
The difference displayed in the run is between
- the new metadata items in the last commit on the source branch, and
- the previous commit on the source branch, when the most recent successful deployment occurred to the target organization
This is the problem with validation only CI jobs: as the validation CI job does not deploy metadata to the target, there is no previous commit which can be used as a substitute to the most recent successful deployment. As a result, we can't generate a delta CI job run in the same way as we can for deployment jobs.
We have considered several options, but we have not identified yet a suitable alternative to compare against. If you can think of any possible substitute. We'd love to hear from you.
Cole Prato commented
This would be really awesome!
Ruslan Kurchenko commented
Please, consider this one!