Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SVN feature to get last-changed-revision and the current branch/tag/trunk name #2

Merged
merged 15 commits into from Sep 11, 2018
Merged

Conversation

climblinne
Copy link

complement to SVN issue-3130 of conan

…ag/trunk name

Change-Id: I0aa798a2bda23569ed93c139dc56ce62938edc6d
…e repository.

This is used for the translation from "auto" to "url@revision" in SCM-URL for Subversion.

Change-Id: I36d41ef5271e195c9d43269173990496733404ef
@climblinne
Copy link
Author

Add also peg revision to remote url.

@jgsogo
Copy link
Owner

jgsogo commented Sep 5, 2018

Ey! Thanks for the PR!

I was waiting for some feedback from the rest of the Conan team about my concerns here. But maybe we can discuss those here and come back there with some conclusions.

About the 3 points we have in the air:

  • peg revision. Completely ok. Although Git doesn't have it, we can easily add it in SVN. I will add a review to your PR with some comments now.
  • last commit: I still think that we need to ask for the last revision number to the root directory of the project in order to know that revision/version you talked about... We need to know at least the root directory of the checkout part (take a look at this PR, we need a SVN.get_repo_root() and ask to that folder for the last revision). I think that PR will we merged soon into develop.
  • branch: ok

conans/client/tools/scm.py Outdated Show resolved Hide resolved
conans/client/tools/scm.py Outdated Show resolved Hide resolved
conans/client/tools/scm.py Outdated Show resolved Hide resolved
conans/client/tools/scm.py Outdated Show resolved Hide resolved
…ue-3130

Change-Id: Iff2fdda89e7dd38eef27e5d1e1fc3b203b8909aa
Change-Id: I5d4a988b82c55b87afab94c00923490be8c3dd4d
Replace auto-keyword at export to url + peg revision for SVN. Git keeps the remote url.

Change-Id: I02a97e59123681478a38046e52d90d5b24456242
…r SVN & Git.

Change-Id: I6cbabd464feca02e5b6ba78099f8775f61f41d80
@climblinne
Copy link
Author

I added some changes to the code.
I still don't know, what you want to do with the SVN.get_repo_root().
When I use the last changed rev on the repo root it should be identical to the revision. But I would need the rev number of the current folder (in the SVN tree).

We have normally multiple repositories in one SVN repository, which uses different paths.

Change-Id: I97b0ad4cef164b1d1001c97e96305f8a54be238d
…ue-3130

Change-Id: I9c935f80b3d1f89407cba62f02b3565f1ae7a436
Copy link
Owner

@jgsogo jgsogo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change these details and I will merge the PR into mine so we can check against the test suite of Conan itself.

conans/client/tools/scm.py Outdated Show resolved Hide resolved
conans/client/tools/scm.py Outdated Show resolved Hide resolved
conans/client/tools/scm.py Show resolved Hide resolved
conans/client/cmd/export.py Show resolved Hide resolved
Change-Id: If0a6cbfd46de014045185a9a9825b6052c6fc2bc
Change-Id: Ia448a903a61f1c4a77c267652758653b2c6a74d4
…t_last_changed_revision`

Change-Id: I6a98787b2790547149e247c49015d5a50090b214
Complete `get_last_changed_revision` in SVN

Change-Id: Ia0882eee0d355f7cc060b15f8f99212f79d35532
@jgsogo
Copy link
Owner

jgsogo commented Sep 11, 2018

@climblinne , just waiting for my PR on your branch to be accepted ;D

https://github.com/climblinne/conan/pull/1

@jgsogo jgsogo merged commit 65ff4ef into jgsogo:issue-3130 Sep 11, 2018
jgsogo pushed a commit that referenced this pull request Nov 25, 2019
Merge code from conan.io
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants