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

Deploy on GH release event #640

Merged
merged 4 commits into from
Jun 22, 2021
Merged

Deploy on GH release event #640

merged 4 commits into from
Jun 22, 2021

Conversation

gkocur
Copy link
Contributor

@gkocur gkocur commented Jun 16, 2021

No description provided.

paths-ignore:
- "helm/**"

jobs:
scala-ts-tests:
# run on external PRs, but not on internal PRs since those will be run by push to branch
if: github.event_name == 'push' || github.event.pull_request.head.repo.full_name != github.repository
Copy link
Member

Choose a reason for hiding this comment

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

this was quite useful as when we were doing PRs from branches in this repository (not from forks), we got double builds (one for the PR, one for the in-repository branch). Is this problem solved somehow else?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, but please note I also added explicite branch name in on:.
So now this workflow is triggered:

  • on push to master branch
  • on PR (create, update etc)
  • on GH release.
    So no double builds (unless unlikely event when someone creates PR with master as source branch)

build.sbt Outdated
@@ -156,29 +155,24 @@ lazy val fatJarSettings = Seq(
}
)

git.uncommittedSignifier := Some("dirty")
Copy link
Member

Choose a reason for hiding this comment

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

if these settings are used only for docker build, maybe we can scope and move them to dockerSettings?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, please check it now.

@adamw
Copy link
Member

adamw commented Jun 21, 2021

I think we should automatically create a GH release, once a version-tag is pushed? We have this set up using release-drafter in other projects, so maybe we can do the same here? E.g. https://github.com/softwaremill/quicklens/blob/master/.github/workflows/ci.yml#L80-L89

@adamw adamw merged commit 32181dd into master Jun 22, 2021
@mergify mergify bot deleted the deploy-on-release branch June 22, 2021 12:29
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.

2 participants