70d1794916
* Automate setup-go-work as a dependency for Make targets (#35476) * automate setup-go-work It's all to easy to forget to `make setup-go-work`, only to run into mysterious build failures. Let's default to doing this automatically, unless `SKIP_SETUP_GO_WORK` is true (or the legacy `IGNORE_GO_WORK_IF_EXISTS`, which was oddly named, since we can't actually ignore it.) * Make setup-go-work recipe fail-fast with set -e * ci: post success to required e2e status contexts when no relevant changes (#35880) * ci: post correct skip status from within cypress/playwright reusable workflows The 'Required Status Checks' ruleset requires e2e-test/cypress-full/enterprise and e2e-test/playwright-full/enterprise on master and release-*.* branches. When a PR has no E2E-relevant changes, the jobs were silently skipped, leaving required statuses unset and the PR permanently blocked. Architecture fix: instead of a separate skip-e2e job in the caller that hardcodes status context names, the skip logic now lives inside the reusable workflows that already own and compute those context names. Changes: - e2e-tests-cypress.yml: add should_run input (default 'true') + skip job that uses the dynamically-computed context_name when should_run == 'false' - e2e-tests-playwright.yml: same pattern - e2e-tests-ci.yml: change e2e-cypress/e2e-playwright job conditions from should_run == 'true' to PR_NUMBER != '' (always run when there's a PR), pass should_run as input to both reusable workflows * Add E2E template workflows for Cypress and Playwright * Add check-e2e-test-only action for E2E workflow * Fix: Remove circular E2E workflow file check - skip tests when only CI files change * Add pull_request trigger to E2E workflow - run automatically on PR events * Fix resolve-pr to use github.event context for automatic pull_request trigger * Fix checkout condition to work with pull_request events * Fix: Remove orphaned fi statement in check-changes script --------- Co-authored-by: yasser khan <attitude3cena.yf@gmail.com>
About this folder
This folder contains some files that we use to build the mattermost-server and other files like privacy policy and licenses.
The Dockerfile in this folder (Dockerfile.buildenv) is the build environment for our current builds you can find the docker image to download here or build your own.
Docker Image for building the Server
We have a docker image to build mattermost-server and it is based on Go docker image.
In our Docker Hub Repository we have the following images:
mattermost/mattermost-build-server:dec-7-2018which is based on Go 1.11 you can use for MM versions <=5.8.0mattermost/mattermost-build-server:feb-28-2019which is based on Go 1.12 you can use for MM versions >=5.9.0<=5.15.0mattermost/mattermost-build-server:sep-17-2019which is based on Go 1.12.9 you can use for MM versions >=5.16.0mattermost/mattermost-build-server:20200322_golang-1.14.1which is based on Go 1.14.1 you can use for MM versions >=5.24.xmattermost/mattermost-build-server:20201023_golang-1.14.6which is based on Go 1.14.6 you can use for MM versions >=5.25.xmattermost/mattermost-build-server:20201119_golang-1.15.5which is based on Go 1.15.5 you can use for MM versions >=5.26.xto5.37.xmattermost/mattermost-build-server:20210810_golang-1.16.7which is based on Go 1.16.X you can use for MM versions >=5.38.x