Merge pull request #460 from hpi-swa-teaching/develop

Merges results from 2021 into master

Author: codeZeilen

.github/pull_request_template.md

@@ -10,7 +10,7 @@ Please, go through these steps before you submit a PR.
     c. You have only one commit (if not, squash them into one commit).
 
     d. Running tests doesn't throw any error. If it does, fix them first and amend your commit (`git commit --amend`).
-    
+
     e. You have tracked ALL applicable time working in clockify!
 
 3. **After** these steps, you're ready to open a pull request.

.github/workflows/ci-linter.yml

@@ -1,6 +1,6 @@
 name: CI-Lint
 
-on: 
+on:
   push:
     branches:
       - develop

.github/workflows/main.yml

@@ -1,6 +1,6 @@
 name: CI
 
-on: 
+on:
   push:
     branches:
       - develop
@@ -17,14 +17,19 @@ jobs:
       fail-fast: false
       matrix:
         os: [ ubuntu-latest ]
-        smalltalk: [ Squeak64-Trunk, Squeak64-5.3, Squeak64-5.2 ]
+        smalltalk: [ Squeak64-5.3 ]
     name: ${{ matrix.smalltalk }} on ${{ matrix.os }}
     steps:
       - uses: actions/checkout@v2
       - uses: hpi-swa/setup-smalltalkCI@v1
         with:
           smalltalk-version: ${{ matrix.smalltalk }}
       - run: smalltalkci -s ${{ matrix.smalltalk }}
-        timeout-minutes: 15
+        timeout-minutes: 30
         env:
            GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/upload-artifact@master
+        if: ${{ always() }}
+        with:
+          name: Test Artifacts (${{ matrix.smalltalk }} (${{ matrix.os }}))
+          path: /home/runner/.smalltalkCI/_builds/telegramTestResults

.github/workflows/release.yml

@@ -39,17 +39,17 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-          tag_name: ${{ steps.tag_prefix.outputs.value }}${{ steps.current-time.outputs.formattedTime }} 
+          tag_name: ${{ steps.tag_prefix.outputs.value }}${{ steps.current-time.outputs.formattedTime }}
           release_name: ${{ matrix.smalltalk }} ${{ steps.current-time.outputs.formattedTime }}
           draft: false
           prerelease: ${{ env.prerelease }}
       - name: Upload Release Asset
-        id: upload-release-asset 
+        id: upload-release-asset
         uses: actions/upload-release-asset@v1
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-          upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps 
+          upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
           asset_path: /home/runner/.smalltalkCI/_builds/TelegramClient.sar
           asset_name: TelegramClient.sar
           asset_content_type: application/zip

.gitignore

@@ -0,0 +1,2 @@
+.DS_STORE
+/.idea

.smalltalk.lint.ston

@@ -12,6 +12,6 @@ SmalltalkCISpec {
     'scripts/preLoading.st'
   ],
   #testing : {
-    #classes : [ #TCTLinterTests ]
+    #classes : [ #TCTMLinterTests ]
   }
 }

.smalltalk.release.ston

@@ -10,7 +10,7 @@ SmalltalkCISpec {
     }
   ],
    #testing : {
-    #classes : [ #TCTSarFileGenerator ],
+    #classes : [ #TCTMSarFileGenerator ],
     #defaultTimeout : 60
   }
 }

.smalltalk.ston

@@ -14,7 +14,7 @@ SmalltalkCISpec {
       #packages : [ 'TelegramClient-Core.*', 'TelegramClient-UI.*' ]
     },
     #exclude : {
-      #classes : [ #TCTLinterTests ]
+      #classes : [ #TCTMLinterTests ]
     },
     #defaultTimeout : 60
   }

.squot

@@ -1,6 +1,8 @@
 OrderedDictionary {
-	'packages\/TelegramClient-Core.package' : #SquotCypressCodeSerializer,
-	'packages\/TelegramClient-Tests.package' : #SquotCypressCodeSerializer,
-	'packages\/BaselineOfTelegramClient.package' : #SquotCypressCodeSerializer,
-	'packages\/TelegramClient-UI.package' : #SquotCypressCodeSerializer
+	'packages/TelegramClient-Core.package' : #SquotCypressCodeSerializer,
+	'packages/BaselineOfTelegramClient.package' : #SquotCypressCodeSerializer,
+	'packages/TelegramClient-UI.package' : #SquotCypressCodeSerializer,
+	'packages/TelegramClientTests-Core.package' : #SquotCypressCodeSerializer,
+	'packages/TelegramClientTests-UI.package' : #SquotCypressCodeSerializer,
+	'packages/TelegramClientTests-Misc.package' : #SquotCypressCodeSerializer
 }

CONTRIBUTING.md

@@ -83,7 +83,7 @@ $ git merge develop                                  // merges changes from mast
 When development on the feature is complete, reviewers should merge changes into `develop` and then make sure the remote branch is deleted.
 
 ```
-$ git checkout develop                               // change to the develop branch  
+$ git checkout develop                               // change to the develop branch
 $ git merge --no-ff feature/GH-id                      // makes sure to create a commit object during merge
 $ git push origin develop                            // push merge changes
 $ git push origin :feature/GH-id                       // deletes the remote branch
@@ -97,7 +97,7 @@ Fix branches differ from feature branches only semantically. Fix branches will b
 
 Although likelihood will be less, during the lifespan of the bug development, the lead should watch the `develop` branch (network tool or branch tool in GitHub) to see if there have been commits since the bug was branched. Any and all changes to `develop` should be merged into the bug before merging back to `develop`; this can be done at various times during the project or at the end, but time to handle merge conflicts should be accounted for.
 
-`<tbd number>` represents the Basecamp project to which Project Management will be tracked. 
+`<tbd number>` represents the Basecamp project to which Project Management will be tracked.
 
 * Must branch from: `develop`
 * Must merge back into: `develop`
@@ -121,7 +121,7 @@ $ git merge develop                                  // merges changes from deve
 When development on the bug is complete, [the Lead] should merge changes into `develop` and then make sure the remote branch is deleted.
 
 ```
-$ git checkout develop                               // change to the develop branch  
+$ git checkout develop                               // change to the develop branch
 $ git merge --no-ff bugfix/GH-id                          // makes sure to create a commit object during merge
 $ git push origin develop                            // push merge changes
 $ git push origin :bugfix/GH-id                           // deletes the remote branch