On Tue, Oct 29, 2013 at 8:28 AM, random <[email protected]> wrote:
> Jenkins is great at making it obvious when a code change causes a test
> failure.
> It's less great when other things cause a test failure, like database
> changes or dependency changes.
>
> How can we have changes to these artifacts appear in the 'Recent changes'
> list?
> By artifacts I mean things like:
>
> The SQL file we use to create our blank database before each test run
> The text file into which we pipe all the versions of installed dependencies
> before each test run
>
> I have heard about the Artifact Diff Plugin, but I suspect that would _not_
> make artifacts as integrated as code changes are, so we would still have to
> click through manually every time to see if something changed. I'm looking
> for an automated/integrated solution so that Jenkins itself "knows" when an
> artifact has changed, and can make that obvious to users like it does for
> code changes.
The obvious thing is to push all of the things where you want to track
changes into your version control system so you get the changes logged
and listed in the same places as the code. If you are using
subversion, you can use externals to pull in components from different
repositories or paths so you don't actually have to store everything
in the same tree. Not sure how that text file of dependencies is
being created, but shouldn't that be something you know ahead of time
instead of building at runtime? If it has to do with component and
library versions, we handle that with svn externals too - controlling
the versioning by referencing tags.
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
