Skip to content

config: add config-production-thunderbird.toml (bug 2012575)#83

Open
shtrom wants to merge 4 commits intomainfrom
bug2012575/thunderbird-worker
Open

config: add config-production-thunderbird.toml (bug 2012575)#83
shtrom wants to merge 4 commits intomainfrom
bug2012575/thunderbird-worker

Conversation

@shtrom
Copy link
Member

@shtrom shtrom commented Mar 3, 2026

  • Add configuration for thunderbird worker
  • Cover thunderbird and firefox config in tests (and make noop fx config pass the tests)

@shtrom
Copy link
Member Author

shtrom commented Mar 3, 2026

@coreycb if you want to have a look at the suggested mappings

This comment was marked as abuse.

@mozilla-conduit mozilla-conduit deleted a comment from Copilot AI Mar 3, 2026
@mozilla-conduit mozilla-conduit deleted a comment from Copilot AI Mar 3, 2026
@mozilla-conduit mozilla-conduit deleted a comment from Copilot AI Mar 3, 2026
Copy link

@coreycb coreycb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Generally looks good to me. I left a couple of comments, but they are probably just areas that I need clarity on and not actual issues.


[[tag_mappings]]
source_url = "https://github.com/thunderbird/infra-testing.git"
# (BETA|NIGHTLY)_(\d+)_(BASE|END)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need anything for tags prefixed with ESR_, RELEASE_, or THUNDERBIRD? I'm guessing the idea is that we would only test main and beta with infra-testing.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah! I missed those.

For infra-testing, yes, we can have a more limited set of tags.

However, it's also a good opportunity to capture the whole list, so we're not surprised that some are missing later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shtrom shtrom force-pushed the bug2012575/thunderbird-worker branch from e35c411 to f9c3cfd Compare March 3, 2026 03:35
# destination_url = "ssh://hg.mozilla.org/releases/comm-release/"
# ESR
# tag_pattern = "^(THUNDERBIRD)_(\\d+)(_\\d+)+esr_(BUILD\\d+|RELEASE)$"
# destination_url = "ssh://hg.mozilla.org/releases/comm-esr\\2/"
Copy link

@coreycb coreycb Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be a tag_pattern for comm-central?

Do the tag_patterns only include tags from the corresponding git branch?
I think the following would cover tags, assuming only tags from the corresponding git branches are included:

https://hg-edge.mozilla.org/comm-central/tags

(NIGHTLY)_(\d+)_(BASE|END)
(BETA)_(\d+)_(BASE|END)

https://hg-edge.mozilla.org/releases/comm-beta/tags

(NIGHTLY)_(\d+)_(BASE|END)
(BETA)_(\d+)_(BASE|END)
(RELEASE)_(\d+)_(BASE|END)
^(THUNDERBIRD)_(\\d+)_0b(\\d+)_(BUILD\\d+|RELEASE)$  # beta tags

https://hg-edge.mozilla.org/releases/comm-release/tags

(NIGHTLY)_(\d+)_(BASE|END)
(BETA)_(\d+)_(BASE|END)
(RELEASE)_(\d+)_(BASE|END)
^(THUNDERBIRD)_(\\d+)_0b(\\d+)_(BUILD\\d+|RELEASE)$  # beta tags
^(THUNDERBIRD)_(\\d+)(_\\d+)+_(BUILD\\d+|RELEASE)$  # release tags

https://hg-edge.mozilla.org/releases/comm-esr140/tags

(NIGHTLY)_(\d+)_(BASE|END)
(BETA)_(\d+)_(BASE|END)
(RELEASE)_(\d+)_(BASE|END)
(ESR)_(\d+)_(BASE|END)
^(THUNDERBIRD)_(\\d+)_0b(\\d+)_(BUILD\\d+|RELEASE)$  # beta tags
^(THUNDERBIRD)_(\\d+)(_\\d+)+esr_(BUILD\\d+|RELEASE)$  # esr tags

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants