Firebase & CI/CD DevOps Support
Budget: $50 – $100 AUD
I run a production-level application that sits on Google Firebase and App Engine, with the Atlassian tool-chain (Bitbucket repos and Jira boards) guiding day-to-day work. The immediate need is ad-hoc, ongoing support: keeping builds green, deployments smooth, and the infrastructure ready for the next feature push.
The current Bitbucket-based CI/CD pipeline exists . I need the pipeline tightened up, test stages unified, and roll-backs made reliable so releases remain one-click. While you are inside the stack, small optimisations to Firebase rules, App Engine configs, or Jira workflow integrations will crop up; folding those into regular support requests is part of the brief.
In practice that means:
• Troubleshooting and refining the existing CI/CD workflow (Bitbucket Pipelines, Firebase CLI, gcloud).
• Monitoring live environments, diagnosing build-to-prod issues, and patching configs on an as-needed basis.
• Proposing and executing upgrades that future-proof the Google application framework.
• Documenting every change so that any team member can reproduce or extend your work.
Acceptance is simple: each change must ship through the improved pipeline without manual intervention, be logged in Jira, and leave clear markdown documentation beside the code.
If you thrive on iterative improvement rather than one-off handovers, this should fit perfectly.
The current Bitbucket-based CI/CD pipeline exists . I need the pipeline tightened up, test stages unified, and roll-backs made reliable so releases remain one-click. While you are inside the stack, small optimisations to Firebase rules, App Engine configs, or Jira workflow integrations will crop up; folding those into regular support requests is part of the brief.
In practice that means:
• Troubleshooting and refining the existing CI/CD workflow (Bitbucket Pipelines, Firebase CLI, gcloud).
• Monitoring live environments, diagnosing build-to-prod issues, and patching configs on an as-needed basis.
• Proposing and executing upgrades that future-proof the Google application framework.
• Documenting every change so that any team member can reproduce or extend your work.
Acceptance is simple: each change must ship through the improved pipeline without manual intervention, be logged in Jira, and leave clear markdown documentation beside the code.
If you thrive on iterative improvement rather than one-off handovers, this should fit perfectly.