```
At line:1 char:34
+ cd $env:CI_PROJECT_DIR/gst-build && python git-update --no-interactio ...
+ ~~
The token '&&' is not a valid statement separator in this version.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordEx
ception
+ FullyQualifiedErrorId : InvalidEndOfLine
```
This is not bash, but powershell, hue hue hue
Rebuild the windows docker image against the current ltsc [1]
of server 2019. This requires moving some of the msys setup
to the runner job cause it causes docker build to hang
Switch the job tags so they now use the 1809 runner, instead
of 1607.
Tweak the PATHs in the msys job so bash doesn't complain about
slashes..
Lastly, increase the timeout of the windows jobs, as msys2
installs its deps at runtime
[1] https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19
In case a build gets stuck for whatever reason,
happens from time to time on windows,
try to baild out quickly.
For cerbero builds, set the timeout to 3h which
according to the docs should also be able to
override the project defined timeout
Fix#19https://docs.gitlab.com/ce/ci/yaml/README.html#timeout
We have lots of tests that timeout on the CI due to a high load
of jobs on the CI runners. Let's try giving them a bit more time
and see how its going.
Check tests are being added to gstreamer/gstreamer-vaapi!181.
However, gstreamer-vaapi inherently requires specific hardware
drivers and platforms to function. The CI does not provide this
level of driver/platform selection. Thus, avoid running any
check tests in gstreamer-vaapi.
We are only using the builddir of the main fedora job to run
tests, the rest where exported by accident. Its especially
problematic cause static build eat a bunch of space and take
an eternity to be uploaded.
Part of #32
* Install git-lfs as its required now by gst-integration-suites
* Clone gst-build eache time to avoid dated gst-build checkouts
and overwritting .wrap files. Similar to !137
* Split the dockerfile and add a second run stage refresh the
powershell env inbetween calls
* Remove the msys2 workaround as its not needed anymore
This adds 3 new jobs that build against msys2 x86_64, msvc 2017 x86
and msvc 2017 x86_64. For the msvc build, some subprojects (like libnice)
don't satisfy all their deps, and are getting automatically disabled.
This doesn't add jobs that run the test suite also. Will hopefully
get implemented later on.
The git-update that is performed attempts to update gst-build however
will not use the updated git-update script for further operations. This
causes the CI to not use any updates to the git-update which is always
stuck on the version provided by the backing docker image.
The valgrind runs are there to spot obvious problems during the dev phase,
not sure we really need to run them in full after each merge.
Should reduce load on the build bots a little.
If any problems slip in they will be picked up soon enough by
the MR jobs again.
