Setting up environment for CI/CD

[Pandawan]

(Continuing from #140)

I've setup a simple repository with docker to try and get a minimal reproducible example:

Dockerfile

FROM rust:1.59

WORKDIR /usr/src/example
COPY . .

RUN cargo install --path .

RUN cargo build

RUN apt-get update && apt-get install -y libdbus-1-dev

CMD ["cargo", "run"]

main.rs

use notify_rust::Notification;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    Notification::new()
        .summary("Title")
        .body("Body")
        .show()?;
    Ok(())
}

When running this docker container (with the appropriate cargo setup and notify-rust = "4.5.8"), I get the error:

thread 'main' panicked at 'called Result::unwrap() on an Err value: Error { kind: Zbus(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })) }', src/main.rs:4:55

I'm assuming this means that my environment is missing some kind of config file (or maybe something else, given that unix uses files for everything). It seems like your ci.yml file (for the linux_zbus job) doesn't have anything specific so I'm unsure what I could be missing.

Any insight would be appreciated!

[hoodie]

seems we're continuing in #140 after all 😁

[zeenix]

It may have to do with there being no DBUS_SESSION_BUS_ADDRESS as was suggested in #140?

Yes and you need the bus running as well. If you want your app to be talking to your desktop session, you need to provide access to the session bus socket on your host to the docker container and set the env.

As for a CI example, the zbus CI could give you some clues.

[Pandawan]

Gotcha, I'll look into those, thanks! It's just strange that notify-rust's ci doesn't have any of these and yet is able to test it... Unless I'm missing something.

[zeenix]

@Pandawan best of luck. @hoodie can say if I'm wrong but I'm guessing the notify's tests are not e2e and hence not talking to the service on the bus.

[hoodie]

oh yes, my bad, I forgot that, sorry!
That's what the original server was for. I usually do manual tests locally on.
That is partially also necessary because KDE/Gnome/Xfce etc have slightly different behavior when displaying the notifications. so the actual sending is not tested in CI.

[Pandawan]

Gotcha, so I guess what @zeenix said with zbus' CI is the way to go. Thanks!

[hoodie]

Thing is, something needs to provide that org.freedesktop.notification interface, otherwise you'll just get errors upon sending too.