| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It's useless in its current shape and wrongly triggering on all types.
See https://github.com/rust-lang/rust-clippy/issues/8045
|
|
It's now included in the base image we use.
https://gitlab.freedesktop.org/gstreamer/gstreamer-rs/-/merge_requests/942
|
|
Otherwise it will regularly fail because the runner already has the
directory available for some reason.
|
|
|
|
|
|
|
|
Co-authored-by: Sebastian Dröge <sebastian@centricular.com>
Co-authored-by: Jordan Petridis <jordan@centricular.com>
|
|
|
|
When an MR is open, you can have both a normal and a "detached"
pipeline.
They have different properties, but a detached pipeline is
enough for us and identical to the normal one, so we can avoid
the extra load on the CI.
https://docs.gitlab.com/ee/ci/jobs/job_control.html#avoid-duplicate-pipelines
https://docs.gitlab.com/ee/ci/yaml/index.html#switch-between-branch-pipelines-and-merge-request-pipelines
|
|
Put clippy overrides into the sources files instead of the CI
configuration, and fix various warnings / clean up code.
|
|
Like it was done for the bindings [1]
Also update the ci-template sha
[1] https://gitlab.freedesktop.org/gstreamer/gstreamer-rs/-/merge_requests/836
|
|
|
|
It rejects code such as:
```rust
if state
.start_ts
.zip(accumulate_time)
.map_or(false, |(start_ts, accumulate_time)| {
start_ts + accumulate_time < pts
})
```
because it looks like:
```rust
if { true }
```
|
|
csound-sys can detect the system lib using either pkg-config or using
the CSOUND_LIB_DIR env variable.
The former case just work but the second is trickier as we need to
ensure that CSOUND_LIB_DIR is defined when building.
So we no longer try to detect the lib using find_library() if user
didn't define the env variable as the build will fail later.
Also explicitly pass the env variable to cargo so user can now call
'CSOUND_LIB_DIR=/usr/lib64 meson build && ninja -C build'
and have it work without repassing the env variable to ninja.
|
|
It's supported with the latest version.
Also ignore build.rs when generating reports.
The new gitlab summary parsing regexp is now:
<abbr .*>(\d+.\d+) %<\/abbr>
|
|
It's using the nightly compiler and can easily break every now and then,
like it does now with https://github.com/rust-lang/rust/issues/84421 .
|
|
Uses the new llvm source-base coverage from nightly to generate coverage
reports:
- full html report as artifact
- cobertura report for gitlab MR integration
- output coverage summary for gitlab parsing
Here is the regexp to set in gitlab as "Test coverage parsing":
\s*lines\.*:\s*([\d\.]+%)
Resources:
- https://github.com/marco-c/rust-code-coverage-sample
- https://github.com/mozilla/grcov/issues/468#issuecomment-691615245
- https://www.greycastle.se/how-to-show-flutter-test-coverage-in-gitlab-ci/
|
|
That would otherwise change a lot of API in confusing ways, e.g. RTSP -> Rtsp
and would be inconsistent with the naming in C.
|
|
|
|
Need to define CARGO_HOME so it's installed to the same places as the
rest of the Rust tools.
|
|
Will ensure that our static libraries and pkg-config files are properly
generated.
|
|
|
|
|
|
|
|
|
|
Will prevent us to forget adding new plugins to meson.
|
|
|
|
The gitlab parser will only expand the variables once,
which make it impossible to abstract over the rust
version in a nice way. A hacky workaround is to
duplicate some things and get rid of the RUST_VERSION
var to avoid the issue.
https://gitlab.freedesktop.org/gstreamer/gstreamer-rs/-/merge_requests/618#note_679774
|
|
variables
And don't make the actual version numbers part of the jobs.
|
|
|
|
There have been some very weird issues, where
cargo keeps fetching older commits of glib-rs
and breaking the build like so [1]
Might be stale cache, or some http/git mirroring
shenanigans, so lets stop trying to use the
cache for now and check if the issue persists.
[1]: https://gitlab.freedesktop.org/slomo/gst-plugins-rs/-/jobs/4715922
|
|
|
|
We are caching the CARGO_HOME which includes git repos of
the gtk-rs bindings. Since we don't specify a branch
so it uses the default branch for the ref.
cargo build usually does an update if it has network access,
but its not guaranteed or the case for other tools like clippy
which may still point to the stale git snapshot like here:
https://gitlab.freedesktop.org/thaytan/gstreamer-rs/-/jobs/4165449
|
|
See https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html#checking-commits
In this setup it will check for any leftover fixup!/squash! commits and
that messages don't have the 'Signed-off-by:' tag.
|
|
Unless they are explicitly marked, they won't
run on detached pipelines by default
|
|
only/except is deprecated and going to be removed
from future versions of gitlab.
|
|
Prevent creating a second useless layer, see
https://gitlab.freedesktop.org/freedesktop/ci-templates/-/merge_requests/26
Update image tag to ensure building images is still working.
|
|
Save us from using the static version when building the crate.
|
|
Fix #110
|
|
Those jobs are triggered by gstreamer-rs when their images are updated
so we can rebuild ours.
Also disable normal building jobs and unrelated tests when updating a
specific image as they are not needed.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/321>
|
|
Build our own images based on the ones used by gstreamer-rs ci.
Fix #109
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/321>
|
|
|
|
Workaround so fdo redirects actually work.
|
|
We'd like to be able to ignore some outdated deps which is not yet
possible: https://github.com/kbknapp/cargo-outdated/issues/127
|
|
Automatically detect if a crate we are directly using is outdated.
|
|
|
|
It disables all our other tests apparently.
|
|
At least one dependency of one plugin uses 1.40 features now.
|
|
- Use gst-ci's stages instead of our own
- Override GIT_STRATEGY for Rust only builds as gst-ci relies on
gst-build subprojects by default.
First step merging our Rust CI with gst-ci. Once this is merged we'll
enable Rust in gst-ci builds and so will guard gst-plugins-rs MR against
breaking gst-build.
|
