Dear Andrew,
Thnks fr ur reply. Atleast, can you plz tell us which jenkins
package/plugin we should use fr our existing GCE Debian?
I gave some links in my previous reply, plz its very hard to
select the package with the right PHP plugins.
HoW will we know which package/plugins to install and which
will support the google plugin or which one will support Google Auto deploy
function? Totally we are blank. R u telling
that only people, who use 'Click to deploy' solution can use
Google's above 'Push to Deploy' method? If so, its really hard for those
who cannot use that option?
That said, why Google doesn't support multiple 'Click to
deploy' solutions under a same given GCE instance?
Plz help Andrew.
BR,
Ss
On Friday, May 29, 2015 at 2:05:16 AM UTC+8, Andrew Jessup wrote:
>
> Hi SS,
>
> We've only tested this with the documentation provided at
> https://cloud.google.com/tools/repo/push-to-deploy
>
> which describes how to create a new Jenkins instance with the appropriate
> plugins and tools already installed. You may be able to re-use a different
> Jenkins instance to work with these instructions, or update one to use the
> same plugins and tools, but we don't have instructions for doing so at this
> time.
>
> As for unit testing instructions for PHP, we will aim to to provide some
> shortly. We will likely need to update the image described in the
> documentation to do this however since we don't install PHPUnit by default.
>
> On Wednesday, 27 May 2015 21:59:43 UTC-7, SS wrote:
>>
>> Dear Andrew,
>> Thnks fr ur reply. We ll test it. We already have a
>> GCE(Debian Linux) running w LAMP stack.
>>
>> So, should I install the below bitnami jenkins under GCE
>> Debian platform to proceed further, since i cant use a second time 'Click
>> to deploy JENKINS' under the same GCE instance
>> https://bitnami.com/stack/jenkins/installer
>>
>> Also which plugins should I use for jenkins? Should I use the
>> below one or use a specific PHP plugin fr Jenkins?
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Google+Source+Plugin
>> http://jenkins-php.org/
>>
>> As you mentioned, should I ignore these below steps fr BUILD
>> & TEST under PHP deployements:
>>
>>
>>
>>
>>
>> *Python If you have have implemented unit tests for your app,
>> do the following: Select Execute Shell.
>> Enter the following in the Command text field:
>> nosetests --with-xunit --xunit-file=nosetests.xml*
>>
>> Is so, how my PHP App will be auto built and tested(PHPUnit fr eg.)
>> like xunit in Python?
>>
>> Thnks in advance fr ur help, very eager to setup this jenkin fr our
>> dozens of PHP APP in GAE.Hope u ll help us.
>> SS
>>
>>
>> On Thursday, May 28, 2015 at 9:02:37 AM UTC+8, Andrew Jessup wrote:
>>>
>>> Hi SS, thanks for your patience. I've done some testing, you should be
>>> able to deploy PHP applications using Jenkins by following the instructions
>>> at:
>>>
>>> https://cloud.google.com/tools/repo/push-to-deploy
>>>
>>> These don't explicitly say how to deploy a PHP application, but
>>> fortunately it's exactly the same as for python apps (except for the "Build
>>> and Test" step, which will not work - but you can also safely ignore).
>>>
>>> We'll get the documentation updated to describe how to deploy PHP
>>> applications shortly.
>>>
>>> On Friday, 22 May 2015 21:37:57 UTC-7, SS wrote:
>>>>
>>>> Thnks Andrew fr ur instant reply.We are waiting eagerly for this news
>>>> update.
>>>>
>>>> Thnks,
>>>> Ss
>>>>
>>>> On Friday, May 22, 2015 at 10:57:34 PM UTC+8, Andrew Jessup wrote:
>>>>>
>>>>> Hi SS, we're testing PHP with Jenkins right now. I'll update this
>>>>> thread as soon as we've fixed up the documentation.
>>>>>
>>>>> On Fri, May 22, 2015 at 4:31 AM, SS <sarathbab...@ssomens.com> wrote:
>>>>>
>>>>>> Dear Brad,
>>>>>> I just saw this. I have a PHP app deployed in GAE,
>>>>>> can I use JENKINS?
>>>>>> Does Jenkins supports PHP app AUTO deployment for GAE?
>>>>>>
>>>>>> Currently, I see only, JAVA, PY, GO support in the documentation.
>>>>>> Can you please clear this?
>>>>>>
>>>>>> Thnks,
>>>>>> Ss
>>>>>>
>>>>>> On Saturday, March 7, 2015 at 1:23:28 AM UTC+8, Brad Abrams wrote:
>>>>>>>
>>>>>>> We really want to enable that use case. The infrastructure we used
>>>>>>> for that in the past has proven to not meet our reliability
>>>>>>> requirements,
>>>>>>> so we are actively building a replacement. As soon as that replacement
>>>>>>> is
>>>>>>> ready, we will re-enable this functionality.
>>>>>>>
>>>>>>> ..brad
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Mar 6, 2015 at 9:18 AM Dustin Hoffmann <dustin...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hey Brad, my use case is this: I have a new html/css/js based
>>>>>>>> single page app that I am hosting on Google Cloud. The old pipeline ui
>>>>>>>> is
>>>>>>>> now gone, and I am not a fan of Jenkins. All I want to do is have a
>>>>>>>> simple
>>>>>>>> deploy on git push like it was previously. Is this possible for me?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wednesday, March 4, 2015 at 11:02:03 PM UTC-6, Brad Abrams wrote:
>>>>>>>>
>>>>>>>>> Thanks for following up -- I am sorry this is confusing.
>>>>>>>>>
>>>>>>>>> For Java developers, we recommend you use Jenkins as we describe
>>>>>>>>> here:
>>>>>>>>> https://cloud.google.com/tools/repo/push-to-deploy
>>>>>>>>>
>>>>>>>>> does that help?
>>>>>>>>>
>>>>>>>>> ..brad
>>>>>>>>>
>>>>>>>>> On Wed, Mar 4, 2015 at 8:52 PM <bergstrom...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>> Sorry I'm a bit confused as of how to exactly deploy a project.
>>>>>>>>>>
>>>>>>>>>> For existing projects I always used "git push origin master" to
>>>>>>>>>> push-and-deploy. How would existing projects do that now? Will they
>>>>>>>>>> continue to work? It seems as from yesterday this stopped working
>>>>>>>>>> (but then
>>>>>>>>>> I heard that it started working again...) It would be nice to know
>>>>>>>>>> the
>>>>>>>>>> official stance on this, if it *should* work or not.
>>>>>>>>>>
>>>>>>>>>> For new projects, we just have to use Jenkins, right? Or is there
>>>>>>>>>> another way? That email, which we also received, stated that "gcloud
>>>>>>>>>> app
>>>>>>>>>> update" would work to deploy, but I don't think that's a working
>>>>>>>>>> command at
>>>>>>>>>> all. Please shed some light.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tuesday, February 3, 2015 at 12:48:53 PM UTC+9, Brad Abrams
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks for all your feedback on this change. We heard from many
>>>>>>>>>>> of you that, while the Jenkins-based solution we offer works
>>>>>>>>>>> <https://cloud.google.com/tools/repo/push-to-deploy>well for
>>>>>>>>>>> larger projects with dedicated build and test steps, it works much
>>>>>>>>>>> less
>>>>>>>>>>> well for more simple projects with no build or test steps.
>>>>>>>>>>>
>>>>>>>>>>> To that end, we are going to continue to support push to deploy
>>>>>>>>>>> for existing projects that don’t require build or test. For
>>>>>>>>>>> example,
>>>>>>>>>>> python or php applications code be pushed to the git repo and will
>>>>>>>>>>> be
>>>>>>>>>>> deployed to app engine just as it works today. We continue to
>>>>>>>>>>> recommend
>>>>>>>>>>> jenkins <https://cloud.google.com/tools/repo/push-to-deploy>for
>>>>>>>>>>> applications that require build and test steps.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> If you have any problems with the source only deployments,
>>>>>>>>>>> please do let me know.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks again for your feedback.
>>>>>>>>>>>
>>>>>>>>>>> ..brad
>>>>>>>>>>>
>>>>>>>>>>> On Mon Feb 02 2015 at 12:57:30 PM Syrus Mesdaghi <
>>>>>>>>>>> syr...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>> At the very least you should have a one liner notice when someone
>>>>>>>>>>>> goes to setup a new pipeline with deploy source only mentioning
>>>>>>>>>>>> that it is
>>>>>>>>>>>> deprecated. We have a project that is still building as 'deploy
>>>>>>>>>>>> source
>>>>>>>>>>>> only'... I made a new project and have spent days trying to figure
>>>>>>>>>>>> out why
>>>>>>>>>>>> it doesn't deploy. I just happened to come across this thread in
>>>>>>>>>>>> my
>>>>>>>>>>>> desperate attempts to figure out what is going on. I agree with
>>>>>>>>>>>> Lucas that
>>>>>>>>>>>> "At least pushing source should remain as a feature". Having to do
>>>>>>>>>>>> a lot
>>>>>>>>>>>> more to do exactly what we needed doesn't feel like an upgrade
>>>>>>>>>>>> though I'm
>>>>>>>>>>>> sure some users will enjoy the extra capability.
>>>>>>>>>>>>
>>>>>>>>>>>> On Friday, December 19, 2014 at 6:44:30 PM UTC-5, Lucas Geiger
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Guys, this is absurd. You finally got the push-to-deploy
>>>>>>>>>>>>> product right , and now you are discontinuing it. At least
>>>>>>>>>>>>> pushing source
>>>>>>>>>>>>> should remain as a feature.
>>>>>>>>>>>>> The whole appeal of push to deploy was NOT setting up Jenkins.
>>>>>>>>>>>>> I think you are misjudging the number of people who object to
>>>>>>>>>>>>> using
>>>>>>>>>>>>> Jenkins.
>>>>>>>>>>>>> (By the way it was very disrespectful of you to cloak this
>>>>>>>>>>>>> discontinuation as a feature upgrade. A tasteless and
>>>>>>>>>>>>> disingenuous tactic,
>>>>>>>>>>>>> to be precise.)
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>> Google Groups "Google App Engine" group.
>>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>> it, send an email to google-appengi...@googlegroups.com.
>>>>>>>>>>>> To post to this group, send email to google-a...@googlegroups.
>>>>>>>>>>>> com.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Visit this group at http://groups.google.com/group
>>>>>>>>>>>> /google-appengine.
>>>>>>>>>>>> To view this discussion on the web visit
>>>>>>>>>>>> https://groups.google.com/d/msgid/google-appengine/c668fa0a-
>>>>>>>>>>>> 6c6a-4a82-8a28-e3f1a4f4eb83%40googlegroups.com
>>>>>>>>>>>> <https://groups.google.com/d/msgid/google-appengine/c668fa0a-6c6a-4a82-8a28-e3f1a4f4eb83%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>>>>> .
>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>> Google Groups "Google App Engine" group.
>>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>>> send an email to google-appengi...@googlegroups.com.
>>>>>>>>>> To post to this group, send email to google-a...@googlegroups.com
>>>>>>>>>> .
>>>>>>>>>> Visit this group at http://groups.google.com/
>>>>>>>>>> group/google-appengine.
>>>>>>>>>>
>>>>>>>>> To view this discussion on the web visit
>>>>>>>>>> https://groups.google.com/d/msgid/google-appengine/
>>>>>>>>>> 49a123fe-1398-42a3-b7d5-b475783ed7fe%40googlegroups.com
>>>>>>>>>> <https://groups.google.com/d/msgid/google-appengine/49a123fe-1398-42a3-b7d5-b475783ed7fe%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>>> .
>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>
>>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "Google App Engine" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>> send an email to google-appengi...@googlegroups.com.
>>>>>>>> To post to this group, send email to google-a...@googlegroups.com.
>>>>>>>> Visit this group at http://groups.google.com/group/google-appengine
>>>>>>>> .
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/msgid/google-appengine/83705dd9-df55-44f0-a3fe-7a86a42f32c2%40googlegroups.com
>>>>>>>>
>>>>>>>> <https://groups.google.com/d/msgid/google-appengine/83705dd9-df55-44f0-a3fe-7a86a42f32c2%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>> .
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Google App Engine" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to google-appengi...@googlegroups.com.
>>>>>> To post to this group, send email to google-a...@googlegroups.com.
>>>>>> Visit this group at http://groups.google.com/group/google-appengine.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/google-appengine/c36c62cf-7f09-4216-9faf-a72e6dd2c459%40googlegroups.com
>>>>>>
>>>>>> <https://groups.google.com/d/msgid/google-appengine/c36c62cf-7f09-4216-9faf-a72e6dd2c459%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Andrew Jessup | Product Manager, Google Cloud Platform |
>>>>> jes...@google.com
>>>>>
>>>>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/15ab7446-dab2-42de-a4f4-33839dd7e8c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
