You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Gregory Nutt <sp...@gmail.com> on 2019/12/20 21:09:18 UTC
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
[This conversation belongs on the dev list]
> Which way is the mirrors?
>
> I believe I read somewhere, it's apache --> github. But I could be wrong.
I recall Duo saying that you can set this up either way.
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
For me I do not think a jenkins job will stop others to try other
solutions, like buildbot or travis CI or other CI tools.
We can both provide our solutions, at least a POC, and then start to argue
which one is better. And maybe both ways are fine, or we can find a way to
them all in one. For HBase, we use both jira and github, and you can upload
your patch on jira and then a jenkins job will test your patch and post the
result on jira. And you can also create a PR on github and another pipeline
jenkins job will test your patch and post the result to GitHub.
Thanks.
Gregory Nutt <sp...@gmail.com> 于2019年12月21日周六 下午12:54写道：
> Same answer. We need to clearly define how the workflow should behave
> first. Then we will have a set of requirements that we can use to make
> trade-offs against the design options.
>
> With no requirements in hand, it is just people supporting their
> favorite tools or implementations they are familiar with. This is no
> way to develop systems. We need top-down requirements analysis, then
> and only then. bottoms up implementation.
>
> We cannot abandon good engineering practices. I think that putting the
> workflow requirements together from existing discussion (if you could
> find it) would be a simple job of an hour or so, if you don't get
> murdered in your sleep for doing so.
>
> Greg
>
> On 12/20/2019 10:46 PM, Brennan Ashton wrote:
> > On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) <pa...@gmail.com>
> wrote:
> >
> >> And I could help setting up the jenkins jobs on the asf infrastructure
> >> against github PRs to test them automatically. The website is
> >> https://builds.apache.org/ . Plan to work with Haitao together next
> week
> >> on
> >> this.
> >>
> > Could we please have a discussion on this before jumping into using
> > Jenkins. I think there are some compelling reasons to use something
> like
> > GitHub Actions, especially with the ability to build on Linux, Windows,
> and
> > Mac easily. Also we can easily register outside runners which I would
> like
> > to wire up for a real device testing lab (I acquired hardware for the
> imxrt
> > family to do this prior to the Apache move)
> >
> > --Brennan
> >
>
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by Gregory Nutt <sp...@gmail.com>.
Same answer. We need to clearly define how the workflow should behave
first. Then we will have a set of requirements that we can use to make
trade-offs against the design options.
With no requirements in hand, it is just people supporting their
favorite tools or implementations they are familiar with. This is no
way to develop systems. We need top-down requirements analysis, then
and only then. bottoms up implementation.
We cannot abandon good engineering practices. I think that putting the
workflow requirements together from existing discussion (if you could
find it) would be a simple job of an hour or so, if you don't get
murdered in your sleep for doing so.
Greg
On 12/20/2019 10:46 PM, Brennan Ashton wrote:
> On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) <pa...@gmail.com> wrote:
>
>> And I could help setting up the jenkins jobs on the asf infrastructure
>> against github PRs to test them automatically. The website is
>> https://builds.apache.org/ . Plan to work with Haitao together next week
>> on
>> this.
>>
> Could we please have a discussion on this before jumping into using
> Jenkins. I think there are some compelling reasons to use something like
> GitHub Actions, especially with the ability to build on Linux, Windows, and
> Mac easily. Also we can easily register outside runners which I would like
> to wire up for a real device testing lab (I acquired hardware for the imxrt
> family to do this prior to the Apache move)
>
> --Brennan
>
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by Gregory Nutt <sp...@gmail.com>.
Thanks for your offer. We really need to agree to an end-to-end
workflow before we invest very much into implementation. The
implementation should not drive the workflow; the workflow requirements
should drive the implementation.
Unfortunately, the topic is now so poisoned that people don't want to
get close to it. I think we need a little time.
Greg
On 12/20/2019 10:30 PM, 张铎(Duo Zhang) wrote:
> And I could help setting up the jenkins jobs on the asf infrastructure
> against github PRs to test them automatically. The website is
> https://builds.apache.org/ . Plan to work with Haitao together next week on
> this.
>
> I saw the very long thread about workflow and seems David was on fire so
> due to my poor English, I haven't jumped in as it is not easy for me to
> find the accurate words to explain my opinion without hurting others'
> feelings. David is a good man, we have talked face to face when he came to
> China recently.
>
> Anyway, I think technically, it is possible for a jenkins job to test
> multiple PRs at once. The jenkins plugin can only allow a single PR to be
> the trigger, but anyway, we could add some special markers in the title of
> the PR to let the jenkins job know that this PR has several related PRs,
> and then the jenkins job could go to fetch these PRs and apply them to
> different git repos and test them together.
>
> Thanks.
>
> 张铎(Duo Zhang) <pa...@gmail.com> 于2019年12月21日周六 下午12:19写道：
>
>> The sync is bidirection.
>>
>> See this page:
>>
>> https://gitbox.apache.org/setup/
>>
>> On https://id.apache.org/ , fill your github username and then there will
>> be an invitation sent to you on github to let you join the apache
>> organization on github. And once the MFA status on
>> https://gitbox.apache.org/setup/ is enabled, then you can directly write
>> to the github repo and sync it back to the asf gitbox, and also you can
>> accept PRs on github.
>>
>> Gregory Nutt <sp...@gmail.com> 于2019年12月21日周六 上午5:09写道：
>>
>>> [This conversation belongs on the dev list]
>>>
>>>> Which way is the mirrors?
>>>>
>>>> I believe I read somewhere, it's apache --> github. But I could be
>>> wrong.
>>>
>>> I recall Duo saying that you can set this up either way.
>>>
>>>
>>>
RE: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by David Sidrane <Da...@nscdg.com>.
+1
-----Original Message-----
From: Brennan Ashton [mailto:bashton@brennanashton.com]
Sent: Friday, December 20, 2019 8:47 PM
To: dev@nuttx.apache.org
Subject: Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) <pa...@gmail.com> wrote:
> And I could help setting up the jenkins jobs on the asf infrastructure
> against github PRs to test them automatically. The website is
> https://builds.apache.org/ . Plan to work with Haitao together next week
> on
> this.
>
Could we please have a discussion on this before jumping into using
Jenkins. I think there are some compelling reasons to use something like
GitHub Actions, especially with the ability to build on Linux, Windows, and
Mac easily. Also we can easily register outside runners which I would like
to wire up for a real device testing lab (I acquired hardware for the imxrt
family to do this prior to the Apache move)
--Brennan
>
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by Brennan Ashton <ba...@brennanashton.com>.
On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) <pa...@gmail.com> wrote:
> And I could help setting up the jenkins jobs on the asf infrastructure
> against github PRs to test them automatically. The website is
> https://builds.apache.org/ . Plan to work with Haitao together next week
> on
> this.
>
Could we please have a discussion on this before jumping into using
Jenkins. I think there are some compelling reasons to use something like
GitHub Actions, especially with the ability to build on Linux, Windows, and
Mac easily. Also we can easily register outside runners which I would like
to wire up for a real device testing lab (I acquired hardware for the imxrt
family to do this prior to the Apache move)
--Brennan
>
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
And I could help setting up the jenkins jobs on the asf infrastructure
against github PRs to test them automatically. The website is
https://builds.apache.org/ . Plan to work with Haitao together next week on
this.
I saw the very long thread about workflow and seems David was on fire so
due to my poor English, I haven't jumped in as it is not easy for me to
find the accurate words to explain my opinion without hurting others'
feelings. David is a good man, we have talked face to face when he came to
China recently.
Anyway, I think technically, it is possible for a jenkins job to test
multiple PRs at once. The jenkins plugin can only allow a single PR to be
the trigger, but anyway, we could add some special markers in the title of
the PR to let the jenkins job know that this PR has several related PRs,
and then the jenkins job could go to fetch these PRs and apply them to
different git repos and test them together.
Thanks.
张铎(Duo Zhang) <pa...@gmail.com> 于2019年12月21日周六 下午12:19写道：
> The sync is bidirection.
>
> See this page:
>
> https://gitbox.apache.org/setup/
>
> On https://id.apache.org/ , fill your github username and then there will
> be an invitation sent to you on github to let you join the apache
> organization on github. And once the MFA status on
> https://gitbox.apache.org/setup/ is enabled, then you can directly write
> to the github repo and sync it back to the asf gitbox, and also you can
> accept PRs on github.
>
> Gregory Nutt <sp...@gmail.com> 于2019年12月21日周六 上午5:09写道：
>
>> [This conversation belongs on the dev list]
>>
>> > Which way is the mirrors?
>> >
>> > I believe I read somewhere, it's apache --> github. But I could be
>> wrong.
>>
>> I recall Duo saying that you can set this up either way.
>>
>>
>>
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to
NuttX committers)
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
The sync is bidirection.
See this page:
https://gitbox.apache.org/setup/
On https://id.apache.org/ , fill your github username and then there will
be an invitation sent to you on github to let you join the apache
organization on github. And once the MFA status on
https://gitbox.apache.org/setup/ is enabled, then you can directly write to
the github repo and sync it back to the asf gitbox, and also you can accept
PRs on github.
Gregory Nutt <sp...@gmail.com> 于2019年12月21日周六 上午5:09写道：
> [This conversation belongs on the dev list]
>
> > Which way is the mirrors?
> >
> > I believe I read somewhere, it's apache --> github. But I could be wrong.
>
> I recall Duo saying that you can set this up either way.
>
>
>
Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)
Posted by David Sidrane <da...@apache.org>.
On 2019/12/20 21:09:18, Gregory Nutt <sp...@gmail.com> wrote:
> [This conversation belongs on the dev list]
>
> > Which way is the mirrors?
> >
> > I believe I read somewhere, it's apache --> github. But I could be wrong.
>
> I recall Duo saying that you can set this up either way.
>
>
>
PMC I would like to suggest the following be merged to bitbucket but not up streamed.
https://bitbucket.org/david_s5/nuttx/src/master_move_notice/
I will also share a suggestion that a college made once when we faced this same situation.
Hold on.cuz it sounds crazy.. you add the above notice with a link back one commit in the repo and `rm -fr` everything else in the repo this commit,
What this does prevent people from mistakenly using the repo and at the same time keeps all the ref to it valid, It is worth considering as it avoids "Oh the ... is a dead project" and hate mail.
Thoughts?
David