Sent: Thursday, May 10, 2012 12:08 AM
To: [email protected]
Cc: 'Saros'
Subject: Re: [Dpp-devel] Commit History is broken
Hi Franz,
I'm not sure whether your phrases "great improvement" and "very good
job" are to be taken ironically ...
This was not ironic
Yes,
currently we do not need the chaining mechanism as every Job will be build,
because Jenkins will trigger this Job, because it just polls the repo,
where all
components are stored.
You already mentioned that stuff. With SVN it was a little bit easier.
Just poll a
subdirectory, I know that t
!
>
> Franz
>
>
> -Original Message-
> From: Stefan Rossbach [mailto:[email protected]]
> Sent: Wednesday, May 09, 2012 2:13 AM
> To: Saros
> Subject: [Dpp-devel] Commit History is broken
>
> During the migration from SVN to GIT, the commit history of separate
> c
e-
From: Stefan Rossbach [mailto:[email protected]]
Sent: Wednesday, May 09, 2012 2:13 AM
To: Saros
Subject: [Dpp-devel] Commit History is broken
During the migration from SVN to GIT, the commit history of separate
components (Saros, Whiteboard)
were / are still broken.
You will always read the
On 05/09/2012 02:13 AM, Stefan Rossbach wrote:
Hi,
the subject scared me. You are talking about the Jenkins triggers and that we
can not match a path inside the commit. So a change to .raus will trigger a
build of nebula right now?
We can look into using the 'url' trigger mechanism and write a s
During the migration from SVN to GIT, the commit history of separate
components (Saros, Whiteboard)
were / are still broken.
You will always read the whole changelog for any Jenkins Job, even if
the build for this component has
not affected any files of this Job (e.g you will read changes in the
