@roshandawrani

for the question:
Did anything get checked out successfully under the workspace directory "
/scratch/jenkins/workspace/**cloudbees_doofry_jenkins_2"?

i actualy no way to verify if something is inside this directory as its
cloudbees that process the checkout operation from github (the project im
building is on github) during the build. Any idea how to check that even
its cloudbees who does the checkout operation ?


2013/6/14 roshandawrani <[email protected]>

> Did anything get checked out successfully under the workspace directory "
> /scratch/jenkins/workspace/**cloudbees_doofry_jenkins_2"? From the look
> of the error, it seems like that directory is still empty.
>
> Could be related to warning "There are multiple branch changesets here"
>
> -- Roshan
>
> On Friday, 14 June 2013 14:12:37 UTC+5:30, pedrospaulus wrote:
>>
>> HI every one,
>> im running a jenkins instance for a grails app build and deploy on
>> cloudbees ,but i am running into a problem now, somewhere during the buid
>> it tell me that my checkedout project (from github) is not a part of grails
>> application. The message logged is :
>>
>> *********************************
>> Started by GitHub push by xxxxxx
>> Building remotely on s-ea17527f in workspace /scratch/jenkins/workspace/*
>> *cloudbees_doofry_jenkins_2
>> Checkout:cloudbees_doofry_**jenkins_2 / 
>> /scratch/jenkins/workspace/**cloudbees_doofry_jenkins_2
>> - hudson.remoting.Channel@**3a1ecfab:s-ea17527f
>> Using strategy: Default
>> Last Built Revision: Revision 7d9e4790f577b6c4d3a53338653647**d1f1400701
>> (origin/HEAD, origin/master)
>> Fetching changes from 1 remote Git repository
>> Fetching upstream changes from origin
>> Seen branch in repository origin/HEAD
>> Seen branch in repository origin/master
>> Seen 2 remote branches
>> Commencing build of Revision 4716cf96f4edcc7eef3a4d6826ef3a**966aa9a670
>> (origin/HEAD, origin/master)
>> Checking out Revision 4716cf96f4edcc7eef3a4d6826ef3a**966aa9a670
>> (origin/HEAD, origin/master)
>> Warning : There are multiple branch changesets here
>> [cloudbees_doofry_jenkins_2] $ /opt/grails/grails-1.3.7/bin/**grails war
>> target/cloudbees_doofry.war --non-interactive
>> Welcome to Grails 1.3.7 - http://grails.org/
>> Licensed under Apache Standard License 2.0
>> Grails home is set to: /opt/grails/grails-1.3.7
>>
>> Base Directory: /scratch/jenkins/workspace/**cloudbees_doofry_jenkins_2
>> Resolving dependencies...
>> Dependencies resolved in 4346ms.
>> /scratch/jenkins/workspace/**cloudbees_doofry_jenkins_2 does not appear
>> to be part of a Grails application.
>> The following commands are supported outside of a project:
>>     add-proxy
>>     clear-proxy
>>     create-app
>>     create-plugin
>>     help
>>     list-plugins
>>     package-plugin
>>     plugin-info
>>     remove-proxy
>>     set-proxy
>> Run 'grails help' for a complete list of available scripts.
>> Build step 'Build With Grails' marked build as failure
>> Archiving artifacts
>> [cloudbees-deployer] Skipping deployment as build result is FAILURE
>> Sending e-mails to: xxxxxxxx
>> Finished: FAILURE
>> *********************************
>>
>> do someone already run into the kind of problem, any idea of what im
>> doing wrong ??
>> may be im at the wrong place can you play indicate me where to post those
>> kind of questions
>> I even dont know if it related to the grails framework (as it can be
>> spring, play etc ...)
>> thankx in advance.
>>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/bg2zpDt-5XE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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.


Reply via email to