Development

Find code on xunit tests here »

Principles We use scaled trunk-based development. This ensures the codebase is always releasable on demand and helps to make Continuous Delivery a reality. Code is checked in using short lived feature branches and pull requests (PR). Review is always done by someone else than the author Scaled Trunk Based Development Read more about scaled trunk based development here. A source-control branching model, where developers collaborate on code in a single branch called “trunk” (master), resist any pressure to create other long-lived development branches by employing documented techniques. »

What are flight rules? Flight rules is originally a compendium of step-by-step manuals, what to do when X occurs and why. Essentially, they are extremely detailed, scenario-specific standard operating procedures. Loadbalancer is responding with HTTP Error 502 - bad gateway This occurs when the loadbalancer could not find any of the services in it’s configuration. Can be triggerd by these issues: Some of the kubernetes services are not existing Some of the kubernetes pods are not existing Kubernetes mapping between deployments and services are incorrect. »

Gitea is used for version control of the apps developed in Altinn Studio. Customize The documentation on how to customize Gitea can be found here. Templates The user interface of Gitea can be customized to match your application needs. You can copy the templates from Gitea’s GitHub. For example the default login page looks like this Default login It’s customized to look like this Customized login Follow these steps to change any user interface of Gitea. »

This should provide all basic information needed to get started with development on the altinn-studio repo. It should alto contain the information needed to make sure all developers write their code in a consistent way. The guidelines should work as reference material, but it should also be possible to read through the whole development handbook in a logical order so that new developers quickly get up and running. The development handbook is a dynamic material and everybody should feel free to extend or correct articles when needed. »

Moving messages between queues During operations we sometimes need to move messages between queues. The most common scenario is wanting to re-process elements that have ended in the poison queue after too many failed attempts. Prerequisites Azure Storage Explorer An Azure AD account with write-permissions for the related storage account How to Open Storage Explorer. If you are working towards a test or production environment you must Sign into Azure under the Account Management tab select the storage account you want to work with Move to the Explorer tab and identify the source queue in the left hand menu You should now see the messages in the queue in the explorer. »

Altinn.studio is under heavy development and errors are most likely to come with it. If the error is not covered here, please submit a bug report. Check out Flight Rules. Check out known issues: Altinn Studio Front-end App libraries »