Re: [Artifactory-users] How to get Hudson build information from Artifactory with REST?

Noam Y. Tenne Thu, 07 Jan 2010 05:05:40 -0800

Is there anything on the tomcat request logs from the deployment?


Lóránd Somogyi wrote:

I manged to do as you suggested, on an other (new) project.

From hudson log:

-----------------------------------------cut -----------------------------------------Jan 7, 2010 1:39:37 PM hudson.model.Run run

INFO: a-ui1 #6 main build action completed: SUCCESS

Jan 7, 2010 1:39:37 PMorg.apache.http.impl.client.AbstractAuthenticationHandler selectScheme

WARNING: Authentication scheme ntlm not supported

Jan 7, 2010 1:39:37 PMorg.apache.http.impl.client.AbstractAuthenticationHandler selectScheme

WARNING: Authentication scheme ntlm not supported

Jan 7, 2010 1:39:37 PMorg.apache.http.impl.client.AbstractAuthenticationHandler selectScheme

WARNING: Authentication scheme ntlm not supported
Jan 7, 2010 1:39:38 PM net.sf.json.JSONObject _fromBean
WARNING: Property 'startedDate' has no read method. SKIPPED

Jan 7, 2010 1:39:38 PMorg.apache.http.impl.client.AbstractAuthenticationHandler selectScheme

WARNING: Authentication scheme ntlm not supported
Jan 7, 2010 1:39:46 PM hudson.model.Run run
INFO: a-ui2 #7 main build action completed: FAILURE

-----------------------------------------cut -----------------------------------------I've highlighted the part I think is relevant. The strange is that thejob build is successful.



Artifactory log:

-----------------------------------------cut -----------------------------------------2010-01-07 13:39:37,811 [pool-1-thread-1027] [INFO ](o.a.s.a.ArchiveIndexer:91) - The content of the archive:'a-ui1-2.0.9-SNAPSHOT.jar' was indexed successfully2010-01-07 13:39:38,164 [pool-1-thread-1028] [INFO ](o.a.s.a.ArchiveIndexer:91) - The content of the archive:'a-ui1-2.0.9-SNAPSHOT-sources.jar' was indexed successfully-----------------------------------------cut -----------------------------------------

Apache httpd log:

-----------------------------------------cut ----------------------------------------------------------------------------------cut -----------------------------------------(none at all, from any for that time window)

Regards,Lóránd Somogyi

http://lorands.com
http://photols.com

On Tue, Jan 5, 2010 at 3:02 PM, Noam Y. Tenne <[email protected]<mailto:[email protected]>> wrote:


    I'm thinking maybe the tag parameters are being filtered somehow
    on the way to Artifactory.
    Please try to delete the artifacts and build infos in question,
    perform clean build and publish from Hudson and attach the tomcat
    and the httpd (if behind one) request logs from the time of
    deployment.
    If there is any sensitive information in the logs, you can send it
    directly to our [email protected] <mailto:[email protected]>.


    Lóránd Somogyi wrote:

    There are some differences, but in both cases I get 404

    For (Hudson deploy to this one:):
    
http://maven/*snapshots*/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar:properties


          HTTP Status 404 - metadata not found

    For* *
    
http://maven/*repo*/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar:properties

        *


          HTTP Status 404 - Artifact not found:
          
com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar:properties

        *




    On Tue, Jan 5, 2010 at 1:55 PM, Noam Y. Tenne <[email protected]
    <mailto:[email protected]>> wrote:

        I noticed that you make the request through "repo". Do you
        still get a 404 if you make the request directly through the
        repo that the artifact is stored in?
        That is, say it's stored in "libs-snapshots-local", change
        the request from:


        
http://maven/repo/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar:properties*

        *
        To:

        
http://maven/libs-snapshots-local/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar
        
<http://maven/repo/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar>:properties



        Lóránd Somogyi wrote:


        Age: 0d 1h 59m 19s @ Jan 5. 1:15 --> Looks just fine.



        On Tue, Jan 5, 2010 at 1:01 PM, Noam Y. Tenne
        <[email protected] <mailto:[email protected]>> wrote:

            And how about the age of the artifact itself, not the
            build info (viewable by selecting the artifact in the
            browse tree. The "Age" field under the "General" tab).
            Does it comply too?


            Lóránd Somogyi wrote:

            Hi!

            Sure:

                * snapshot policy: Non-Unique
                * Hudson build time: Jan 5, 2010 11:15:35 AM

<http://hudson/job/a-dal/8/>* Artifactory build TS: 2010-01-05T11:15:35.619+0100


            Based on TS, it is the same one. Is the snapshot policy OK?

Regards,

            Lóránd Somogyi
            http://lorands.com
            http://photols.com


            On Tue, Jan 5, 2010 at 12:36 PM, Noam Y. Tenne
            <[email protected] <mailto:[email protected]>> wrote:

                Hi

                Could you please specify the snapshot policy that's
                being used in the repository that you deploy to?
                Also, you can make sure that the artifact wasn't
                overridden by checking that the artifact's deployer
                is the one used by Hudson, and that the artifact's
                age complies with the time Hudson deployed it.


                Noam

                Lóránd Somogyi wrote:

Hi!

I can only see maven-metadata.xml under Metadata tab.The artifact is published with hudson, through

                Hudson Artifactory plugin, relevant part from the
                Hudson job log:

                ---------------------------------
                cut ---------------------------------
                Deploying artifacts to http://maven/
                Deploying artifacts of module: com.example.mvn.test.a:a-dal
                Deploying artifact: 
http://maven//snapshots/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar;build.name=a-dal;build.number=8
                Deploying artifact: 
http://maven//snapshots/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.pom;build.name=a-dal;build.number=8
                Deploying artifact: 
http://maven//snapshots/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT-sources.jar;build.name=a-dal;build.number=8
                Deploying build info to: http://maven//api/build
                Finished: SUCCESS
                ---------------------------------
                cut ---------------------------------

What do I do wrong?Regards,

                Lóránd Somogyi
                http://lorands.com
                http://photols.com


                On Tue, Jan 5, 2010 at 12:01 PM, Noam Y. Tenne
                <[email protected] <mailto:[email protected]>> wrote:

                    Hi

                    Can you please make sure that the artifact is
                    actually tagged? This can be done by viewing
                    the Metadata tab in the UI. The properties XML
                    should appear in the list of types.
                    If it's not tagged, maybe this specific
                    artifact was published by maven, or overridden

in some way?

                    HTH

                    Noam

                    Lóránd Somogyi wrote:

                    Hi!

                    Happy New Year to You too! And to ALL!

                    Now, with AF 2.1.3 I get 404 if I add an
                    extra ":properties" after the artifact (which
                    I can download). For example:

                    
http://maven/repo/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar
                     -- downloads the JAR

                    
http://maven/repo/com/example/mvn/test/a/a-dal/3.2.0-SNAPSHOT/a-dal-3.2.0-SNAPSHOT.jar*:properties*
                    -- *I get 404*

                    As you can see I'm running AF from within

Tomcat (6) ROOT context.I see no extra information in the log. The

                    given artifact is built by Hudson, and I can
                    see the informations under the Build menu.

                    Any hint?

thx,Lóránd Somogyi

                    http://lorands.com
                    http://photols.com


                    On Tue, Jan 5, 2010 at 10:51 AM, Noam Y.
                    Tenne <[email protected]
                    <mailto:[email protected]>> wrote:

                        Hi there

                        It's possible to get the properties of a
                        certain artifact by a simple HTTP GET method:

                        
http://myhost/artifactory/myrepo/group/artifact/version/artifact-version.jar*:properties

                        *This will return the XML of the
                        artifact's properties.

                        Have fun and an happy new year

                        Noam

                        Lóránd Somogyi wrote:

                        Hi!

                        I would like to know if there is a way
                        to get Hudson build properties, like
                        build number, from Artifactory. The goal
                        would be to get a build number for a
                        specified artifact (a snapshot) with

simple REST method.

                        thx
                        Lóránd Somogyi
                        http://lorands.com
                        http://photols.com
                        
------------------------------------------------------------------------

                        
------------------------------------------------------------------------------
                        This SF.Net email is sponsored by the Verizon Developer 
Community
                        Take advantage of Verizon's best-in-class app 
development support
                        A streamlined, 14 day to market process makes app 
distribution fast and easy
                        Join now and get one step closer to millions of Verizon 
customers