** Notice: all internal pipelines have been restricted to 30 minute timeouts, if your CI/CD runs take longer, either use your own runners or read below **
We would remind everyone that the CI/CD services provided by the university Gitlab servers are intended for CI/CD use only (ie. delivering new versions of your software to your production servers, etc).They are not intended for data analysis or -production use, or creating, building and running servers to do heavy data calculation or visualization.
As a general guideline; if your jobs take more than 15 minutes, you might be running something that is better suited for a dedicated system or a virtual server - in this case, please contact the helpdesk for a solution to your needs.
@@ -24,7 +24,7 @@ Let's start by setting up a new git repository:
...
@@ -24,7 +24,7 @@ Let's start by setting up a new git repository:
```
```
$ git init
$ git init
Initialized empty Git repository in /home/j/johnson/practice_git/.git/
Initialized empty Git repository in /home/jubery/Documents/Github/exercise/.git/
```
```
Now Git will start tracking the content of this directory. All changes and old versions are saved in a directory named `.git` which is hidden by default.
Now Git will start tracking the content of this directory. All changes and old versions are saved in a directory named `.git` which is hidden by default.
...
@@ -171,7 +171,9 @@ Let's try to rename the file again. Let's change the file name to `MessageTimes1
...
@@ -171,7 +171,9 @@ Let's try to rename the file again. Let's change the file name to `MessageTimes1
`$ git status`
`$ git status`
<imgsrc="pictures/change1.png"alt="">,Since Git does not understand the changed file name, it shows two changes. The change must be sent to the repository either by adding both files separately
<imgsrc="pictures/change1.png"alt="">
Since Git does not understand the changed file name, it shows two changes. The change must be sent to the repository either by adding both files separately
