Sorry for the wording of the question, I couldn't think of another way to put it.
I recently created a repository hook for my company's bitbucket server and when it was enabled on the repo, it blew up the server because there are so many commits on the project. Is there a way to make the commits not work retroactively for commits? I was looking for a way to not apply the hook to commits that have been pushed more than 10 minutes ago, but it doesn't look like the Java API keeps track of the time and date a push was made.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot