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

Build and release pipelines for Gist Web #10

Merged
merged 2 commits into from
Apr 21, 2023

Conversation

stephen-pope-customer-io
Copy link
Contributor

Build on merge to develop
Release on tag creation

Task: https://github.com/customerio/issues/issues/9599

Build on merge to develop
Release on tag creation
AWS_DEST="web/$RELEASE_VERSION"
echo "AWS_DEST=$AWS_DEST" >> $GITHUB_ENV
echo "AWS_DEST=$AWS_DEST"
- uses: shallwefootball/s3-upload-action@master
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we specify permissions? If uploaded with default permissions only the admin has read permissions.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You can specify otherwise, but the action by default makes it publicly readable.

@stephen-pope-customer-io stephen-pope-customer-io changed the title Build and release pipelines Build and release pipelines for Gist Web Apr 19, 2023
@BernardGatt BernardGatt merged commit f975c95 into develop Apr 21, 2023
@BernardGatt BernardGatt deleted the feature/9599-pipelines branch April 21, 2023 10:49
@BernardGatt BernardGatt restored the feature/9599-pipelines branch April 21, 2023 11:19
@BernardGatt
Copy link
Collaborator

After merging and looking at the result, I realized this would create an issue when trying to release a hotfix.

Imagine this scenario where we have 3.0.0 released and we want to create a hotfix on it 3.0.1

Since master is in sync with develop and release flow will take directly from master, there's no way for us to create a hotfix release.

I suggest we:

  • Build gist.min.js on develop & master (no merging though)
  • Tagging should always pick the git ref being tagged (not master).

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.

None yet

2 participants