Cross project atomic commits

[Wink Saville]

What is the status of cross project atomic commits? This is

one of the solutions to reduce the number of build breakages and

syncing to bad builds. It also seems to be necessary for an

effective presubmit queue.

-- Wink

[Martin Fick]

removed
"android-git-discuss" <android-g...@google.com>

As far as Gerrit is concerned, here are the in progress
changes:

https://gerrit-
review.googlesource.com/#/q/status:open+project:gerrit+branch:master+topic:cross-
repo-dependencies,n,z

Good progress was being made, but it still needs some work,

-Martin

--
Employee of Qualcomm Innovation Center, Inc. which is a
member of Code Aurora Forum

[Åsmund Østvold]

I am investigating Gerrit and I am unsure about what a "project" in your terminological.  So my question is:

Will a API change that require more then one git repository to change be possible to approved as one change(set)?

My goal is to be able to do automatic code review (+1) and verification with builds and integration tests in our Jenkins CI environment.  I was hoping that the git-repo tool would enable the needed behavior.  I do not need cross git-repo manifest file automation. 

Is this possible before the blow change is implemented. If not, will it be possible after the below change is implemented?

Asmund

 

PS. Dyslectic mistakes may be present in the text. 

--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

[Magnus Bäck]

On Mon, Feb 20, 2012 at 3:53 EST,
Åsmund Østvold <asm...@gmail.com> wrote:

> I am investigating Gerrit and I am unsure about what a
> "project" in your terminological.

project == Git repository

> So my question is:
>
> Will a API change that require more then one git repository to
> change be possible to approved as one change(set)?

This is currently not possible. Sorry.

> My goal is to be able to do automatic code review (+1) and
> verification with builds and integration tests in our Jenkins CI
> environment.  I was hoping that the git-repo tool would enable
> the needed behavior.  I do not need cross git-repo manifest
> file automation.
>
> Is this possible before the blow change is implemented. If
> not, will it be possible after the below change is
> implemented?

I believe so, but I haven't looked into the details of this patch
series.

--
Magnus Bäck
ba...@google.com

[Martin Fick]

"Åsmund Østvold" <asm...@gmail.com> wrote:

>I am investigating Gerrit and I am unsure about what a "project" in
>your terminological. So my question is:
>
>Will a API change that require more then one git repository to change
>be possible to approved as one change(set)?
>
>My goal is to be able to do automatic code review (+1) and verification
>with builds and integration tests in our Jenkins CI environment. I was
>hoping that the git-repo tool would enable the needed behavior. I do
>not need cross git-repo manifest file automation.
>
>Is this possible before the blow change is implemented. If not, will it be
>possible after the below change is implemented?
>

To better understand what will and what will not be possible you should search the mailing list for the cross repo dependency threads started by the author of that change since December. It is not a simple yes or no answer.

Employee of Qualcomm Innovation Center,Inc. which is a member of Code Aurora Forum

[Åsmund Østvold]

Thank you Martin

That thread seems to require at least two cops of coffee and some time.

Asmund