"deploy" Goal does not cover queues #143
Comments
|
@NicolaSpreafico Sorry for the inconvenience. We will be introducing similar goals for this Maven plugin soon. In the mean time you can add the appengine-staging/queue.yaml to your list of deployables in your plugin config. (you'll also need to add the generated app.yaml if you want to deploy the application with it). |
|
@patflynn Thank you, I understand from the documentation that I need to use the Reading other issue like:
Please note that the I like very much the possibility of deploying ONLY the application and not the related files (cron, queue, ...) which with the previous deploy procedure was not possibile. You could the deploy only the queue/cron but not only the app. I also tried, as an example, to remove the Now that I successfully configured the Maven plugin I can choose file per file to deploy. |
|
Thanks for the detailed comments. We'll try to design it so that we
maintain the ability to deploy only the app without the related files.
…On Thu, Mar 2, 2017 at 2:41 AM, NicolaSpreafico ***@***.***> wrote:
@patflynn <https://github.com/patflynn> Thank you, I understand from the
documentation
<https://cloud.google.com/appengine/docs/standard/java/tools/maven-reference#appenginedeploy>
that I need to use the deployables parameter.
Reading other issue like:
- #89 (comment)
<#89 (comment)>
- #90
<#90>
- GoogleCloudPlatform/nodejs-getting-started#56
<GoogleCloudPlatform/nodejs-getting-started#56>
I now created a configuration like this (I configured app.yaml as well
as you suggested)
<plugin>
<groupId>com.google.cloud.tools</groupId>
<artifactId>appengine-maven-plugin</artifactId>
<version>${appengine.maven.plugin.version}</version>
<configuration>
<deploy.project>${app.id}</deploy.project>
<deploy.version>${app.version}</deploy.version>
<deploy.promote>False</deploy.promote>
<stage.enableJarClasses>true</stage.enableJarClasses>
<stage.stagingDirectory>${java.io.tmpdir}/appengine-staging</stage.stagingDirectory>
<deployables>
<param>${java.io.tmpdir}/appengine-staging/app.yaml</param>
<param>${java.io.tmpdir}/appengine-staging/cron.yaml</param>
<param>${java.io.tmpdir}/appengine-staging/queue.yaml</param>
<param>${java.io.tmpdir}/appengine-staging/index.yaml</param>
</deployables>
</configuration>
</plugin>
Please note that the stagingDirectory parameter was already there, I
configured the deployables param to follow that configuration.
I like very much the possibility of deploying ONLY the application and not
the related files (cron, queue, ...) which with the previous deploy
procedure was not possibile. You could the deploy only the queue/cron but
not only the app. I also tried, as an example, to remove the app.yaml
from the deploy and it works as well.
[INFO] GCLOUD: You are about to update the following configurations:
[INFO] GCLOUD: Updating config [cron]...
[INFO] GCLOUD: done.
[INFO] GCLOUD: Updating config [queue]...
[INFO] GCLOUD: done.
[INFO] GCLOUD: Updating config [index]...
[INFO] GCLOUD: done.
[INFO] GCLOUD:
[INFO] GCLOUD: Cron jobs have been updated.
[INFO] GCLOUD:
[INFO] GCLOUD: Task queues have been updated.
Now that I successfully configured the Maven plugin I can choose file per
file to deploy.
I can comment and uncomment the param lines in order to deploy only the
proper files (which is not very comfortable but at least can be done).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#143 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHf5HR7xdIKHYx-HLe62WEsEwL0biaWvks5rhnKMgaJpZM4MPYKo>
.
|
|
This doesn't work for cloud endpoints projects |
|
@boogie4eva deploying indexes and the app doesn't work for endpoints projects? |
|
@boogie4eva do you mean it's not deploying your endpoints config? |
|
@patflynn @loosebazooka |
|
@loosebazooka @meltsufin this issue seems pretty critical. What do you guys thinking about doing a fix release for gradle/maven ASAP? |
|
maven fix is going out the door, this doesn't affect gradle. I mean #144 |
|
Was this fixed? We're using v1.2.1 and deploy doesn't seem to update queues.xml for us. |
|
@depsypher the issue in this bug is fixed. If nothing in this issue works please open a new bug with your specific issue. |
|
It works with 1.0 .0 is it fixed for the latest release ?.
…On Sat, Mar 18, 2017, 6:31 PM Appu Goundan ***@***.***> wrote:
@depsypher <https://github.com/depsypher> the issue in this bug is fixed.
If nothing in this issue works please open a new bug with your specific
issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#143 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACL6DMgB-HZpnbH7n1nngLJwTC40r9RMks5rnBT9gaJpZM4MPYKo>
.
|
Hi,
I have a Java Maven-based project with the following file system
I noticed that the goal
com.google.cloud.tools:appengine-maven-plugin:deployonly deploy the application, thequeue.xmlis not handled. I discovered this because I created a new queue but during the deploy procedure the queue has been not created online (and I got an error for queue not defined)Is there an additional configuration required in order to deploy all the files? (application, queues, crons, ...)
The strange thing is that inside the staging directory i can see
appengine-staging/queue.yaml, in addition to the original fileappengine-staging/WEB-INF/queue.xmlAt the end in order to deploy the updated queue file I used the
com.google.appengine:appengine-maven-plugin:update_queuesgoal with the previous App Engine Maven pluginThe text was updated successfully, but these errors were encountered: