Currently jobs to build and deploy applications in Altinn Studio are set in the same queue as the jobs deploying Altinn Studio with terraform. We are using a free tier in DevOps that results in only one job being able to run at a time.
An important selling point for Altinn Studio is that it is quick to build and deploy your application. So these types of jobs should be seperated into isolated queues and run on designated agens.
Screenshots
Screenshots or links to Figma (make sure your sketch is public)
Considerations
Describe input (beyond tasks) on how the user story should be solved can be put here.
Acceptance criteria
Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)
Specification tasks
[ ] Development tasks are defined
[ ] Test design / decide test need
Development tasks
Add tasks here
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)
Description
Currently jobs to build and deploy applications in Altinn Studio are set in the same queue as the jobs deploying Altinn Studio with terraform. We are using a free tier in DevOps that results in only one job being able to run at a time.
An important selling point for Altinn Studio is that it is quick to build and deploy your application. So these types of jobs should be seperated into isolated queues and run on designated agens.
Screenshots
Considerations
Acceptance criteria
Specification tasks
Development tasks
Definition of done
Verify that this issue meets DoD (Only for project members) before closing.