Re: Triggering "Windows Build" job

[Ivan Nardi <nardi.ivan () gmail com>]

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 Sept 2021 at 11:24, Roland Knall <rknall () gmail com> wrote:
> 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 builders available to everyone. But if you submit your changes, we can 
> trigger it for you.
>
> Btw, as a Mac & Linux user myself, I keep a virtualbox around just for that purpose. To be able to build Wireshark. 
> It is not required, but certainly helps. Also, building Wireshark on your local Linux machine with a clang compiler 
> instead of gcc, will also identify most issues with the Microsoft VS compilers (as was my experience in the past)
>
> kind regards
> Roland
>
> Am Mo., 13. Sept. 2021 um 11:17 Uhr schrieb Ivan Nardi <nardi.ivan () gmail com>:
> > 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/wireshark/wireshark/-/merge_requests/3628)
> > triggers a warning only in the Windows build.
> > I **think** to have a fix for it. I could push it, wait for a
> > maintainer to pick it up again and cross my fingers...
> > But if I could trigger the Windows test myself it should be less a
> > bother to anyone.
> > Can I do that somehow?
> >
> > I hope I made myself clear
> > Thanks
> >
> > Ivan
> > ___________________________________________________________________________
> > Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> > Archives:    https://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> >              mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe