Infrastructure Preview avis

Tom L. · Examiné il y a environ un an

it was impossible to access the jenkins site url so I had to stop the lab halfway through

Pablo B. · Examiné il y a environ un an

Suchy1210 S. · Examiné il y a environ un an

Yujie Z. · Examiné il y a environ un an

Francisca A. · Examiné il y a environ un an

i tried a couple of times but the jenkins deployment failed. It succeeded once but that time i was not able to open the site url, hence couldn't proceed further.

Lovish G. · Examiné il y a environ un an

MARCOS G. · Examiné il y a environ un an

Manjunatha L. · Examiné il y a environ un an

Manthan G. · Examiné il y a environ un an

f1-micro instance is unavailable in the us-central1-f region. I have tried multiple times and several hours apart but it didn't succeed.

Prince B. · Examiné il y a environ un an

Magdalena Z. · Examiné il y a environ un an

Alfredo M. · Examiné il y a environ un an

Reina M. · Examiné il y a environ un an

not working

Andrea C. · Examiné il y a environ un an

Terrible lab. I've had to repeat three times already. First, the jenkins deployment doesn't work. Second time, opening the jenkins site url returns a 502. Edit: third try, again failing on the deployment: ERROR: build step 0 "us-central1-docker.pkg.dev/cloud-config-sdk/images/config-sdk-tf:public-image-v0.0.165_1.5.7" failed: step exited with non-zero status: 1 Edit: Forth time, deployment failed again. I guess I'll have to skip this lab

Victor M. · Examiné il y a environ un an

Massimiliano G. · Examiné il y a environ un an

No N1 machines available.

Alberto I. · Examiné il y a environ un an

Have to use another version Jenkin to continue the lab

Hung Y. · Examiné il y a environ un an

I must be retry the deployment of jenkins several times before it works

Fabien F. · Examiné il y a environ un an

Fail to open Jenkin console and could not ssh to the VM

Hung Y. · Examiné il y a environ un an

Chelsea A. · Examiné il y a environ un an

Niranjan K. · Examiné il y a environ un an

The lab failed twice, was successful until the first task, but it still recognised it as failed for some reason.

Refilwe M. · Examiné il y a environ un an

I could not execute the following steps: 1. Click the link next to Site URL to view the site in another browser tab. If you encounter an error, you may need to reload the page a couple of times. ——> This site can’t be reached xx.xxx.xxx.xx took too long to respond. 2. Click SSH to connect to the Jenkins server. ——> Hanging on : “Establishing connection to SSH server…”

Justyna B. · Examiné il y a environ un an

getting confused not able to continue

Sai Praveena V. · Examiné il y a environ un an