Save this change, and then commit them to the local Git repository by running git commit:
$ git commit -a -m "Changes stars to pluses"
[master 61ce946] Changes stars to pluses
1 files changed, 1 insertions(+), 1 deletions(-)This will commit the changes locally, but since Git is a distributed repository, you now have to push
these changes through to your fork on GitHub. You do this by running git push:
$ git push
Counting objects: 21, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (11/11), 754 bytes, done.
Total 11 (delta 4), reused 0 (delta 0)
To [email protected]:john-smart/game-of-life.git
7882d5c..61ce946 master -> masterNow go back to the Jenkins web page. After a minute or so, a new build should kick off, and fail. In fact,
there are several other places which are affected by this change, and the regression tests related to these
features are now failing. On the build job home page, you will see a second build in the build history with
an ominous red ball (see Figure 2.21, “A failed build”)—this tells you that the latest build has failed.
You might also notice some clouds next to the Build History title—this is the same “weather” icon that
we saw on the home page, and serves the same purpose—to give you a general idea of how stable your
build is over time.
Figure 2.21. A failed build
If you click on the new build history entry, Jenkins will give you some more details about what went
wrong (see Figure 2.22, “The list of all the broken tests”). Jenkins tells us that there were 11 new test