[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2019-07-29 Thread 'Harmit Rishi (Cloud Platform Support)' via Google App Engine
Hello, In an attempt to isolate the issue, would you be able to set "app_start_timeout_sec" to the max? The max is 1800, you may try it again once set. Also, this will help rule out if the issue is due to app initialization or not. You may find further information about this here

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2019-07-26 Thread 'GCP Microloan' via Google App Engine
Hello Daniel , I am trying to deploy appengine-web.xml and cron.yaml together PFB my pom.xml portaldata False true ${java.io.tmpdir}/appengine-staging

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-04-04 Thread Luckyy
thanks a lot for your help man!! now it running !! :-) On Tue, Apr 4, 2017 at 3:43 PM, Daniel Garrido wrote: > I skipped this information from Brian. How to run appcfg from the command > line: > > [1] appcfg.sh is from the App Engine SDK for Java >

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-04-04 Thread Daniel Garrido
I skipped this information from Brian. How to run appcfg from the command line: [1] appcfg.sh is from the App Engine SDK for Java and not included in the Google Cloud SDK. But it's a simple wrapper around a jar that is

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-04-04 Thread my self lky
Thanks Daniel!! i ran this appcfg command!! but my cron job is not getting uploded!! i dont know why!! On Tue, Apr 4, 2017 at 3:38 PM, Daniel Garrido wrote: > Hi, > > I ran appcfg from the command line. You will have to use appcfg.cmd > included in the java app engine

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-04-04 Thread Daniel Garrido
Hi, I ran appcfg from the command line. You will have to use appcfg.cmd included in the java app engine sdk. It seems that it is not included in the cloud sdk. At least, I wasn't able to find it. This point doesn't seem very clear in the documentation. Inside eclipse, I followed the

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-04-01 Thread my self lky
hi daniel!! same thing is happening with me!! corn job not being uploded!! what to do?? where to run this appcfg command in eclipse?? im using eclipse!! its a gwt project!! please tell me how to make it work? thanx in advance! On Wednesday, March 15, 2017 at 3:05:19 AM UTC+5:30, Daniel

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-04-01 Thread my self lky
hii Brian!! my corn job is not getting uploded! my corn.xml cornservlet.java and web.xml are fine! im not able to get how to trigger corn service?? ! im not getting uploding corn job message in my console page!! what should i do?? i even dont know how to run appcfg.sh command and where to run

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-03-31 Thread Brian de Alwis
Jason, This will be fixed in the next release of Cloud Tools for Eclipse. In the meantime you should be able to use the `appcfg.sh` command [1] to upload your cron.xml (`appcfg.sh help update_cron`) and `queue.xml` (`appcfg.sh help update_queues`). You'll need to use the `-A` argument to

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-03-31 Thread Jason
What if you are not using a Maven-based project? I created a non-maven project and it is not uploading my queue.xml or cron.xml either. On Wednesday, March 15, 2017 at 3:23:46 AM UTC-7, Nicola Spreafico wrote: > > If you're using a Maven-based project, by default implementation of the > Maven

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-03-23 Thread 'Nicholas (Google Cloud Support)' via Google App Engine
It seems like the first option does not consult your configuration with specified *deployables*. It is thus likely consulting a different maven goal. On Wednesday, March 15, 2017 at 4:17:12 PM UTC-4, Daniel Garrido wrote: > > Thank you very much Nicola, > > It worked with minor modifications!

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-03-15 Thread Daniel Garrido
Thank you very much Nicola, It worked with minor modifications! My final configuration is as follows: True true ${java.io.tmpdir}/appengine-staging ${java.io.tmpdir}/appengine-staging/app.yaml

[google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

2017-03-15 Thread 'Nicola Spreafico' via Google App Engine
If you're using a Maven-based project, by default implementation of the Maven Plugin only the app.yaml file (the application itself) is deployed. If you need to deploy the *cron*, *queue *and *index *as well, you need to configure the deployables configuration with all the files Please see this