Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inf 371 community release workflow #5595

Merged
merged 50 commits into from
May 20, 2024

Conversation

AliaksandrRyzhou
Copy link
Collaborator

@AliaksandrRyzhou AliaksandrRyzhou commented May 17, 2024

What changed? Why was the change needed?

These changes are needed for monthly community releases. It will create a new workflow (WF) to build a community version of docker images for multiple architectures.
Currently, we assume to bump the Lerna release version manually.
How does this WF work?
When we run pnpm release:xxxxx and Lerna creates a git tag the workflow will be triggered automatically to build docker images with the same docker tag as the git tag and the lerna version.

.github/workflows/community-releases.yml Outdated Show resolved Hide resolved
.github/workflows/community-releases.yml Outdated Show resolved Hide resolved
.github/workflows/community-releases.yml Show resolved Hide resolved
@@ -71,28 +115,37 @@ jobs:
--platform=linux/amd64,linux/arm64 --provenance=false
--output=type=image,name=ghcr.io/${{ env.REGISTRY_OWNER }}/${{ env.SERVICE_NAME }},push-by-digest=true,name-canonical=true
run: |
cd apps/$SERVICE_NAME && pnpm run docker:build
if [ "${{ env.SERVICE_NAME }}" = "embed" ] || [ "${{ env.SERVICE_NAME }}" = "embed-ee" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

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

there are currently a few services/apps without the enterprise functionality, so they are not different from the community build, and embed is one of these... however, the embed leaves in a different folder under the libs that's why we have this code... embed is a static JS script that is served with the http-server

Copy link

github-actions bot commented May 20, 2024

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Your PR title is: Inf 371 community release workflow
It should be something like: feat(scope): Add fancy new feature

Details:

No release type found in pull request title "Inf 371 community release workflow". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@AliaksandrRyzhou AliaksandrRyzhou merged commit 17c61b7 into next May 20, 2024
6 of 8 checks passed
@AliaksandrRyzhou AliaksandrRyzhou deleted the inf-371-community-release-workflow branch May 20, 2024 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants