# taskcluster Published articles for taskcluster. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Skipping persistent intermittent failures DevFeed: [Skipping persistent intermittent failures]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2016-10-07T23:16:25Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [bug](), [Test coverage](), [Android]() Tags: [android](), [automated](), [bug](), [developers](), [intermittent-failures](), [mozilla](), [project-stockwell](), [reporting](), [taskcluster](), [test](), [testing](), [tests]() ### AI overview The article argues that teams should more aggressively skip tests with frequent, persistent intermittent failures to reduce the cost of repeated failures and developer attention. It acknowledges the trade-off of losing test coverage and potentially missing spontaneous fixes. ### Source excerpt Our automated tests seem to fail a lot. Instead of a sea of green, a typical good push often looks ... Continue reading -> ## Mozilla London All Hands 2016 DevFeed: [Mozilla London All Hands 2016]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-06-20T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [Web]() Tags: [culture](), [event](), [executive](), [intern](), [london](), [mozilla](), [organization](), [outreachy](), [taskcluster](), [technology](), [web]() ### AI overview An Outreachy intern recounts attending Mozilla London All Hands 2016, highlighting the event's talks, meetings, team activities, and the opportunity to connect with Mozilla colleagues and interns. The article also reflects on finding valued female role models across Mozilla. ### Source excerpt Last week, all of Mozilla met in London for a whirlwind tour from TARDIS to TaskCluster, from BBC1 to e10s, from Regent Park to the release train, from Paddington to Positron. As an Outreachy intern, I felt incredibly lucky to be part of this event, which gave me a chance to get to know Mozilla, my team, and the other interns much better. It was a jam-packed work week of talks, meetings, team events, pubs, and parties, and it would be impossible to blog about all of the fun, fascinating, and foxy things I learned and did. But I can at least give you some of the highlights! Or, should I say, Who-lights? (Be warned, that is not the last pun you will encounter here today.) Foxy, the TARDIS, and espionage in the park? All in a day's work at #MozLondon! pic.twitter.com/QPWdPRnJHY -- Anjana Vakil (@AnjanaVakil) June 14, 2016 Role models While watching the plenary session that kicked off the week, it felt great to realize that of the 4 executives emerging from the TARDIS in the corner to take the stage (3 Mozillians and 1 guest star), a full 50% were women. As I had shared with my mentor (also a woman) before arriving in London, one of my goals for the week was to get inspired by finding some new role moz-els (ha!): Mozillians who I could aspire to be like one day, especially those of the female variety. Why a female role model, specifically? What does gender have to do with it? Well, to be a good role model for you, a person needs to not only have a life/career/lego-dragon you aspire to have one day, but also be someone who you can already identify with, and see yourself in, today. A role model serves as a bridge between the two. As I am a woman, and that is a fundamental part of my experience, a role model who shares that experience is that much easier for me to relate to. I wouldn't turn down a half-Irish-half-Indian American living in Germany, either. At any rate, in London I found no shortage of talented, experienced, and - perhaps most importantly - valued women at Mo ## Firefox-ui-tests - Platform Operations Project of the Month DevFeed: [Firefox-ui-tests - Platform Operations Project of the Month]() Original publisher: [Read original article]() Author: Admin Published: 2016-06-02T09:18:23Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Testing](), [ci](), [Puppeteer](), [Automation](), [Mozilla](), [Jenkins]() Tags: [automation](), [browser](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [mozilla](), [mozmill](), [taskcluster](), [testing](), [tests](), [treeherder]() ### AI overview This article presents firefox-ui-tests as a Mozilla project for integration testing of Firefox's user interface. The tests use the Marionette automation framework and Firefox Puppeteer's page object model, run across Firefox code-check and release workflows, and include localized-build and update testing. The project's work includes improving result visibility, test placement, stability, and coverage. ### Source excerpt Hello from Platforms Operations! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month's project is firefox-ui-tests! What are firefox-ui-tests? Firefox UI tests are a test suite for integration tests which are based on the Marionette automation framework and are majorly used for user interface centric testing of Firefox. The difference to pure Marionette tests is, that Firefox UI tests are interacting with the chrome scope (browser interface) and not content scope (websites) by default.Continue readingFirefox-ui-tests - Platform Operations Project of the Month ## Not Testing a Firefox Build (Generic Tasks in TaskCluster) DevFeed: [Not Testing a Firefox Build (Generic Tasks in TaskCluster)]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-05-02T04:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Testing](), [Script](), [Firefox](), [Mozilla]() Tags: [automation](), [ci](), [firefox](), [foss](), [mozilla](), [script](), [taskcluster](), [testing]() ### AI overview The article explains how Mozilla's generic TaskCluster tasks can run in-tree Marionette harness tests when files change, without waiting for a Firefox build or unrelated dependencies. It describes the chain of YAML configurations and shell scripts that checks out the source and runs mozharness, and explains why mozharness is preferred over a direct mach invocation for dependency and result handling. ### Source excerpt I take advantage of generic tasks to run a mozharness script in a gecko source checkout. ## First Experiment with TaskCluster DevFeed: [First Experiment with TaskCluster]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-02-09T05:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [CI/CD](), [YAML](), [configuration](), [Testing](), [Mozilla](), [Docker](), [Python]() Tags: [build](), [ci](), [configuration](), [continuous-integration](), [docker](), [eslint](), [firefox](), [foss](), [mozilla](), [python](), [taskcluster](), [testing](), [treeherder](), [yaml]() ### AI overview A developer explains how to add and schedule a new task in Mozilla's TaskCluster continuous integration system. The article covers task graphs, YAML configuration, Docker-based execution, source checkouts, and the steps required to register tasks for scheduling and try pushes. ### Source excerpt Adding a new task to TaskCluster continuous integration system. ## mozregression - new way for handling merges DevFeed: [mozregression - new way for handling merges]() Original publisher: [Read original article]() Author: parkouss Published: 2015-11-14T09:42:48Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Testing](), [Mozilla]() Tags: [automation](), [contribution](), [integration](), [mozilla](), [mozregression](), [python](), [regression](), [taskcluster](), [test]() ### AI overview This article proposes improving mozregression's handling of merge commits during regression bisection. The approach uses Taskcluster builds to narrow the range, identifies the branch containing the merged commits, and bisects that push range. ### Source excerpt I am currently investigating how we can make mozregression smarter to handle merges, and I will explain how in this post. Problem While bisecting builds with mozregression on mozilla-central, we often end up with a merge commit. These commits often incorporate many individual changes, consider for example this url for a merge commit. A regression ... Continue reading mozregression - new way for handling merges ## Engineering Productivity Update, November 5, 2015 DevFeed: [Engineering Productivity Update, November 5, 2015]() Original publisher: [Read original article]() Author: jagriffin Published: 2015-11-05T13:59:20Z Content type: news Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [developer tooling](), [Firefox](), [Tool]() Tags: [devtools](), [engineering-productivity](), [mozilla](), [performance](), [taskcluster](), [treeherder](), [version-control](), [windows]() ### AI overview Mozilla's Engineering Productivity team reports progress on Mercurial cloning performance, community contribution, MozReview and Autoland, Treeherder, Perfherder, Android workflows, TaskCluster migration, and e10s testing on Windows. ### Source excerpt It's the first week of November, and because of the December all-hands and the end-of-year holidays, this essentially means the quarter is half over. You can see what the team is up to and how we're tracking against our deliverables with this spreadsheet. Highlights hg.mozilla.org: gps did some interesting work investigating ways to increase cloning [...] ## Firefox Automation report - Q3 2015 DevFeed: [Firefox Automation report - Q3 2015]() Original publisher: [Read original article]() Author: Admin Published: 2015-10-20T19:42:37Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Automation](), [Firefox](), [Jenkins](), [Refactoring](), [Puppeteer](), [ci](), [modules]() Tags: [automation](), [blog](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [modules](), [mozilla](), [mozmill](), [refactoring](), [report](), [software](), [taskcluster](), [test](), [treeherder]() ### AI overview A Q3 2015 Firefox Automation report describes work on mozharness scripts for firefox-ui-tests, including improved configurability, crash-report handling, and support for Jenkins and release-testing workflows. It also covers Mozmill-CI updates, test-job refactoring, fixes for update tests affected by Release Engineering changes, and rewritten Pulse-message handling. ### Source excerpt 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