Setup continuous deployment for studio

[lorang92]

Description

As discussed in Tech Forum there is a wish to move from the current weekly deploy schedule to a continuous deployment schedule for the various components. A great way to experiment and gain experience with this approach is to try this out, and altinn-studio is considered the best place to start.

Considerations

• How should deploys to prod be released? A thought is that a PR merge deploys to dev as is, and when this feature has been tested the tester can approve a further deploy to prod. This way we can reduce the time from merge to prod from worst case 1 week, to potentially hours.
• Are there any restrictions in our SLA agreement that needs to be accounted for? Talk with @lvbachmann

Acceptance criteria

• Continuous deployment for altinn-studio is enabled
• Deploy to prod is only done after the requirements we land on is accepted

Specification tasks

• [ ] Identify requirements that need to be fulfilled before deploying to prod

Development tasks

• [ ] Update studio release pipeline

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

• [ ] Documentation is updated (if relevant)
  • [ ] Technical documentation (docs.altinn.studio)
  • [ ] User documentation (altinn.github.io/docs)
• [ ] QA
• [ ] Manual test is complete (if relevant)
• [ ] Automated test is implemented (if relevant)
• [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

[lvbachmann]

The SLA only restricts us in two cases:

• Breaking changes where the app owners needs to do something
• When downtime or severely lower performance will occur during deploy