Site Overlay

Tag: jenkins

CategoriesMisc Mozilla

Review of automation work – Q4 2015

By Admin

The last quarter of 2015 is gone and its time to reflect what happened in Q4. In the following you will find a full overview again for the whole quarter. It will be the last time that I will do that. From now on I will post in shorter intervals to specific topics instead of covering everything. This was actually a wish from our latest automation survey which I want to implement now. I hope you will like it. So during the last quarter my focus was completely on gettingContinue readingReview of automation work – Q4 2015

CategoriesMozilla

Firefox Automation report – Q3 2015

By Admin

It’s time for another Firefox Automation report! It’s incredible how fast a quarter passes by without that I have time to write reports more often. Hopefully it will change soon – news will be posted in a follow-up blog post. Ok, so what happened last quarter for our projects. Mozharness One of my deliverables in Q3 was to create mozharness scripts for our various tests in the firefox-ui-tests repository, so that our custom runner scripts can be replaced. This gives us a way more stable system and additional features likeContinue readingFirefox Automation report – Q3 2015

CategoriesMozilla

Firefox Automation report – Q2 2015

By Admin

It’s been a while since I wrote my last Firefox automation report, so lets do another one to wrap up everything happened in Q2 this year. As you may remember from my last report the team has been cut down to only myself, and beside that I was away the whole April. Means only 2 months worth of work will be covered this time. In general it was a tough quarter for me. Working alone and having to maintain all of our infrastructure and keeping both of our tests (MozmillContinue readingFirefox Automation report – Q2 2015

CategoriesMozilla

Firefox Automation report – week 47/48 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 47 and 48. Highlights Most of the work during those two weeks made by myself were related to get [Jenkins](http://jenkins-ci.org/ upgraded on our Mozmill CI systems to the most recent LTS version 1.580.1. This was a somewhat critical task given the huge number of issue as mentioned in my last Firefox Automation report. On November 17th we were finally able to get all the code changes landed on our production machineContinue readingFirefox Automation report – week 47/48 2014

CategoriesMozilla

Firefox Automation report – week 45/46 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 45 and 46. Highlights In our Mozmill-CI environment we had a couple of frozen Windows machines, which were running with 100% CPU load and 0MB of memory used. Those values came from the vSphere client, and didn’t give us that much information. Henrik checked the affected machines after a reboot, and none of them had any suspicious entries in the event viewer either. But he noticed that most of our VMsContinue readingFirefox Automation report – week 45/46 2014

CategoriesMozilla

Firefox Automation report – week 43/44 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 43 and 44. Highlights In preparation for the QA-wide demonstration of Mozmill-CI, Henrik reorganized our documentation to allow everyone a simple local setup of the tool. Along that we did the remaining deployment of latest code to our production instance. Henrik also worked on the upgrade of Jenkins to latest LTS version 1.565.3, and we were able to push this upgrade to our staging instance for observation. Further he got theContinue readingFirefox Automation report – week 43/44 2014

CategoriesMozilla

Firefox Automation report – week 25/26 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 25 and 26. Highlights June the 11th was actually the last Automation Training day for our team in Q3. About the results you can read here. We will implement some changes for the next quarter, when we most likely want to host 2 of them. Henrik finally got the time to upgrade our Mozmill-CI systems to the lastest LTS version of Jenkins. There were a bit of changes necessary but inContinue readingFirefox Automation report – week 25/26 2014

CategoriesMozilla

Firefox Automation report – week 23/24 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 23 and 24. Highlights To continue the training for Mozilla related test frameworks, we had the 3rd automation training day on June 4th. This time lesser people attended, but we were still able to get a couple of tasks done on oneanddone. Something which bothered us already for a while, is that for our mozmill-tests repository no push_printurl hook was setup. As result the landed changeset URL gets not printed toContinue readingFirefox Automation report – week 23/24 2014

CategoriesMozilla

Firefox Automation report – week 21/22 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 21 and 22. Highlights To assist everyone from our community to learn more about test automation at Mozilla, we targeted 4 full-day automation training days from mid of May to mid of June. The first training day was planned for May 21rd and went well. Lots of [people were present and actively learning more about automation[https://quality.mozilla.org/2014/05/automation-training-day-may-21st-results/). Especially about testing with Mozmill. To support community members to get in touch with MozmillContinue readingFirefox Automation report – week 21/22 2014

CategoriesMozilla

Firefox Automation report – week 19/20 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 19 and 20. Highlights When we noticed that our Mozmill-CI production instance is quickly filling up the /data partition, and having nearly no space left to actually run Jenkins, Henrik did a quick check, and has seen that the problem were the update jobs. Instead of producing log files with about 7MB in size, files with more than 100MB each were present. Inspecting those files revealed that the problem were allContinue readingFirefox Automation report – week 19/20 2014

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close