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

Add release channel comparison to prepare-version #24

Merged
merged 1 commit into from Sep 9, 2019

Conversation

@rrrene
Copy link
Contributor

commented Sep 9, 2019

Wenn man aktuell von bspw. beta nach master mergt, um aus Version 2.0.0-beta.1 die Version 2.0.0 zu machen, dann brechen die CI Tools ab, weil sie denken "Da sind keine Änderungen im Vergleich zu 2.0.0-beta.1, also brechen wir hier mal ab.".

Die Änderungen dieses PRs bedingen einen Vergleich des Release-Kanals, um festzustellen, ob trotz gleicher Inhalte eine neue Version gebaut werden muss.

@rrrene rrrene merged commit ec99ede into develop Sep 9, 2019
5 checks passed
5 checks passed
Build
Details
Build
Details
WIP Ready for review
Details
ci/jenkins/node This commit looks good
Details
process-engine.ci_tools Build #20190909.7 succeeded
Details
@rrrene rrrene deleted the feature/add-release-channel-comparison branch Sep 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.