Lab 8 Travis

In this lab we were to connect with TravisCI. I had some experience with Travis thanks to my 0.1 release bug, but it was interesting to be able to read more and actually connect to it from scratch. All of the requests made to Travis are done through a .travis.yml file, where you tell it how to configure, build and test the project. I wrote some tests in order to check whether or not the code I wrote in Python on the previous lab was working as intended, in a way that would be automated. My testing framework was pytest. Everything went along very smoothly, and it didn't take too long to see a very happy sight: a green checkmark on my Travis build.


Popular posts from this blog

Lab 2 - Building Firefox for Desktop from source on Windows 10

Image
Not a pretty sight if I can say so myself. After hours of waiting, seeing "Error 2" and not knowing where to go or what to do can be frustrating. But how did I get here? Relatively speaking, when following the instructions posted on  Building Firefox for Windows , everything went smoothly. Windows 10 is up to date? Check. Visual Studio 2017 is installed? Check. Rust and MozillaBuild are all installed as well? Check and check. Getting the source with Mercurial was a process that took quite a while, but that too went without any hitches. The problem came on attempting to build the code. Everything went well until we got to the image that you can see above. A Unicode error stops the building process from going ahead. When attempting to change the file "config.data", by substituting the single backslash with a double backslash on line 238, the issue still persists since the file gets rewritten every time one attempts to build. Thus far I have not found a way to
Read more

Lab 3 - Mastering your Code Editor: Sublime Text 3 and Atom

Image
Note to reader: For this lab we were tasked with working with 2 different editors. I chose Sublime Text 3  as something that I have but don't use too often and Atom , an editor I never used before. Feel free to download both as they are great editors, and feel free to take them for a spin if what you are about to read interests you! Test Driving I began by downloading the source to  the Best Resume Ever . After quickly unzipping what I had downloaded, I saw these folders and files: We were tasked with trying out two editors and performing common tasks among them, to ultimately decide which one we prefer. Below you can see the project opened in  Sublime (something done very easily, by simply going to File > Open Folder) : I did the same in Atom ( File > Open Folder): After performing some of the common tasks outlined in the lab (splitting the screen, finding strings, etc) I decided to pick Atom , since as I mentioned earlier, this editor was new to me. I
Read more

3 Things I Learned About the MIT License

Image
The task was simple. We had to first read the MIT License , followed by  The MIT License, Line by Line by Kyle E. Mitchell  and talk about what we learned or thought was interesting. One of the very first things that I learned and my main take away from this reading was to not simply trust or believe that there isn't much to a license if its writing is less than 200 words. I was impressed by just how much depth there was to the 171 word text. Secondly, I learned that the MIT License isn't one, but many (a family as a matter of fact) of licenses. And lastly, I learned that the MIT License has outlasted most of the software licensed under it.
Read more