Jenkins-CI support? about appengine-maven-plugin HOT 4 CLOSED

Good question.  A colleague of mine answered something similar on stack 
overflow in which a similar solution can be used : 
http://stackoverflow.com/questions/12983110/appengine-java-command-line-deploy-r
efresh-token .

The maven plugin uses oauth2 by default for authentication.  So if you do an 
appengine:update from your local machine (or any goal, except devserver), you 
will generate the '.appcfg_oauth2_tokens_java', if you then copy that to the 
home directory of the user running your jenkins job (the jenkins user 
commonly), you should be able to get this working for you.

Let me know if this works.

This didnt work nicely for me, I had to log in to the machine running jenkins. 
I started an update job in the remote machine and my current machine. I was 
logged into our jenkins apps account and when i was sent to a link on my local 
machine I accepted the app engine notice grabbed the id and then copy pasted 
this to my remote machine running jenkins during the same phase of the job on 
the remote machine.

This generated an oauth token for my remote machine and allowed my jobs to work 
correctly.

I initially tried to copy over the .oauth token from my local machine would 
error out on the jenkins job. My thought is some fingerprint on the machine is 
used with the id used from the oauth url to generate the oauth token.

If this is done. How does it work?

How did you get a link on jenkins account? I got nothing in console