Opinie (Building a DevOps Pipeline)
66536 opinii
Babulal .. · Sprawdzono 2 miesiące temu
The check on VMs did not work and so i waste 5 credit without a complete lab
Antonin L. · Sprawdzono 2 miesiące temu
Pretty pointless
Colin P. · Sprawdzono 2 miesiące temu
Many things not shown at the lab
Mohamed A. · Sprawdzono 2 miesiące temu
This is THE VERY WORST lab I have EVER participated in. The step-by-step instructions are THE VERY WORST! I have taken this lab at least four different times because I ran out of time because I was unable to locate pins, or clickable links. To add to my frustration the flow between the instructions and the actual web page is all screwed up. You have instructions to select a specific setting in one of the three panes, but the instructions do not specify exactly which pane. I want my freakin money back!
David P. · Sprawdzono 2 miesiące temu
Kaan Y. · Sprawdzono 2 miesiące temu
HARIKA Y. · Sprawdzono 2 miesiące temu
Interesting topic, but the first progress check didn't detect my VM. And as the created GitHub account is flagged, couldn't authenticate so couldn't finish the lab.
Martin W. · Sprawdzono 2 miesiące temu
Pratik B. · Sprawdzono 2 miesiące temu
Sandeep P. · Sprawdzono 2 miesiące temu
Richard M. · Sprawdzono 2 miesiące temu
Leonardo O. · Sprawdzono 2 miesiące temu
I had issues in the “Test your Build Changes” section. When creating the machines, different problems appeared. I tried to connect to one of them, but I got the error: “SSH authentication has failed. In order to debug, please analyze the sshd logs on the target machine using the serial console. Reading the recent serial port output may also be helpful.” Additionally, an internal server error was showing on the Flask page that was created.
Juan M. · Sprawdzono 2 miesiące temu
I had issues in the “Test your Build Changes” section. When creating the machines, different problems appeared. I tried to connect to one of them, but I got the error: “SSH authentication has failed. In order to debug, please analyze the sshd logs on the target machine using the serial console. Reading the recent serial port output may also be helpful.” Additionally, an internal server error was showing on the Flask page that was created.
Juan M. · Sprawdzono 2 miesiące temu
Many things not shown at the lab
Mohamed A. · Sprawdzono 2 miesiące temu
Malith M. · Sprawdzono 2 miesiące temu
amanpreet s. · Sprawdzono 2 miesiące temu
Sebastian B. · Sprawdzono 2 miesiące temu
Task 4 fails. Check this lab. Rest of the steps work fine. But the documentation does not reflect correct way to create a VM from container image.
Cyriac P. · Sprawdzono 2 miesiące temu
Soham M. · Sprawdzono 2 miesiące temu
even after completing automate build trigger successfully, step is showing as not completed. now next step is not showing as completed, even after the expected result appears. finally completed after 3rd try.
Nilesh P. · Sprawdzono 2 miesiące temu
even after completing automate build trigger successfully, step is showing as not completed. now next step is not showing as completed, even after the expected result appears.
Nilesh P. · Sprawdzono 2 miesiące temu
Worst lab I have ever encountered. Even though every tasks are perfect it just wont validate. There is bug in final step. And if you connect with the support team regarding the bug there response is just , currently we are not aware about it. I have tried it for 10th time and the support team is like than you do it for 11th and 12th time also. Exploit the bug
Dhruva B. · Sprawdzono 2 miesiące temu
A great lab but this was my score on the Checkpoints Manage Docker images with Cloud Build and Artifact Registry 0 / 30 Automate Builds with Trigger 30 / 30 Test your Build Changes 40 / 40 --- I ran the lab again and passed all the checks, but I encountered problems with Git authentication.
jose b. · Sprawdzono 2 miesiące temu
Sheraz A. · Sprawdzono 2 miesiące temu
Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.