Closed Bug 1683619 Opened 3 years ago Closed 3 years ago

Move Pontoon test automation from Travis CI to GitHub Actions

Categories

(Webtools Graveyard :: Pontoon, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: flod, Assigned: axel)

Details

Attachments

(1 file, 2 obsolete files)

While there's a lot of confusion around Travis announcement of dropping travis-ci.org, it looks like most open source projects are quickly moving away (MoFo is one).

Filing a bug to track the ongoing attempts to migrate.

I'd really like to take the opportunity to clean up the mess that the test automation is. Happy to help with that, too.

flod has some questions about the modularity of the workflows in my PR 1782, and I guess it's better to explain the rationales I have here instead of a PR that might go down the drain of permissions:

The arguments that guide me in creating workflows:

  • if the jobs might not need to be run at all, put them into a workflow
  • if jobs might want to share artifacts or have other dependencies, they should share a workflow

Then https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths can be used to disable a workflow completely

Arguments for individual jobs:

  • If one tool fails, other tools still can report their results.
  • I find it easier to understand what failed if one job has one thing to run.

This is in particular valid for linters, but also different test suites benefit from being run independently.

Concerns:

  • Resource usage. I'm not concerned as long as gh isn't :-)
  • Wall-clock time to test completion. Jobs are run in parallel, and setup times are really fast. It's not been a problem in other projects I used gh actions in.

(In reply to Francesco Lodolo [:flod] from comment #0)

While there's a lot of confusion around Travis announcement of dropping travis-ci.org, it looks like most open source projects are quickly moving away (MoFo is one).

Filing a bug to track the ongoing attempts to migrate.

I got a message about the plan to terminate travis-ci.org a long time ago, could be a year or so. They also offered migration to travis-ci.com and it was the same environment including plans the whole time, until now. Several weeks ago they changed it and in the free plan there are only 10000 credits (1000 minutes), period. As an open source project one can request more credits. I did that for MozillaCZ, but they have some guidelines if the project is important enough, so after two weeks when I haven't heard back from them other than they giving us 50000 more credits (5000 minutes), I migrated away to GitHub Actions too. I believe their decision about Pontoon might be swifter.

I also find actions nicer to schedule and partition. As you can tell from how far I went in the PR :-)

Taking this bug as the PR seems to cut it.

Assignee: nobody → axel
Status: NEW → ASSIGNED
Priority: -- → P2
Summary: Move Pontoon automation from Travis CI to GitHub Actions → Move Pontoon test automation from Travis CI to GitHub Actions
Attachment #9194183 - Attachment is obsolete: true
Attachment #9194201 - Attachment is obsolete: true
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: