On Mon, Sep 13, 2021 at 7:39 PM Gerald Combs wrote:
> How long does the GitHub action take to run?
According to the jobs history, it takes 25 to 30 minutes, which looks
comparable to the wireshark's builds for windows on gitlab.
It usually gets scheduled very quickly, which does not happen in a
How long does the GitHub action take to run? The "Windows Build" job currently uses a
dedicated runner, which is why it only gets run if a maintainer submits, rebases or otherwise
"lays hands" the MR. We use a dedicated runner because installing all of our
prerequisites, building Wireshark, and
You can also leverage github actions: it has a windows build. Just push on
a github fork of yours and you'll trigger a windows build.
https://github.com/wireshark/wireshark/actions/workflows/windows.yml
On Mon, Sep 13, 2021 at 2:48 PM Ivan Nardi wrote:
> Hi Roland
> I thought that the present c
Hi Roland
I thought that the present configuration was a trade-off between
flexibility and resource constraints.
Thank you very much for the suggestions, very appreciated! I will
definitely compile Wireshark with both gcc and clang from now on.
Thanks for your reply
Kind regards
Ivan
On Mon, 13
Hi Ivan
We have a limited number of machines for our build-jobs. Therefore only
when we set the merge-request to a semi-done level, buildjobs are
triggered. What you can do though, is run your own pipeline, and use our
.gitlab-ci.yml file as a template.
At this point we do not plan on making the
Hi
If I am not wrong, the "Windows Build" job is triggered only after a
maintainer picks up the MR and assigns it to the "Wireshark GitLab
Utility".
Is there any way I can trigger it myself?
Some background.
I don't have a Windows machine to build Wireshark myself.
My last MR (https://gitlab.com/
