Testing the New Build Pack
This lesson will test the newly made build pack by importing a project that uses it.
We'll cover the following...
- Remove go-demo-6 project
- Undo commits made to master
- Import project using go-mongo pack
- Listing local files
- Inspecting the activities
- Inspecting the pods
- Diagnosing the issue
- Inspecting the values.yaml file
- Modifying the probePath entry
- Adding probePath to the preview
- Push the updates to the application
- Check the application
- Revert to the go build pack
Let’s check whether our new build pack works as expected.
cd ..cd go-demo-6
We entered into the local copy of the go-demo-6
repository.
Remove go-demo-6 project
If you are reusing Jenkins X installation from the previous chapter, you’ll need to remove the go-demo-6 application as well as the activities so that we can restart the process of importing it.
⚠️ Please execute the commands that follow only if you did not destroy the cluster from the previous chapter and if you still have the go-demo-6 project inside Jenkins X. The first command will delete the application, while the second will remove all the Jenkins X activities related to go-demo-6.
jx delete application \$GH_USER/go-demo-6 \--batch-modekubectl --namespace jx delete act \--selector owner=$GH_USER \--selector sourcerepository=go-demo-6
Undo commits made to master
To make sure that our new build pack is indeed working as expected, we’ll undo all the commits we made to the master
branch in the previous chapter and start over.
git pullgit checkout origgit merge -s ours master --no-editgit checkout mastergit merge origrm -rf chartsgit push
We replaced the master
branch with orig
and pushed the changes to GitHub.