Test Servers

Testserver	Connected Systems	Deployment via	Access	Admin-Accounts
artemis-staging-localci.artemis.cit.tum.de	Integrated Code Lifecycle LDAP LTI Apollon Iris MySQL	Bamboo	TUMonline account Test accounts	On Demand
https://artemis-test0.artemis.in.tum.de/	ICL (migrated) LDAP Sending E-Mails possible MySQL	Bamboo	TUMonline account
https://artemis-test1.artemis.cit.tum.de	Integrated Code Lifecycle MySQL 3 Nodes Iris LTI	GitHub	TUMonline account Test accounts	On Demand
https://artemis-test2.artemis.cit.tum.de	Integrated Code Lifecycle MySQL 1 Node LTI	GitHub	TUMonline account Test accounts	On Demand
https://artemis-test3.artemis.cit.tum.de	Integrated Code Lifecycle Postgres 3 Nodes Iris LTI	GitHub	TUMonline account Test accounts	On Demand
https://artemis-test4.artemis.cit.tum.de	Integrated Code Lifecycle LDAP LTI Apollon Iris MySQL	GitHub	TUMonline account Test accounts	On Demand
https://artemis-test5.artemis.cit.tum.de	Integrated Code Lifecycle Postgres 1 Node Iris LTI	GitHub	TUMonline account Test accounts	On Demand
https://artemis-test6.artemis.cit.tum.de	GitlabCI Postgres 1 Node LTI	GitHub	TUMonline account Test accounts	On Demand
Legacy Testservers: See on confluence below

Test Accounts can be seen on the Artemis Test Server Confluence Page.

GitHub Deployment

1. In your Pull Request on GitHub, scroll all the way down to the build status.

   

2. Wait for the GitHub Docker build to complete successfully

   

3. Check if the test server you want to deploy to is unused. For that, do the following:

   1. Scroll to the testing steps in the PR description

   2. Look at the badges to see which testservers are currently locked

      

   3. If the testserver you want to deploy to is green, you can continue

4. Add the deployment label for your test server

   

   Note: If you try to deploy to a locked server, you will receive an error message (and you waste your time while waiting for it, so just check beforehand like explained above).

   

5. Wait for GitHub to replace your label with the lock label of the test server

   

6. Next to the deployment message in the PR history, GitHub offers a handy button that will forward you to the test server right away. Click it to reach the test server with your PR deployed.

   

7. Perform your testing

8. As soon as you’re done with this PR (even if you want to test more PRs), remove the lock label to make the test server available to other PRs.

   

Bamboo Deployment

1. In your Pull Request on GitHub, scroll all the way down to the build status.

   

2. Click on “Details” next to the successful build with the ASE logo

   

3. Click on #<build number>, either on the green bar or the big title (above “Plan branch”)

   

4. (1) Create release OR (2) Click on the name of the existing release 5.

1. Click on the “Create release” button

   

2. Leave the default options and confirm by clicking “Create release”

   

6. Go to Slack and check the “artemis-testserver” channel.

   1. Check if anyone is using the test server you want to use

   2. If your test server is free, type in the short name. Usually, that would be “ts1”, “ts2”, or “ts3”, and sometimes maybe “ts0” or “staging”. Send the message

   3. The test server is now “yours”

7. Back on Bamboo, click the Deploy button and select the target server. Alternatively, click on the small deployment cloud icon next to the target server in the status list. Bamboo will ask you again to confirm, similarly to the create release workflow. Just leave all default options like they are and confirm.

8. Bamboo will now deploy the PR to the test server. Visit the website of the server and wait until Artemis booted again.

9. Perform your testing

10. After you are done with the PR, there are two options:

    1. Have another PR to test? Start over with step 1. Obviously leave out the slack part as you already reserved the test server for you.

    2. Are you done? Release the test server so it can be used by others by striking through your previous lock message.