How to manage Fetch app source step?

[amakarov-ta]

He guys,

I found a difference between push and pull request triggers, push trigger executes a fetch source from the branch, but the PR trigger executes fetch sources from both branches and makes a difference between branches to present a report in the console output, for my target GitHub repository the last one takes a lot of time, sometimes it can be 10 minutes, sometimes more, yesterday I even saw that job was failed because of timeout. The push trigger works as well.
So, do we have any options on how to make the Fetch source job for PR equal to what we have for the Push job, or maybe you have any ideas why the Fetch code can take 1h?

Technical:
it's GitHub integration
The GitHub repo is huge with a lot of branches and tags

Regards,
Anton

[dtrdic]

Hey @amakarov-ta, yes correct the fetch source job for a pull request trigger typically takes longer than a push trigger because it fetches source code from both the base branch and the head branch of the PR.
As you mentioned, your GitHub repository is huge with a lot of branches and tags. If possible, you could consider removing any unnecessary branches and tags to reduce the amount of data that needs to be fetched?

[dtrdic]

You could try using a shallow clone to fetch only the most recent commits of the base and head branches. This can significantly reduce the amount of data that needs to be fetched and improve the performance

[dtrdic]

This discussion is being closed due to no activity in the last 14 days. You can reopen the discussion at any time if needed.