Last night (GMT - UK) my dev team committed into their master Github repository a current version of a build and then expected Bamboo to run tests from that current version (within 5 minutes of the commit).
The testing would have taken a couple of hours and it was kicked off. But for some reason it was looking at the previous commit of the build, rather than the latest commit.
My question is, once a Github commit (as above) has taken place how long can we expect to wait for Bamboo to see the newly committed version of data? Is there a way to force bamboo to always look at the most current commit?
The commit completed and the devs had confirmation of that.
Any help is much appreciated.
Just to add something here. This eventually started working i.e Bamboo eventually started running tests from the latest commit, but this cost the my dev team around 4 hours of delay to a major release.
This makes me think there is a time delay before the latest commit is looked at.
I'd look to see if you are you polling or using some other way for commit notifications ? If you are polling, I'd expect things within the time period specified. If you are using some other means of delays (like maybe github was having a backlog/slow processing for notifications?)
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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