Hi Eli,
The versions of software we use are:
Jenkins - ver. 1.413
Artifactory plugin - 2.0.1
Artifactory pro - Artifactory 2.3.4 (rev. 13017)
We have one master node, 3 generic build servers, 5 unix servers running
oracle and 6 windows servers running SQLServer.
The parent and child are not likely to be on the same server and so I
believe will not have access to the local cache.
For the parent build
Incremental build - only build changed modules was enabled
Disable automatic artifact archiving
Plugin isolation is being used
Trigger parameterized build on other projects is used to trigger
downstream project
For the child build
Resolve artifacts from Artifactory
Incremental build - only build changed modules
Disable automatic artifact archiving
I've re-run with the -U on the child job this morning and have the same
issue.
>From the child log I can see that it is checking only the isolated area
in Artifactory using the modified build root.
I examined the isolated area for a failed job. There are two old
versions of the pom, checksum and jar from 8/7/2011. I am not sure why
these are present and not any newer versions. There is an up to date
maven-metadata.xml that correctly indicates the last built artifact;
this artifact is not in the isolated area, but is in the repository when
browsing.
When I examine a successful job, again there are two old versions and
the correct latest version in the isolated area.
What would you expect to see in the isolated area if a module is not
built for a job?
Thanks,
Dan
Log extract from the child build:
Downloading:
http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-ar
tifactory-21;/com/experian/eda/tallyman/izpack-common/3.8.0-SNAPSHOT/mav
en-metadata.xml
<http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;/com/experian/eda/tallyman/izpack-common/3.8.0-SNAPSHOT/ma
ven-metadata.xml>
Downloaded:
http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-ar
tifactory-21;/com/experian/eda/tallyman/izpack-common/3.8.0-SNAPSHOT/mav
en-metadata.xml
<http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;/com/experian/eda/tallyman/izpack-common/3.8.0-SNAPSHOT/ma
ven-metadata.xml> (374 B at 0.0 KB/sec)
Downloading:
http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-ar
tifactory-21;/com/experian/eda/tallyman/izpack-common/3.8.0-SNAPSHOT/izp
ack-common-3.8.0-20110719.160800-3.pom
<http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;/com/experian/eda/tallyman/izpack-common/3.8.0-SNAPSHOT/iz
pack-common-3.8.0-20110719.160800-3.pom>
[WARNING] The POM for
com.experian.eda.tallyman:izpack-common:jar:3.8.0-20110719.160800-3 is
missing, no dependency information available
Failed to execute goal on project configuration-installer: Could not
resolve dependencies for project
com.experian.eda.tallyman:configuration-installer:pom:3.8.0-SNAPSHOT:
Could not find artifact
com.experian.eda.tallyman:izpack-common:jar:3.8.0-20110719.160800-3 in
snapshots
(http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;
<http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;> )
cause : Could not resolve dependencies for project
com.experian.eda.tallyman:configuration-installer:pom:3.8.0-SNAPSHOT:
Could not find artifact
com.experian.eda.tallyman:izpack-common:jar:3.8.0-20110719.160800-3 in
snapshots
(http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;
<http://artifactory.tallyman.co.uk/libs-snapshot;build.root=3.8-native-a
rtifactory-21;> )
Dan Russell
Release Manager - EDA Collections
Tel: +44 (0) 1454 441015
Mob: +44 (0) 7870503538
________________________________
From: Eli Givoni [mailto:[email protected]]
Sent: 21 July 2011 09:09
To: [email protected]
Subject: Re: [Artifactory-users] Question on Jenkins Plugins and
Nativebuilds.
Hi Dan,
Some information if you please,
1. Which version of Jenkins/Artifactory Plugin and Artifactory OSS or
Pro are you using?
2. Did you split your build to sub modules that have different jobs in
Jenkins or did you turned on Incremental build - only build changed
modules?
3. If you did split your build, what triggers the downstream build? Are
you using the plugin Isolation feature?
Basically a version of the upstream module is deployed in artifactory
and in your local cache, you can run the downstream builds with the -U
flag to ensure the latest snapshot is downloaded from artifactory so if
your module dependency tree is correct, I don't see why it should not
work.
HTH,
Eli
The Artifactory team
On Wed, Jul 20, 2011 at 4:56 PM, Russell, Daniel
<[email protected]> wrote:
We use Jenkins and have recently started to use Maven and Artifactory.
What we are trying to achieve is to compile and unit test, then create a
distribution and then test that distribution with smoke tests to give
quick developer feedback. Once the test passes we would like to promote
the original build and use Maven release.
To make this as fast as possible I'd like to use a native Jenkins build
so that we only rebuild changed modules and remain sure that we are
testing the correct versions. It seemed that the Artifactory plugin
would make sure that I was testing the expected versions; however I'm
running into an issue.
The Parent job is a native Maven job using Artifactory plugin, executing
mvn install and snapshots versions.
A direct child native Maven job then creates a distribution deliverable
from modules in the parent.
It works fine if the parent job builds all modules, but if the parent
job doesn't have to build every then the child job can't find the
modules not built.
Do you need to build all modules every time, have I miss configured my
jobs or is there a better way of achieving what I want?
Thanks,
Dan
Information in this e-mail and any attachments is confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission. There is no intention to
create any legally binding contract or other binding commitment through
the use of this electronic communication unless it is issued in
accordance with the Experian Limited standard terms and conditions of
purchase or other express written agreement between Experian Limited and
the recipient. Although Experian has taken reasonable steps to ensure
that this communication and any attachments are free from computer
virus, you are advised to take your own steps to ensure that they are
actually virus free.
Companies Act information: Registered name: Experian Limited. Registered
office: Landmark House, Experian Way, NG2 Business Park, Nottingham,
NG80 1ZZ, United Kingdom. Place of registration: England and Wales.
Registered number: 653331
------------------------------------------------------------------------
------
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered
include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private
keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC can
improve internal communications as well as offer faster, more efficient ways
to interact with customers and streamline customer service. Learn more!
http://www.accelacomm.com/jaw/sfnl/114/51426253/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
