Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
I had the opposite today. The status page said the website was down, yet I saw no issues.
@ganey they seem to always blame it on pipelines and webhooks. I don't care about pipelines because I don't have any and I can deal with bitbucket not triggering my jenkins jobs for every commit because they can be triggered manually but I do care about "pipelines and webhooks" stopping us from pushing any code.
ganey1002y@cmarshall10450 yeah they did maintenance yesterday on something and the usual pipelines and webhooks broke.
We use pipelines on merges to run some checks then issue a deployment on aws.
There's a variety of ways to do it by possibly one of the following:
- triggering something on codecommit.
- raising an ECS task from pipelines to run a deployment script
- using SSM documents to run a deployment task on an EC2
Obviously if doing any of these, only use AWS keys with limited permissions on pipelines such as issue SSM or only codecommit access.
Personally, I wouldn't rely on bitbucket pipelines for actually deploying production code whether it's a whole lambda function or something simple like and S3 sync. Pipelines just has too many issues.
Trithon10752yAutocorrect: did you mean sh!t bucket?