search for: before_script

...script executions add the unique ID to the duplicate-tracking list, all "duplicate" tests in the Sieve script would erroneously yield "true" for the next delivery attempt of the same message. Dovecot seems not to honour this specification. Maybe this is because the "before_script" is not the script that fails, but the subsequent scripts fail? Am I missing some configuration option that would propagate the subsequent failure back to the before_script? Or is this a general limitation of the before_script mechanism? Any help appreciated how to alleviate this issue! Best...

...ue ID to the duplicate-tracking list, > all "duplicate" tests in the Sieve script would erroneously yield > "true" for the next delivery attempt of the same message. > > Dovecot seems not to honour this specification. > > Maybe this is because the "before_script" is not the script that fails, > but the subsequent scripts fail? > Am I missing some configuration option that would propagate the > subsequent failure back to the before_script? > Or is this a general limitation of the before_script mechanism? > > Any help appreciated how t...

...s site would also work.. dunno if > it actually makes a difference anyway, but that might be more work. > The work is pretty minimal for what I typically do. You need a CI job to build the docs on merge requests and pushes, which at its most verbose is something like: docs: stage: test before_script: # Pin Sphinx to a particular major version - python3 -m venv ~/docs-venv - source ~/docs-venv/bin/activate - pip install "sphinx<3" - pushd path/to/docs script: make SPHINXOPTS="-W" html artifacts: paths: - path/to/docs/_build/ only: r...

On Wed, Sep 23, 2020 at 11:36:54PM +0200, Karol Herbst wrote: > On Wed, Sep 23, 2020 at 10:39 PM Jeremy Cline <jcline at redhat.com> wrote: > > > > On Wed, Sep 23, 2020 at 09:02:45PM +0200, Karol Herbst wrote: > > > On Fri, Sep 11, 2020 at 6:21 PM Jeremy Cline <jcline at redhat.com> wrote: > > > > <snip> > > > > > yeah, I think