How to find WebRTC version?

[Leon Chen]

Dear all,

I just downloaded another version of WebRTC following https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md

How do I find the version of the WebRTC code?

I see this in third_party/webrtc/README.chromium:

Name: WebRTC
URL: http://www.webrtc.org
Version: 90
CPEPrefix: cpe:/a:webrtc_project:webrtc:90

Is the version of the code 90? But I saw the file of a version I downloaded 2 years has the same info. I am confused.

Thanks.

Leon

[Leon Chen]

Then I found in src/third_party/webrtc/docs/release-notes.md:

  ## Release note generation
  Release notes are generated by taking the git log between the respective
  [release branches](https://chromiumdash.appspot.com/branches) using
  ```
  git log branch-heads/5672..branch-heads/5735
  ```

  To find a branch associated with a particular release, refer to
  [the list of branches](https://chromiumdash.appspot.com/branches).

  ## List of releases
    * [M114 Release notes](https://groups.google.com/g/discuss-webrtc/c/GS-28AVIhg4/m/wGgWSt0TAgAJ)
    * [M113 Release Notes](https://groups.google.com/g/discuss-webrtc/c/imXxtjKJfIA/m/kTj9D_PtAQAJ)
    * [M112 Release Notes](https://groups.google.com/g/discuss-webrtc/c/V-XFau9W9gY/m/SF0n7sALEgAJ)

  ...

I see from https://chromiumdash.appspot.com/branches that 5735 corresponds to "Milestone 114" (M114) and what I downloaded is M114. But the latest release is M124! I don't understand why following the instruction https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md did not lead to downloading the latest release. Is this a bug? 

Thanks.

Leon

[Khun V]

https://webrtc.github.io/webrtc-org/native-code/development/ take a look at Working With Branches

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/4fb7b105-a85c-45a2-b84b-73f37db1cfcfn%40googlegroups.com.

[Hieu than hieu]

All, please take a look with some examples in javascript, nodejs to have easy look at how it works.
Google code is too complicated, I have wasted a long time trying to deploy their example.

Vào Th 3, 26 thg 3, 2024 vào lúc 09:07 Khun V <witaly...@gmail.com> đã viết:

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAFa3_%3D_J5XFp0NQJUtiZFzCbouOVXZWC14pHcvF%3Dq2Ua%3DZA4Hg%40mail.gmail.com.

[Leon Chen]

Thanks Khun! But according to this 2019 post https://groups.google.com/g/discuss-webrtc/c/JR7fsoEuqw0, the command at the link (how new is the info at the link?) you gave: git checkout -b my_branch refs/remotes/branch-heads/3987

was replaced by: git checkout refs/branch-heads/xyzw

I tried both and none of them worked, as shown below:

git checkout -b my_branch refs/remotes/branch-heads/6367
fatal: 'refs/remotes/branch-heads/6367' is not a commit and a branch 'my_branch' cannot be created from it

git checkout refs/branch-heads/6367
error: pathspec 'refs/branch-heads/6367' did not match any file(s) known to git

I checked the available branches:

git branch -a
* (HEAD detached at e99622c238)
  remotes/origin/main

Then updated with: git fetch --all

leading to a whopping 10GB download!

and checked again:

git branch -a
* (HEAD detached at e99622c2387d)
  remotes/origin/ignore/bar
  remotes/origin/ignore/foo
  remotes/origin/infra/config
  remotes/origin/lkgr
  remotes/origin/lkgr-android-internal
  remotes/origin/lkgr-ios-internal
  remotes/origin/main

Despite all these, I still got the same errors.

I don't understand why the instructions at the official site https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md do not lead to cloning the latest release. :(

Any suggestions?

Thanks.

Leon

[Leon Chen]

Thanks Khun for the info! Is the webpage at the link https://webrtc.github.io/webrtc-org/native-code/development/ up-to-date (the example refers to Chrome M80)? It uses this command: git checkout -b my_branch refs/remotes/branch-heads/3987

According to this 2019 post https://groups.google.com/g/discuss-webrtc/c/JR7fsoEuqw0, a new (?) command is used: git checkout refs/branch-heads/xyzw

However, neither worked for me, as shown below:

$git checkout -b my_branch refs/remotes/branch-heads/6367

fatal: 'refs/remotes/branch-heads/6367' is not a commit and a branch 'my_branch' cannot be created from it

$ git checkout refs/branch-heads/6367

error: pathspec 'refs/branch-heads/6367' did not match any file(s) known to git

A check of the branches showed

$ git branch -a

* (HEAD detached at e99622c238)
  remotes/origin/main

Then I did: git fetch --all, and got

$ git branch -a

* (HEAD detached at e99622c2387d)
  remotes/origin/ignore/bar
  remotes/origin/ignore/foo
  remotes/origin/infra/config
  remotes/origin/lkgr
  remotes/origin/lkgr-android-internal
  remotes/origin/lkgr-ios-internal
  remotes/origin/main

But I got the same errors. Honestly, I don't understand why following the instruction https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md did not clone the latest source code.

Any suggestions on what to do next?

Thanks.

Leon

On Monday, March 25, 2024 at 7:07:46 PM UTC-7 Khun V wrote:

[Bitto Niclavose]

Hi Leon, 

You can try fetch the branch-heads specifically and then checking out. In your case

```

git fetch origin refs/branch-heads/6367:refs/remotes/origin/branch-heads/6367

git checkout -b branch-6367 origin/branch-heads/6367
``` 

To get all refs
```

git ls-remote origin
```

To confirm you have the same commit check git log matches with 

https://webrtc.googlesource.com/src.git/+log/refs/branch-heads/6367

Thanks

Bitto Niclavose