This is towards #9107.

GCE e2e build/test failed for commit 6243838cec5482d22a1ca8fb37cb5f70cd0e5935.

• Build Log
• Test Artifacts
• Internal Jenkins Results

GCE e2e build/test failed for commit bfbb9bcd263da6dd46adf6c49d58c8c768bafb69.

• Build Log
• Test Artifacts
• Internal Jenkins Results

GCE e2e build/test failed for commit 09f559143798ffa320f978c7e7a874d5b3affc26.

• Build Log
• Test Artifacts
• Internal Jenkins Results

The new version of the app, and the new GCR images, work fine for me™. I don't know why the jenkins test is failing. I'll try running the test again in a bit.

GCE e2e build/test failed for commit 1119aee1404b8e5042735bfa239715f6dcee50f8.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@brendanburns Brendan, the jenkins build has failed enough times that I no longer think it's a fluke. However, nothing jumps out at me from the build log.
Would you have time to see if you can tell what's up? (sorry!) Multiple starts/restarts of the app have all seemed fine to me.
(The tests aren't assuming that the external load balancer for the frontend should be enabled, are they?)

@k8s-bot test this please

one minor comment, otherwise lgtm. I pinged Jenkins again.

GCE e2e build/test failed for commit 1119aee1404b8e5042735bfa239715f6dcee50f8.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Needs a rebase.

Rebased.
I see that there's a campaign to move example images into a GCR 'google_containers' project. My GCR images are in a devrel-run 'google_samples' project. Don't know if that's something we need to reconcile.
My frontend image differs in building from the php:5-apache image (rather than your custom image), as well as supporting the dns vs env stuff.

Let's see what Jenkins does this time. I did double check that the google_samples images were properly accessible from a personal account, and just ran through setting up the app again. All seems fine. If the build continues to fail I might need some assistance digging into why.

GCE e2e build/test failed for commit 547c44a55cdb3c2014e3aec36a1ad515e5e3f4be.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Jenkins is still broken. Are your images publically readable?

Yes, they are readable-- I confirmed that just a regular 'docker pull' from a personal laptop (no gcloud installed etc.) works fine, and got someone else to confirm as well, just to double check.
Something is up though.

GCE e2e build/test failed for commit b64d386eea5532bdf53c7606fcba4a27c6f3f0a2.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Unfortunately I'll have to punt on looking into this further until next week. Does seem like something's up, but as I noted above, it's all running fine for me. Maybe someone more familiar than me with the Jenkins setup can see if something jumps out at them.
Next week I'll give it a try on a personal account.

Labelling this PR as size/L

GCE e2e build/test failed for commit ddeb284c4c111ab6bb20c8a113690fd574becfa0.

• Build Log
• Test Artifacts
• Internal Jenkins Results

I tried running this example from a personal account as well, to double check the gcr access, and again it worked fine. I think I will need to get some help/consultation to figure out the jenkins issue.

GCE e2e build/test passed for commit 3574999.

• Build Log
• Test Artifacts
• Internal Jenkins Results

hah! turned out I needed to change a test.

LGTM, @amygdala thanks for finishing this out.

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

GCE e2e build/test passed for commit 3574999.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Automatic merge from SubmitQueue

It seems that gcr.io/google_samples/gb-frontend:v2 referenced in this PR is not the latest build of the guestbook. The changes of #12199 (comment) are not included.

@sttts The build files, in the php-redis subdir, have incorporated those changes to the relative URLs -- https://github.com/kubernetes/kubernetes/pull/12497/files (check that those changes look as expected to you).
Let me double check the image build date.
I did change the name of index.php-->guestbook.php (related to a change in the apache setup) and that initially caused one of the Jenkins tests to fail.

$ docker run -it gcr.io/google_samples/gb-frontend:v2 cat index.html                                                                                                     
<html ng-app="redis">
  <head>
    <title>Guestbook</title>
    <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css">
    <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.2.12/angular.min.js"></script>
    <script src="/controllers.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/angular-ui-bootstrap/0.13.0/ui-bootstrap-tpls.js"></script>
  </head>
  <body ng-controller="RedisCtrl">
    <div style="width: 50%; margin-left: 20px">
      <h2>Guestbook</h2>
    <form>
    <fieldset>
    <input ng-model="msg" placeholder="Messages" class="form-control" type="text" name="input"><br>
    <button type="button" class="btn btn-primary" ng-click="controller.onRedis()">Submit</button>
    </fieldset>
    </form>
    <div>
      <div ng-repeat="msg in messages track by $index">
        {{msg}}
      </div>
    </div>
    </div>
  </body>
</html>

Compare the line with controllers.php with the checked in index.html. In the later it's relative.

@sttts yes, it looks like the image needs to be rebuilt. Sorry about that.
gcr.io/google_samples/gb-frontend:v3 should fix it.
I'll test and submit a PR to bump the image version in the .yaml shortly.

@amygdala thanks for the fast fix 👍