We are making changes to the way how Pipelines executes Git clone at the start of a step. Specifically, we are optimising the cloning to benefit from packfile caching. Not only will this positively impact Bitbucket overall performance, it should also reduce the clone time in Pipelines and thus makes your step executions faster.
Although this change will be mostly transparent, we have identified some scenarios that are not entirely compatible without making changes.
Specifically if you are making changes to Git annotated tags in a Pipelines step, and depend on these changes in subsequent steps.
For example, if you have a pipeline which creates and pushes a tag in a step, and in a subsequent step tries to resolve the tag. In this scenario the newly created tag would not be part of the cached clone.
To avoid these problems, we recommend that you update your steps that rely on changed tags to perform a full git clone.
- step:
clone:
depth: full
Alternatively, if you have a big repository and doing a full clone will take too long, you can just fetch the tags by executing this command as your first script command: git fetch --tags
We plan to start gradually roll out these changes in the week of August 9, so we recommend to update your pipelines ahead of time.
0 comments