I’m not sure if we want to make Jenkins public, but we should be able to publish the reports to S3 or similar. I’ll make a note to look into that.
Running on multiple branches (and even pull requests) shouldn’t be a problem either, I’ll add this to the list to do after we have the initial test merged. Thanks, Dave > On 2 May 2018, at 16:54, Stefan Arentz <[email protected]> wrote: > > Thank you Dave & Isabel! This is really wonderful! > > Is there a possibility of opening up that Jenkins instance or at least > publish build reports to a public place? I think that will make it easier for > people to investigate results. > > We would also like to enable this on our feature branches (v11.x, v12.x) so > that we not just test against master, but also against the version that we are > > S. > >> On May 2, 2018, at 11:47 AM, Dave Hunt <[email protected] >> <mailto:[email protected]>> wrote: >> >> Over the last few months I have prototyped and rolled out an initial test >> for the sync integration on Firefox for iOS. In the next week or so, I hope >> to land the new suite within the firefox-ios GitHub repository. For now, the >> single test (save bookmark on iOS, and verify bookmark appears after syncing >> on desktop) is running once per day on a Jenkins server against the latest >> Firefox nightly and the integration branch from my fork of firefox-ios. When >> signed into the VPN you can view the results of the job here >> http://mobileqa2.corp.tor1.mozilla.com:8080/blue/organizations/jenkins/firefox-ios.integration/activity >> >> <http://mobileqa2.corp.tor1.mozilla.com:8080/blue/organizations/jenkins/firefox-ios.integration/activity> >> and if the job fails or is fixed a notification is sent to #firefox-ios on >> Slack. >> >> I wrote about the new suite when I had the initial prototype working on my >> blog, here: >> https://davehunt.co.uk/2018/03/20/prototype-multi-device-firefox-tests.html >> <https://davehunt.co.uk/2018/03/20/prototype-multi-device-firefox-tests.html>. >> Since then, much of the feedback has been positive with a few suggestions, >> many of these I have implemented, such as: >> >> If path to Firefox is not specified, download latest Nightly build >> Enable debug sync logs and gather these in the HTML test report >> Set up continuous integration (see details above) >> Patches necessary for the TPS add-on have been merged upstream in >> mozilla-central >> Creation of Firefox Accounts has been split into a separate pytest plugin >> https://pypi.org/project/pytest-fxa/ <https://pypi.org/project/pytest-fxa/> >> >> The current blocker for me opening a pull request to merge this new suite >> into the firefox-ios repository is >> https://bugzilla.mozilla.org/show_bug.cgi?id=1455570 >> <https://bugzilla.mozilla.org/show_bug.cgi?id=1455570>. Without this, the >> entire code for the TPS add-on is duplicated in firefox-ios. While this >> isn’t a lot of code, it makes sense to simply download a nightly build much >> like we do for Firefox itself. >> >> I’m still very keen to hear feedback and suggestions, and happy to answer >> any questions. I believe Isabel will be demonstrating the new test at this >> week’s iOS meeting, which I also intend to attend. Otherwise, please feel >> free to reply here, or to find me on IRC (davehunt) or Slack (davehunt). >> >> Thanks, >> Dave Hunt >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
