Changes to composer.json are ignored, which means our pipeline builds are now targeting some incorrect package versions.
We're not using the new caching features, but it looks like the composer file is getting cached anyway.
Is there anyway to force pipelines to detect changes to the composer file?
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
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