archive-info.com » INFO » H » HSKUPIN.INFO

Total: 368

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • December | 2015 | hskupin.info
    more focus in the future to both blog posts and discussions on the mailing list More than half of our followers check for updates at least once a day So when we get started with interesting discussions I would expect good activity throughout the day 44 of all feel less informed about our current activities Another 33 answered this question with Mostly So it s a clear indication what I already thought and which clearly needs action on our side to be more communicative Doing this might also bring more people into our active projects so mentoring would be much more valuable and time effective as handling any drive by projects which we cannot fully support A request for the type of news we should do more is definitely for latest changes and code landings from contributors This will ensure people feel recognized and contributors will also know each others work and see the effectiveness in regards of our project goals But also discussions about various automation related topics as mentioned already above are highly wanted Other topics like quarterly goals and current status updates are also wanted and we will see how we can do that We might be able to fold those general updates into the Engineering Productivity updates which are pushed out twice a month via the A Team Planet Also there is a bit of confusion about the Firefox Automation team and how it relates to the Engineering Productivity team formerly A Team Effectively we are all part of the latter and the virtual Automation team has only been created when we got shifted between the A Team and QA Team forth and back This will not happen anymore so we agreed on to get rid of this name All in all there are some topics

    Original URL path: http://www.hskupin.info/2015/12/ (2016-05-01)
    Open archived version from archive


  • 05 | January | 2016 | hskupin.info
    our news via the automation mailing list But given the low usage of that list in the last months it was a bit surprising Nearly all the time I sent emails myself not to count in Travis results That means we want to implement a change here From now on we won t use the mozilla dev automation list but instead utilize the mozilla tools list Also because this is the recommended list for the Engineering Productivity team we are all part of and discussions will reach a larger audience So please subscribe to this list via Google Groups or Email For status updates about our current activities we started to use standu ps last quarter It seems to work pretty well for us and everyone else is welcome to also post updates to our automation project section If you are interested in those updates then read through that list or simply subscribe the page in your RSS reader Please also note that from now on there will be no Firefox Automation reports anymore Instead I will reduce the amount of different contents and only write about projects I worked on So keep an eye out to not miss those automation Mozilla QA Photostream January 2016 M T W T F S S Dec Feb 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Recent Posts Review of Firefox desktop automation work Q1 2016 March 31 2016 Firefox Desktop automation goals Q1 2016 February 2 2016 Review of automation work Q4 2015 January 9 2016 Automation Survey Follow up January 5 2016 Results of the Firefox Automation Survey December 3 2015 Survey about sharing information inside the Firefox

    Original URL path: http://www.hskupin.info/2016/01/05/ (2016-05-01)
    Open archived version from archive

  • 09 | January | 2016 | hskupin.info
    wait with the landing of the patch until mozmill ci production uses the new mozharness code This will hopefully happen soon and only wait of some other bugs to be fixed But based on those created packages we were able to use exactly that code to get our harness puppeteer and tests landed on http hg mozilla org mozilla central We also package them into the common tests zip archive for use in mozmill ci Details about all that can be found on bug 1212609 But please be aware that we still use the Github repository as integration repository I regularly mirror the code to hg which has to happen until we can also use the test package for localized builds and update tests Beside all that there were also a couple of mozharness fixes necessary So I implemented a better fetching of the tooltool script added the uninstall feature and also setup the handling of crash symbols for firefox ui tests Finally the addition of test package support finished up my work on mozharness for Q4 in 2015 During all the time I was also sheriffing our test results on Treeherder e g mozilla central because we are still Tier 3 level and sheriffs don t care about it Mozmill CI Our Jenkins based CI system is still called mozmill ci even it doesn t really run any mozmill tests anymore We decided to not change its name given that it will only be around this year until we can run all of our tests in TaskCluster But lots of changes have been landed which I want to announce below We followed Release Engineering and got rid of the OS X 10 8 testing That means the used Mac minis were ready to get re imaged with OS X 10 11 The transition worked seamlessly Enhancements for test report submission to Treeherder by switching over to Hawk credentials and more understandable group names and symbols Preparation of all the machines of our supported platforms OSX 10 6 10 9 10 10 10 11 Ubuntu 14 04 Windows XP 7 8 1 to be able to handle mozharness driven tests Implemented and updated scripts to run firefox ui tests via mozharness and to allow Treeherder to fully parse our logs Addons Tools I also had some time to work on supporting tools Together with the help of contributors we got the following done mozdownload Release of mozdownload 1 18 1 and 1 19 to cope with the move of builds to AWS Nightly Tester Tools Porting back changes from the NTT fork called Utilu Nightly Tester Tools Memchaser Thanks to the tireless efforts from Szabolcs Hubai we got Memchaser working again in latest Firefox builds So all in all it was a productive quarter with lots of things accomplished I m glad that we got all of this done Now in Q1 it will continue and more interesting work is in front of me which I m excited about I

    Original URL path: http://www.hskupin.info/2016/01/09/ (2016-05-01)
    Open archived version from archive

  • Results of the Firefox Automation Survey | hskupin.info
    So it s a clear indication what I already thought and which clearly needs action on our side to be more communicative Doing this might also bring more people into our active projects so mentoring would be much more valuable and time effective as handling any drive by projects which we cannot fully support A request for the type of news we should do more is definitely for latest changes and code landings from contributors This will ensure people feel recognized and contributors will also know each others work and see the effectiveness in regards of our project goals But also discussions about various automation related topics as mentioned already above are highly wanted Other topics like quarterly goals and current status updates are also wanted and we will see how we can do that We might be able to fold those general updates into the Engineering Productivity updates which are pushed out twice a month via the A Team Planet Also there is a bit of confusion about the Firefox Automation team and how it relates to the Engineering Productivity team formerly A Team Effectively we are all part of the latter and the virtual Automation team has only been created when we got shifted between the A Team and QA Team forth and back This will not happen anymore so we agreed on to get rid of this name All in all there are some topics which will need further discussions I will follow up with another blog post soon which will show off our plans for improvements and how we want to work to make it happen automation QA survey Post navigation Previous Post Survey about sharing information inside the Firefox Automation team Next Post Automation Survey Follow up Logging In Post a Reply to Planet Ateam

    Original URL path: http://www.hskupin.info/2015/12/03/results-of-the-firefox-automation-survey/?replytocom=59450 (2016-05-01)
    Open archived version from archive

  • Results of the Firefox Automation Survey | hskupin.info
    Mostly So it s a clear indication what I already thought and which clearly needs action on our side to be more communicative Doing this might also bring more people into our active projects so mentoring would be much more valuable and time effective as handling any drive by projects which we cannot fully support A request for the type of news we should do more is definitely for latest changes and code landings from contributors This will ensure people feel recognized and contributors will also know each others work and see the effectiveness in regards of our project goals But also discussions about various automation related topics as mentioned already above are highly wanted Other topics like quarterly goals and current status updates are also wanted and we will see how we can do that We might be able to fold those general updates into the Engineering Productivity updates which are pushed out twice a month via the A Team Planet Also there is a bit of confusion about the Firefox Automation team and how it relates to the Engineering Productivity team formerly A Team Effectively we are all part of the latter and the virtual Automation team has only been created when we got shifted between the A Team and QA Team forth and back This will not happen anymore so we agreed on to get rid of this name All in all there are some topics which will need further discussions I will follow up with another blog post soon which will show off our plans for improvements and how we want to work to make it happen automation QA survey Post navigation Previous Post Survey about sharing information inside the Firefox Automation team Next Post Automation Survey Follow up Logging In Post a Reply to PlanetFeeds

    Original URL path: http://www.hskupin.info/2015/12/03/results-of-the-firefox-automation-survey/?replytocom=59452 (2016-05-01)
    Open archived version from archive

  • November | 2015 | hskupin.info
    to get more people involved into our projects To ensure that we do not make use of the wrong communication channels depending where most of our readers are I have setup a little survey It will only take you a minute to go through but it will help us a lot to know more about the preferences of our automation geeks So please take that little time and help us The survey can be found here and is open until end of November 2015 https www surveymonkey com r 528WYYJ Thank you a lot automation Mozilla QA survey testing Photostream November 2015 M T W T F S S Oct Dec 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Recent Posts Review of Firefox desktop automation work Q1 2016 March 31 2016 Firefox Desktop automation goals Q1 2016 February 2 2016 Review of automation work Q4 2015 January 9 2016 Automation Survey Follow up January 5 2016 Results of the Firefox Automation Survey December 3 2015 Survey about sharing information inside the Firefox Automation team November 23 2015

    Original URL path: http://www.hskupin.info/2015/11/ (2016-05-01)
    Open archived version from archive

  • 03 | December | 2015 | hskupin.info
    put more focus in the future to both blog posts and discussions on the mailing list More than half of our followers check for updates at least once a day So when we get started with interesting discussions I would expect good activity throughout the day 44 of all feel less informed about our current activities Another 33 answered this question with Mostly So it s a clear indication what I already thought and which clearly needs action on our side to be more communicative Doing this might also bring more people into our active projects so mentoring would be much more valuable and time effective as handling any drive by projects which we cannot fully support A request for the type of news we should do more is definitely for latest changes and code landings from contributors This will ensure people feel recognized and contributors will also know each others work and see the effectiveness in regards of our project goals But also discussions about various automation related topics as mentioned already above are highly wanted Other topics like quarterly goals and current status updates are also wanted and we will see how we can do that We might be able to fold those general updates into the Engineering Productivity updates which are pushed out twice a month via the A Team Planet Also there is a bit of confusion about the Firefox Automation team and how it relates to the Engineering Productivity team formerly A Team Effectively we are all part of the latter and the virtual Automation team has only been created when we got shifted between the A Team and QA Team forth and back This will not happen anymore so we agreed on to get rid of this name All in all there are some

    Original URL path: http://www.hskupin.info/2015/12/03/ (2016-05-01)
    Open archived version from archive

  • Firefox Automation report – week 25/26 2014 | hskupin.info
    up by IT which we now have to puppetize and bring online But this may still take a bit given the remaining blockers for using PuppetAgain While talking about Puppet we got the next big change reviewed and landed With bug 1021230 we now have our own user account which can be customized to our needs And that s what we totally need given that our infrastructure is so different from the Releng one Also for TPS we made progress so the new TPS CI production machine came online Yet it cannot replace the current CI due to still a fair amount of open blockers but hopefully by end of July we should be able to turn the switch Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 25 and week 26 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 25 and week 26 automation continuous integration firefox jenkins mozmill testing Post navigation Previous Post Firefox Automation report week 23 24 2014 Next Post Firefox Automation report week 27 28 2014 Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 3 Replies 0 Comments 3 Tweets 0 Facebook 0 Pingbacks Last reply was July 17 2014 EdgarsLabRat View July 17 2014 moz Henrik Skupin Firefox Automation report week 25 26 2014 http t co rEZCDL7UWD Reply planetmozilla View July 17 2014 Henrik Skupin Firefox Automation report week 25 26 2014 http t co v82YCqSTTy Reply Planet Ateam View

    Original URL path: http://www.hskupin.info/2014/07/17/firefox-automation-report-week-25-26-2014/ (2016-05-01)
    Open archived version from archive