Hosting and infrastructure
GitHub Actions in Digital SIDECUBE Projects
GitHub Actions helps to automate the buildings, tests, deploys and checks before the changes reach live.
Match
When we use GitHub Actions
The technology is chosen after we understand the objective, the rhythm of the team, the level of administration and how much the project needs to increase.
- CI/CDWe link the changes in the verification code and publication steps defined for the project.
- Automatic checksWe carry out repeatable controls on important functions and rules, with results that can be pursued.
- Controlled DeplayWe publish an identified and verified version, keeping the evidence and the return procedure.
- Technical teamsWe document contracts and operations so that developers can work on the same basis.
Uses
What can we build with GitHub Actions
We only use technology where it helps the project to be faster, easier to manage or safer to expand.
Deliverables
What goes into implementation
Accurate delivery depends on the project, but we keep every documented, tested and prepared implementation for maintenance.
- Workflow CI
- Built / test jobs
- Configured Secrets
- Deploy pipeline
- Process documentation
Connected services
GitHub Actions usually appears in these projects
Choose the service that best describes your need, then determine if this technology is the right choice.
Hosting on our own infrastructureSee serviceCustom softwareSee serviceWeb, mobile and SaaS applicationsSee service
Hosting and maintenance
Hosting in our own data centre and complete management for websites, online stores and applications.
Software solutions
Applications, dashboards and integrations that gather important processes into a more manageable system.
Applications
Web and mobile applications, SaaS platforms and portals connected to company data and processes.
Recommended pages
Services, technologies and guides related to this technology and its use in projects.
Specialised services
Close technologies
Industries
Guides
Frequently Asked Questions
Before you choose technology
Uses, integration and costs for GitHub Actions.
01 / Match
When that choice makes sense
What projects do you consider GitHub Actions for?
Suitable situations: CI / CD; Automatic checks; Controlled Deploy; Technical teams. The choice shall be confirmed after analysis of existing requirements, team and solutions.
What uses do you propose for GitHub Actions?
Relevant examples are: Build Automatically; Tests; Deploy Staging; Audit prior to launch. We determine what serves your objective and what would add complexity without a clear benefit.
02 / Implementation
Integration and deliverables
Can the solution be integrated into an existing project?
We are checking the application, fields, data and services that depend on the current infrastructure. The plan shall include validation prior to activation and a return option in case of a problem.
What could include implementation?
For GitHub Actions, we can define in the offer: Workflow CI; Jobs build / test; Secrets configured; Deploy pipeline; Process Documentation. We confirm the deliverables after verification of compatibility and available access.
03 / Operation
Verification and costs
How do you check that implementation works?
We are checking publication, access, critical services and relevant alerts. For infrastructure changes, the backups and restoration possibility are checked separately from the simple availability of the page.
What costs should be foreseen in the long term?
We calculate resources, traffic, storage, backups and additional services. The initial configuration and administration are distinct from the infrastructure provider's invoice.