Re: [Mesa-dev] X.Org looking for projects and mentors for the Outreach Program for Women
Just a reminder, if you have projects that are suitable for the OPW please add them to the wiki page or, if you can't access the wiki, send me a summary and I'll add it. http://www.x.org/wiki/XorgOPW/ Prospective participants can start submitting applications on Sep 22 and it'd be great if we had a nice range of projects available by then. Note that unlike GSoC, the scope is not limited to coding (see below). Cheers, Peter On Fri, Sep 05, 2014 at 09:01:44AM +1000, Peter Hutterer wrote: > Hi everyone, > > X.Org will join the Outreach Program for Women (OPW) in Round 9 (December > 2014 - March 2015). The OPW is "open to anyone who was > assigned female at birth and anyone who identifies as a woman, genderqueer, > genderfluid, or genderfree regardless of gender presentation or assigned sex > at birth." > For more details on the program see > https://wiki.gnome.org/OutreachProgramForWomen > > We've secured funding for one participant and are currently looking for > suitable projects and mentors. The scope of the program is "not limited to > coding, but include user experience design, graphic design, documentation, > web development, marketing, translation and other types of tasks needed to > sustain a FOSS project." > > So if you are interested in mentoring or you can think of a suitable > project, please add it to the wiki page or alternatively email me. > http://www.x.org/wiki/XorgOPW/ > > If you are interested in participating and you can think of a suitable > project, please do the same and we'll try our best to find a mentor for you. > > The applications will open on September 22, so let's get some good projects > up there by then! > > Cheers, >Peter, on behalf of the X.Org BoD > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] Interest in participating in the OPW with X.org
Hi Juliet, sorry about the delay, thanks for the email. I don't personally work on mesa so I'll wait if anyone on the list has a project to propose here. On Sat, Sep 20, 2014 at 07:52:38PM +0100, Juliet Fru wrote: > I am Juliet Fru, a second year student of Computer Engineering at the > University of Buea. I am interested in participating in the OPW this year. > I've never worked on an open source project before; and I'll like to have > this first experience with Xorg. I am proficient in C and i'm interested in > writing tests for piglit. I'll like to know based on my discussions on IRC > whether there is any programmer who is working on some functionality he/she > would need me to write unit tests for? I would like to work on writing > tests as my OPW project. One of the best ways to start is to build and run piglit and see if anything needs fixing. That way you get familiar with the code-base and the developers get to know you as well. Having a bit of a reputation from sending patches is a good thing to have. Cheers, Peter ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] 2016 Elections to the X.Org Board of Directors and Approval to Changes of the X.Org By Laws
[Apologies for the delay and the single-recipient message, typo in the original email address] The X.Org Foundation is holding elections for - The Board of Directors - Adoption of changes to the By Laws. Election Schedule = Nomination period Start: Feb 24 00:00 UTC Nomination period End: Mar 15 23:59 UTC (3 weeks) Deadline of X.Org membership application renewal: Mar 17 23:59 UTC Publication of Candidates & start of Candiate QA: Mar 17 (2 weeks) Election Start:Mar 30 00:00 UTC Election End: Apr 12 23:59 UTC (2 weeks) == | PLEASE NOTE: | The memberships of all X.Org Members were expired in Dec 2015! | To participate in this election you MUST renew or apply for membership | by the deadline mentioned above! | Please go to http://members.x.org/ for membership application or renewal. == You will find updated info on the elections at: http://www.x.org/wiki/BoardOfDirectors/Elections/2016/ Board Election == The terms of the following Board Members will end this year: Alex Deucher, Matt Dew, Egbert Eich, Keith Packard There are 4 seats on the X.Org Board of Directors up for reelection. The Elections overview page http://www.x.org/wiki/BoardOfDirectors/Elections/ describes the voting methods and process. The election process starts with a 3 week nomination period. If you would like to nominate yourself please send email to the election committee , giving your - name - current professional affiliation - a statement of contribution to X.Org or related technologies - a personal statement To vote or to be elected to the Board you need to be a Member of the X.Org Foundation. To be a Member of the X.Org Foundation you need to apply or renew your membership until the end of the nomination period. Changes to the By Laws of the X.Org Foundation == The X.Org Foundation plans to join SPI (Software in Public Interest). SPI has given it's formal approval and invited the X.Org Foundation to join. In order to join the Members of the X.Org Foundation need to approve this and need to approve a change to the By Laws of the X.Org Foundation. This vote of the members on joining SPI and on changing the By Laws will take place alongside the election to the BoD. There will be a Q&A session on the SPI membership and the new By Laws starting with the nomination period of the candidates. (Please also see separate announcement). == | PLEASE NOTE: | The vote to change the by-laws requires approval of 2/3 of the membership. | Please do vote in this election. == Q&A === After the nomination period members have the chance to meet the candidates and ask questions on the members mailing list members _AT_ x.org. The Q&A session regarding the By Law changes and the joining SPI starts immediately also on the members mailing list. A Q&A wiki page will also be added. Regards, Peter, on behalf of the X.Org BoD ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] Reminder: 2016 X.Org Board of Directors Elections Nomination period is NOW
We are seeking nominations for candidates for election to the X.Org Foundation Board of Directors. All X.Org Foundation members are eligible for election to the board. Nominations for the 2016 election are now open and will remain open until 23:59 UTC on 15 March 2016. The Board consists of directors elected from the membership. Each year, an election is held to bring the total number of directors to eight. The four members receiving the highest vote totals will serve as directors for two year terms. The directors who received two year terms starting in 2015 were Peter Hutterer, Martin Peres, Rob Clark and Daniel Vetter, They will continue to serve until their term ends in 2017. Current directors whose term expires in 2016 are Alex Deucher, Matt Dew, Egbert Eich and Keith Packard. A director is expected to participate in the fortnightly IRC meeting to discuss current business and to attend the annual meeting of the X.Org Foundation, which will be held at a location determined in advance by the Board of Directors. A member may nominate themselves or any other member they feel is qualified. Nominations should be sent to the Election Committee at electi...@x.org. Nominees shall be required to be current members of the X.Org Foundation, and submit a personal statement of up to 200 words that will be provided to prospective voters. The collected statements, along with the statement of contribution to the X.Org Foundation in the members account page on http://members.x.org, will be made available to all voters to help them make their voting decisions. Nominations, membership applications or renewals and completed personal statements must be received no later than 23:59 UTC on 15 March 2016. The slate of candidates will be published 17 March 2016 and candidate Q&A will begin then. The deadline for Xorg membership applications and renewals is 17 March 2016. Cheers, Peter, on behalf of the X.Org BoD ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] Reminder: 2016 X.Org Board of Directors Elections Nomination period is NOW
We are seeking nominations for candidates for election to the X.Org Foundation Board of Directors. All X.Org Foundation members are eligible for election to the board. Nominations for the 2016 election are now open and will remain open until 23:59 UTC on 15 March 2016. The Board consists of directors elected from the membership. Each year, an election is held to bring the total number of directors to eight. The four members receiving the highest vote totals will serve as directors for two year terms. The directors who received two year terms starting in 2015 were Peter Hutterer, Martin Peres, Rob Clark and Daniel Vetter, They will continue to serve until their term ends in 2017. Current directors whose term expires in 2016 are Alex Deucher, Matt Dew, Egbert Eich and Keith Packard. A director is expected to participate in the fortnightly IRC meeting to discuss current business and to attend the annual meeting of the X.Org Foundation, which will be held at a location determined in advance by the Board of Directors. A member may nominate themselves or any other member they feel is qualified. Nominations should be sent to the Election Committee at electi...@x.org. Nominees shall be required to be current members of the X.Org Foundation, and submit a personal statement of up to 200 words that will be provided to prospective voters. The collected statements, along with the statement of contribution to the X.Org Foundation in the members account page on http://members.x.org, will be made available to all voters to help them make their voting decisions. Nominations, membership applications or renewals and completed personal statements must be received no later than 23:59 UTC on 15 March 2016. The slate of candidates will be published 17 March 2016 and candidate Q&A will begin then. The deadline for Xorg membership applications and renewals is 17 March 2016. Cheers, Peter, on behalf of the X.Org BoD ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] EXTENDED: 2016 X.Org Board of Directors Elections Nomination period is NOW
We had a number of last-minute nominations and this did not give all nominees the chance to respond to the nominations. Hence, we are extending the nomination period for two weeks. All election dates thus move back by two weeks. Below is the original text of the nomination request email. We are seeking nominations for candidates for election to the X.Org Foundation Board of Directors. All X.Org Foundation members are eligible for election to the board. Nominations for the 2016 election are now open and will remain open until 23:59 UTC on 29 March 2016. The Board consists of directors elected from the membership. Each year, an election is held to bring the total number of directors to eight. The four members receiving the highest vote totals will serve as directors for two year terms. The directors who received two year terms starting in 2015 were Peter Hutterer, Martin Peres, Rob Clark and Daniel Vetter, They will continue to serve until their term ends in 2017. Current directors whose term expires in 2016 are Alex Deucher, Matt Dew, Egbert Eich and Keith Packard. A director is expected to participate in the fortnightly IRC meeting to discuss current business and to attend the annual meeting of the X.Org Foundation, which will be held at a location determined in advance by the Board of Directors. A member may nominate themselves or any other member they feel is qualified. Nominations should be sent to the Election Committee at electi...@x.org. Nominees shall be required to be current members of the X.Org Foundation, and submit a personal statement of up to 200 words that will be provided to prospective voters. The collected statements, along with the statement of contribution to the X.Org Foundation in the members account page on http://members.x.org, will be made available to all voters to help them make their voting decisions. Nominations, membership applications or renewals and completed personal statements must be received no later than 23:59 UTC on 15 March 2016. The slate of candidates will be published 31 March 2016 and candidate Q&A will begin then. The deadline for Xorg membership applications and renewals is 31 March 2016. Cheers, Peter, on behalf of the X.Org BoD signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] X.Org looking for projects and mentors for the Outreach Program for Women
Hi everyone, X.Org will join the Outreach Program for Women (OPW) in Round 9 (December 2014 - March 2015). The OPW is "open to anyone who was assigned female at birth and anyone who identifies as a woman, genderqueer, genderfluid, or genderfree regardless of gender presentation or assigned sex at birth." For more details on the program see https://wiki.gnome.org/OutreachProgramForWomen We've secured funding for one participant and are currently looking for suitable projects and mentors. The scope of the program is "not limited to coding, but include user experience design, graphic design, documentation, web development, marketing, translation and other types of tasks needed to sustain a FOSS project." So if you are interested in mentoring or you can think of a suitable project, please add it to the wiki page or alternatively email me. http://www.x.org/wiki/XorgOPW/ If you are interested in participating and you can think of a suitable project, please do the same and we'll try our best to find a mentor for you. The applications will open on September 22, so let's get some good projects up there by then! Cheers, Peter, on behalf of the X.Org BoD ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [RFC] Allow fd.o to join forces with X.Org
On Mon, Oct 15, 2018 at 10:49:24AM -0400, Harry Wentland wrote:
> The leadership of freedesktop.org (fd.o) has recently expressed interest
> in having an elected governing body. Given the tight connection between
> fd.o and X.Org and the fact that X.Org has such a governing body it
> seemed obvious to consider extending X.Org's mandate to fd.o.
>
> Quite a bit of background on fd.o leading up to this has been covered by
> Daniel Stone at XDC 2018 and was covered really well by Jake Edge of LWN [1].
>
> One question that is briefly addressed in the LWN article and was
> thoroughly discussed by members of the X.Org boards, Daniel Stone, and
> others in hallway discussions is the question of whether to extend the
> X.Org membership to projects hosted on fd.o but outside the purpose of
> the X.Org foundation as enacted in its bylaws.
>
> Most people I talked to would prefer not to dilute X.Org's mission and
> extend membership only to contributors of projects that follow X.Org's
> purpose as enacted in its bylaws. Other projects can continue to be
> hosted on fd.o but won't receive X.Org membership for the mere reason of
> being hosted on fd.o.
>
> [1] https://lwn.net/Articles/767258/
>
> v2:
> - Subject line that better describes the intention
> - Briefly describe reasons behind this change
> - Drop expanding membership eligibility
> ---
>
> We're looking for feedback and comments on this patch. If it's not
> widely controversial the final version of the patch will be put to a
> vote at the 2019 X.Org elections.
>
> The patch applies to the X.Org bylaws git repo, which can be found at
> https://gitlab.freedesktop.org/xorgfoundation/bylaws
>
> Happy commenting.
>
> Harry
>
> bylaws.tex | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/bylaws.tex b/bylaws.tex
> index 4ab35a4f7745..44ff4745963b 100644
> --- a/bylaws.tex
> +++ b/bylaws.tex
> @@ -14,7 +14,7 @@ BE IT ENACTED AND IT IS HEREBY ENACTED as a By-law of the
> X.Org Foundation
>
> The purpose of the X.Org Foundation shall be to:
> \begin{enumerate}[(i)\hspace{.2cm}]
> - \item Research, develop, support, organize, administrate, standardize,
> + \item \label{1} Research, develop, support, organize, administrate,
> standardize,
> promote, and defend a free and open accelerated graphics stack. This
> includes, but is not limited to, the following projects: DRM, Mesa,
> Wayland and the X Window System,
> @@ -24,6 +24,11 @@ The purpose of the X.Org Foundation shall be to:
>
> \item Support and educate the general community of users of this
> graphics stack.
> +
> + \item Support free and open source projects through the freedesktop.org
> + infrastructure. For projects outside the scope of item (\ref{1}) support
> + extends to project hosting only.
> +
Yes to the idea but given that the remaining 11 pages cover all the legalese
for xorg I think we need to add at least a section of what "project hosting"
means. Even if it's just a "includes but is not limited to blah". And some
addition to 4.1 Powers is needed to spell out what the BoD can do in regards
to fdo.
Cheers,
Peter
> \end{enumerate}
>
> \article{INTERPRETATION}
> --
> 2.19.1
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [RFC] Allow fd.o to join forces with X.Org
On Wed, Oct 17, 2018 at 02:37:25PM +0200, Daniel Vetter wrote:
> On Wed, Oct 17, 2018 at 2:05 PM Daniel Stone wrote:
> >
> > On Tue, 16 Oct 2018 at 08:17, Peter Hutterer
> > wrote:
> > > On Mon, Oct 15, 2018 at 10:49:24AM -0400, Harry Wentland wrote:
> > > > + \item Support free and open source projects through the
> > > > freedesktop.org
> > > > + infrastructure. For projects outside the scope of item (\ref{1})
> > > > support
> > > > + extends to project hosting only.
> > > > +
> > >
> > > Yes to the idea but given that the remaining 11 pages cover all the
> > > legalese
> > > for xorg I think we need to add at least a section of what "project
> > > hosting"
> > > means. Even if it's just a "includes but is not limited to blah". And
> > > some
> > > addition to 4.1 Powers is needed to spell out what the BoD can do in
> > > regards
> > > to fdo.
> >
> > Yeah, I think it makes sense. Some things we do:
> > - provide hosted network services for collaborative development,
> > testing, and discussion, of open-source projects
> > - administer, improve, and extend this suite of services as necessary
> > - assist open-source projects in their use of these services
> > - purchase, lease, or subscribe to, computing and networking
> > infrastructure allowing these services to be run
>
> I fully agree that we should document all this. I don't think the
> bylaws are the right place though, much better to put that into
> policies that the board approves and which can be adapted as needed.
> Imo bylaws should cover the high-level mission and procedural details,
> as our "constitution", with the really high acceptance criteria of
> 2/3rd of all members approving any changes. Some of the early
> discussions tried to spell out a lot of the fd.o policies in bylaw
> changes, but then we realized it's all there already. All the details
> are much better served in policies enacted by the board, like we do
> with everything else.
>
> As an example, let's look at XDC. Definitely one of the biggest things
> the foundation does, with handling finances, travel sponsoring grants,
> papers committee, and acquiring lots of sponsors. None of this is
> spelled out in the bylaws, it's all in policies that the board
> deliberates and approves. I think this same approach will also work
> well for fd.o.
>
> And if members are unhappy with what the board does, they can fix in
> the next election by throwing out the unwanted directors.
yeah, fair call. though IMO in that case we can just reduce to
\item Support free and open source projects through the freedesktop.org
infrastructure.
because my gripe is less with the fdo bit but more with defining what
"project hosting" means, given that we use that term to exclude fdo projects
from getting anything else. I think just dropping that bit is sufficient.
Cheers,
Peter
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH v3] Allow fd.o to join forces with X.Org
On Thu, Nov 08, 2018 at 05:52:08PM -0500, Harry Wentland wrote:
> The leadership of freedesktop.org (fd.o) has recently expressed interest
> in having an elected governing body. Given the tight connection between
> fd.o and X.Org and the fact that X.Org has such a governing body it
> seemed obvious to consider extending X.Org's mandate to fd.o.
>
> Quite a bit of background on fd.o leading up to this has been covered by
> Daniel Stone at XDC 2018 [2] and was covered really well by Jake Edge of
> LWN [1].
>
> One question that is briefly addressed in the LWN article and was
> thoroughly discussed by members of the X.Org boards, Daniel Stone, and
> others in hallway discussions is the question of whether to extend the
> X.Org membership to projects hosted on fd.o but outside the purpose of
> the X.Org foundation as enacted in its bylaws.
>
> Most people I talked to would prefer not to dilute X.Org's mission and
> extend membership only to contributors of projects that follow X.Org's
> purpose as enacted in its bylaws. Other projects can continue to be
> hosted on fd.o but won't receive X.Org membership for the mere reason of
> being hosted on fd.o.
>
> [1] https://lwn.net/Articles/767258/
> [2] https://youtu.be/s22B3E7rUTs
>
> v3:
> - Clarify what support of fd.o projects entails without formalizing a
>two-tier system for fd.o projects that fall under X.Org's mandate and
>those who don't
> - Add link to Daniel's talk at XDC2018
>
> v2:
> - Subject line that better describes the intention
> - Briefly describe reasons behind this change
> - Drop expanding membership eligibility
>
> Acked-by: Daniel Stone
> ---
>
> We're looking for feedback and comments on this patch. If it's not
> widely controversial the final version of the patch will be put to a
> vote at the 2019 X.Org elections.
>
> The patch applies to the X.Org bylaws git repo, which can be found at
> https://gitlab.freedesktop.org/xorgfoundation/bylaws
>
> Happy commenting.
Acked-by: Peter Hutterer
Cheers,
Peter
> Harry
>
> bylaws.tex | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/bylaws.tex b/bylaws.tex
> index 4ab35a4f7745..5a7542739582 100644
> --- a/bylaws.tex
> +++ b/bylaws.tex
> @@ -24,6 +24,11 @@ The purpose of the X.Org Foundation shall be to:
>
> \item Support and educate the general community of users of this
> graphics stack.
> +
> + \item Support free and open source projects through the freedesktop.org
> + infrastructure. This includes, but is not limited to: Administering and
> + providing project hosting services.
> +
> \end{enumerate}
>
> \article{INTERPRETATION}
> --
> 2.19.1
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] Results of the 2016 Election to the X.Org BoD & Vote on the By-Law Changes
The 2016 Election is now over and the results are in. Two questions were up for voting, 4 seats on the Board of Directors and approval of the amended By-Laws to join SPI. The Results of the Board of Director elections: Candidates and their respective points: Egbert Eich 205 Alex Deucher 195 Keith Packard152 Bryce Harrington 142 Lucas Stach 129 Therefore the following candidates have been elected to the board: Egbert Eich, Alex Deucher, Keith Packard, Bryce Harrington The results on the vote to change the By-Laws to join SPI: Do you agree to the changed By-Laws? Yes 54/65 (83.1%) No 4/65 (6.2%) Abstain 3/65 (4.6%) We have 65 members and 61 votes were recorded. According to Article 7 of the Oct. 29, 2006 By-Laws the following provision is made for changes to the By-Laws: "AMENDMENT These By-law may be altered, amended or repealed by an affirmative vote of at least two-thirds (2/3) of the Members of X.Org." We have reached quorum and have a 2/3 majority in favour of the change. The changes to the By-Laws are thus accepted. Cheers, The X.Org 2016 Election Committee Peter Hutterer Daniel Vetter Martin Peres Rob Clark signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [Intel-gfx] gitlab.fd.o financial situation and impact on services
On Sat, Apr 04, 2020 at 11:16:08AM -0700, Rob Clark wrote: > On Sat, Apr 4, 2020 at 10:47 AM Nicolas Dufresne wrote: > > > > Le samedi 04 avril 2020 à 08:11 -0700, Rob Clark a écrit : > > > On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer wrote: > > > > On 2020-03-01 6:46 a.m., Marek Olšák wrote: > > > > > For Mesa, we could run CI only when Marge pushes, so that it's a > > > > > strictly > > > > > pre-merge CI. > > > > > > > > Thanks for the suggestion! I implemented something like this for Mesa: > > > > > > > > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432 > > > > > > > > > > I wouldn't mind manually triggering pipelines, but unless there is > > > some trick I'm not realizing, it is super cumbersome. Ie. you have to > > > click first the container jobs.. then wait.. then the build jobs.. > > > then wait some more.. and then finally the actual runners. That would > > > be a real step back in terms of usefulness of CI.. one might call it a > > > regression :-( > > > > On GStreamer side we have moved some existing pipeline to manual mode. > > As we use needs: between jobs, we could simply set the first job to > > manual (in our case it's a single job called manifest in your case it > > would be the N container jobs). This way you can have a manual pipeline > > that is triggered in single (or fewer) clicks. Here's an example: > > > > https://gitlab.freedesktop.org/gstreamer/gstreamer/pipelines/128292 > > > > That our post-merge pipelines, we only trigger then if we suspect a > > problem. > > > > I'm not sure that would work for mesa since the hierarchy of jobs > branches out pretty far.. ie. if I just clicked the arm64 build + test > container jobs, and everything else ran automatically after that, it > would end up running all the CI jobs for all the arm devices (or at > least all the 64b ones) generate your gitlab-ci from a template so each pipeline has its own job dependency. The duplication won't hurt you if it's expanded through templating and it gives you fine-grained running of the manual jobs. We're using this in ci-templates/libevdev/libinput for the various distributions and their versions so each distribution+version is effectively its own pipeline. But we only need to maintain one job in the actual template file. https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html#templating-gitlab-ci-yml Cheers, Peter ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [Intel-gfx] gitlab.fd.o financial situation and impact on services
On Sat, Apr 04, 2020 at 08:11:23AM -0700, Rob Clark wrote: > On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer wrote: > > > > On 2020-03-01 6:46 a.m., Marek Olšák wrote: > > > For Mesa, we could run CI only when Marge pushes, so that it's a strictly > > > pre-merge CI. > > > > Thanks for the suggestion! I implemented something like this for Mesa: > > > > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432 > > > > I wouldn't mind manually triggering pipelines, but unless there is > some trick I'm not realizing, it is super cumbersome. Ie. you have to > click first the container jobs.. then wait.. then the build jobs.. > then wait some more.. and then finally the actual runners. That would > be a real step back in terms of usefulness of CI.. one might call it a > regression :-( I *think* this should work though if you set up the right job dependencies. very simple example: https://gitlab.freedesktop.org/whot/ci-playground/pipelines/128601 job1 is "when:manual", job2 has "needs: job1", job3 has "needs: job2". Nothing runs at first, if you trigger job1 it'll cascade down to job 2 and 3. The main limit you have here are the stages - where a job is part of a stage but does not have an explicit "needs:" it will wait for the previous stage to complete. That will never happen if one job in that stage has a manual dependency. See this pipeline as an example: https://gitlab.freedesktop.org/whot/ci-playground/pipelines/128605 So basically: if you set up all your jobs with the correct "needs" you could even have a noop stage for user interface purposes. Here's an example: https://gitlab.freedesktop.org/whot/ci-playground/pipelines/128606 It has a UI stage with "test-arm" and "test-x86" manual jobs. It has other stages with dependent jobs on those (cascading down) but it also has a set of autorun jobs that run independent of the manual triggers. When you push, the autorun jobs run. When you trigger "test-arm" manually, it triggers the various dependent jobs. So I think what you want to do is possible, it just requires some tweaking of the "needs" entries. Cheers, Peter ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
