Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
Hi,

We are still on track to retire SVN and complete the transition to GitHub
by Oct 21, 2019 (This year's US Dev Meeting).

Even though this 3+ months away, it is very important that you begin to migrate
your workflows to GitHub as soon as possible.  For developers, this means using
the git-llvm script to commit changes and for CI systems or other read-only use
cases can begin fetching code directly from GitHub.

I have created a migration status page, so you can track the progress of the migration:
http://llvm.org/GitHubMigrationStatus.html  There is also a link to instructions for
how to use the git-llvm script for committing changes.

If you would like to help with any of the TODOs on that page, please comment on the
bugzilla associated with the task.

Thanks,
Tom
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
On Fri, Jul 12, 2019 at 4:24 AM Tom Stellard via llvm-dev
<[hidden email]> wrote:
> We are still on track to retire SVN and complete the transition to GitHub
> by Oct 21, 2019 (This year's US Dev Meeting).
>
> Even though this 3+ months away, it is very important that you begin to migrate
> your workflows to GitHub as soon as possible.  For developers, this means using
> the git-llvm script to commit changes and for CI systems or other read-only use
> cases can begin fetching code directly from GitHub.

The migration isn't just about moving from SVN to Git. For many folks,
it's also about moving from individual component repository to the
monorepo.

What's the experience people have had with that move? What works and
what doesn't?

Cheers,
Nicolai

--
Lerne, wie die Welt wirklich ist,
aber vergiss niemals, wie sie sein sollte.
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
On 2019-07-12 17:41, Nicolai Hähnle-Montoro via llvm-dev wrote:

> On Fri, Jul 12, 2019 at 4:24 AM Tom Stellard via llvm-dev
> <[hidden email]> wrote:
>> We are still on track to retire SVN and complete the transition to
>> GitHub
>> by Oct 21, 2019 (This year's US Dev Meeting).
>>
>> Even though this 3+ months away, it is very important that you begin
>> to migrate
>> your workflows to GitHub as soon as possible.  For developers, this
>> means using
>> the git-llvm script to commit changes and for CI systems or other
>> read-only use
>> cases can begin fetching code directly from GitHub.
>
> The migration isn't just about moving from SVN to Git. For many folks,
> it's also about moving from individual component repository to the
> monorepo.
>
> What's the experience people have had with that move? What works and
> what doesn't?

One gotcha was the automatic blind inclusion of "clang extra tools"
when building clang (eg `-DLLVM_ENABLE_PROJECTS="clang;lld"`).

This caused linker problems (trying to build a static lib), which we
weren't able to solve in a few hours of looking.

Instead, the undocumented flag `-DLLVM_TOOL_CLANG_TOOLS_EXTRA_BUILD=OFF`
can be added to the CMake line to turn off building those extra tools.

With that flag added things worked. :)

+ Justin


> Cheers,
> Nicolai
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
In reply to this post by Nathan Ridge via cfe-dev
Tom

I attempted to use `git llvm push` with the test-suite repository (which isn’t moving to the monorepo) and it didn’t work. I presume this was expected.

It is slightly infuriating that most of the documentation as to how to use the SVN repositories has vanished (which is still relevant to contributing to test-suite and lnt), and it seems there is little guidance about what these repos will do when the monorepo moves to git and GitHub.

More clarity on the situation for these repos, and the tooling that’s expected to be used with them, would be useful.

Sam

> On 12 Jul 2019, at 3:23AM, Tom Stellard via llvm-dev <[hidden email]> wrote:
>
> Hi,
>
> We are still on track to retire SVN and complete the transition to GitHub
> by Oct 21, 2019 (This year's US Dev Meeting).
>
> Even though this 3+ months away, it is very important that you begin to migrate
> your workflows to GitHub as soon as possible.  For developers, this means using
> the git-llvm script to commit changes and for CI systems or other read-only use
> cases can begin fetching code directly from GitHub.
>
> I have created a migration status page, so you can track the progress of the migration:
> http://llvm.org/GitHubMigrationStatus.html  There is also a link to instructions for
> how to use the git-llvm script for committing changes.
>
> If you would like to help with any of the TODOs on that page, please comment on the
> bugzilla associated with the task.
>
> Thanks,
> Tom
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

--
Sam Elliott
Software Developer - LLVM
lowRISC CIC
[hidden email]
--





_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
In reply to this post by Nathan Ridge via cfe-dev

This got fixed by https://reviews.llvm.org/D58157, btw.

 

From: llvm-dev <[hidden email]> on behalf of Justin Clift via llvm-dev <[hidden email]>
Reply-To: Justin Clift <[hidden email]>
Date: Friday, July 12, 2019 at 2:08 AM
To: Nicolai Hähnle-Montoro <[hidden email]>
Cc: llvm-dev <[hidden email]>, LLDB Dev <[hidden email]>, cfe-dev <[hidden email]>, "openmp-dev ([hidden email])" <[hidden email]>
Subject: Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

 

On 2019-07-12 17:41, Nicolai Hähnle-Montoro via llvm-dev wrote:

On Fri, Jul 12, 2019 at 4:24 AM Tom Stellard via llvm-dev

<[hidden email]> wrote:

We are still on track to retire SVN and complete the transition to

GitHub

by Oct 21, 2019 (This year's US Dev Meeting).

Even though this 3+ months away, it is very important that you begin

to migrate

your workflows to GitHub as soon as possible.  For developers, this

means using

the git-llvm script to commit changes and for CI systems or other

read-only use

cases can begin fetching code directly from GitHub.

The migration isn't just about moving from SVN to Git. For many folks,

it's also about moving from individual component repository to the

monorepo.

What's the experience people have had with that move? What works and

what doesn't?

 

One gotcha was the automatic blind inclusion of "clang extra tools"

when building clang (eg `-DLLVM_ENABLE_PROJECTS="clang;lld"`).

 

This caused linker problems (trying to build a static lib), which we

weren't able to solve in a few hours of looking.

 

Instead, the undocumented flag `-DLLVM_TOOL_CLANG_TOOLS_EXTRA_BUILD=OFF`

can be added to the CMake line to turn off building those extra tools.

 

With that flag added things worked. :)

 

+ Justin

 

 

Cheers,

Nicolai

_______________________________________________

LLVM Developers mailing list

 


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
In reply to this post by Nathan Ridge via cfe-dev
On Fri, Jul 12, 2019 at 10:35 AM Sam Elliott via llvm-dev <[hidden email]> wrote:
Tom

I attempted to use `git llvm push` with the test-suite repository (which isn’t moving to the monorepo) and it didn’t work. I presume this was expected

 
It is slightly infuriating that most of the documentation as to how to use the SVN repositories has vanished (which is still relevant to contributing to test-suite and lnt), and it seems there is little guidance about what these repos will do when the monorepo moves to git and GitHub. 

The plan is for these repos to live on github as well, the same way they are laid out currently in the github project. E.g. test-suite lives in https://github.com/llvm/llvm-test-suite).


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [lldb-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
In reply to this post by Nathan Ridge via cfe-dev
Hi Tom,

Thanks for driving this!  It's a big project and it's great to see
the progress being made on it. My org's adaptation to the monorepo
is in progress as we speak.

I had two hopefully easy questions.
1) Can we get a link to the status page from the llvm.org front page?
   That will make it a lot easier to find in the future.
2) I assume everyone will need to have a GitHub account; is there any
   story needing to be told about correlating a GitHub account with
   our current SVN IDs?  I don't even have a GH account at this point,
   don't know what's involved in signing up.

Thanks,
--paulr

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [lldb-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
On 07/12/2019 10:29 AM, [hidden email] wrote:
> Hi Tom,
>
> Thanks for driving this!  It's a big project and it's great to see
> the progress being made on it. My org's adaptation to the monorepo
> is in progress as we speak.
>
> I had two hopefully easy questions.
> 1) Can we get a link to the status page from the llvm.org front page?
>    That will make it a lot easier to find in the future.

Sure, I just added a link.

> 2) I assume everyone will need to have a GitHub account; is there any
>    story needing to be told about correlating a GitHub account with
>    our current SVN IDs?  I don't even have a GH account at this point,
>    don't know what's involved in signing up.

We are still working on a process for mapping SVN accounts to GitHub accounts.
I will provide an update once we have something finalized.

-Tom

>
> Thanks,
> --paulr
>

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev
In reply to this post by Nathan Ridge via cfe-dev
I've found that for first-time users (myself included) it's easy to accidentally commit a series of SVN commits with git llvm push.  If we expect that a lot of folks will be switching over, might it be worth adding a warning to the script when more than one commit will be pushed?

On Fri, Jul 12, 2019 at 12:48 PM James Y Knight via cfe-dev <[hidden email]> wrote:
On Fri, Jul 12, 2019 at 10:35 AM Sam Elliott via llvm-dev <[hidden email]> wrote:
Tom

I attempted to use `git llvm push` with the test-suite repository (which isn’t moving to the monorepo) and it didn’t work. I presume this was expected

 
It is slightly infuriating that most of the documentation as to how to use the SVN repositories has vanished (which is still relevant to contributing to test-suite and lnt), and it seems there is little guidance about what these repos will do when the monorepo moves to git and GitHub. 

The plan is for these repos to live on github as well, the same way they are laid out currently in the github project. E.g. test-suite lives in https://github.com/llvm/llvm-test-suite).

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Nathan Ridge via cfe-dev


On Tue, Jul 16, 2019 at 12:42 PM Yitzhak Mandelbaum via cfe-dev <[hidden email]> wrote:
I've found that for first-time users (myself included) it's easy to accidentally commit a series of SVN commits with git llvm push.  If we expect that a lot of folks will be switching over, might it be worth adding a warning to the script when more than one commit will be pushed?

I sent this tentative patch: https://reviews.llvm.org/D64893

-- 
Mehdi

 

On Fri, Jul 12, 2019 at 12:48 PM James Y Knight via cfe-dev <[hidden email]> wrote:
On Fri, Jul 12, 2019 at 10:35 AM Sam Elliott via llvm-dev <[hidden email]> wrote:
Tom

I attempted to use `git llvm push` with the test-suite repository (which isn’t moving to the monorepo) and it didn’t work. I presume this was expected

 
It is slightly infuriating that most of the documentation as to how to use the SVN repositories has vanished (which is still relevant to contributing to test-suite and lnt), and it seems there is little guidance about what these repos will do when the monorepo moves to git and GitHub. 

The plan is for these repos to live on github as well, the same way they are laid out currently in the github project. E.g. test-suite lives in https://github.com/llvm/llvm-test-suite).

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev