You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had some issues while doing GitHub Actions: Continuous Delivery with Azure. It would have been really nice if there were some tips and tricks hints in the skills readmes.
For example, the points below would have helped me (some may be obvious, but if we are doing these skills trainings then we don't necessarily know things that will become obvious)
Don't name your repository with capital letters. It can cause the error below when Azure tries to retrieve the container package. DockerApiException: Docker API responded with status code=BadRequest, response={"message":"invalid reference format: repository name must be lowercase"}
You will need to create a github PAT with workflow write permissions for step 2 to work. PATS are created by selecting settings from your user icon in the top right corner when you are in github and then select Developer Settings at the bottom of the left hand menu. I added mine to the repository's secrets and then updated the step 2 yml file to use the PAT secret in the checkout step.
It can take a few minutes for the updates in Azure to complete. This can mean that:
The deploy fails saying that your app service isn't there - even though it is visible in the Azure gui. Just rerun the failing workflow.
The app appears to be failing even after a couple of refreshes of the app service page. Wait a few more minutes or check the Deployment Center logs to see if the app has been started (see below)
Monitor the messages Azure generates during installation of the App Service by navigating to the App Service in the Azure gui and selecting Deployment Center in the left hand menu, then selecting the Logs tab. When the deployment has completed successfully the message below appears: Container <username>-ttt-app_0_f1542a56 for site <username>-ttt-app initialized successfully and is ready to serve requests. .
There were some other issues because it appears that this specific skill started to get an update but it wasn't quite finished. I just worked my way through each of the errors and dug around in the discussions and skills repository until I got past the problem I had building in Step 2. My cd-azure repository contains my working version of the skills files. I think after "Check step 2, Set up the Azure environment" failed on the pull request syntax because the --title parameter was causing an error I commented out the step that failed in the step 2 yaml file and then reran it. I may have had to create the PR manually, I didn't feel like putting more time into figuring out why --title wasn't working. I did learn a lot from fixing all the problems but the --title was something I couldn't be bothered to investigate. :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I had some issues while doing GitHub Actions: Continuous Delivery with Azure. It would have been really nice if there were some tips and tricks hints in the skills readmes.
For example, the points below would have helped me (some may be obvious, but if we are doing these skills trainings then we don't necessarily know things that will become obvious)
DockerApiException: Docker API responded with status code=BadRequest, response={"message":"invalid reference format: repository name must be lowercase"}
Container <username>-ttt-app_0_f1542a56 for site <username>-ttt-app initialized successfully and is ready to serve requests.
.There were some other issues because it appears that this specific skill started to get an update but it wasn't quite finished. I just worked my way through each of the errors and dug around in the discussions and skills repository until I got past the problem I had building in Step 2. My cd-azure repository contains my working version of the skills files. I think after "Check step 2, Set up the Azure environment" failed on the pull request syntax because the --title parameter was causing an error I commented out the step that failed in the step 2 yaml file and then reran it. I may have had to create the PR manually, I didn't feel like putting more time into figuring out why --title wasn't working. I did learn a lot from fixing all the problems but the --title was something I couldn't be bothered to investigate. :)
Beta Was this translation helpful? Give feedback.
All reactions