Refactor build pipeline #1645
Merged
Refactor build pipeline #1645
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Manangka
force-pushed
the
refactor_build_pipeline
branch
from
148a4df
to
e244c5f
Compare
Manangka
force-pushed
the
refactor_build_pipeline
branch
from
e244c5f
to
d071b37
Compare
…its original build steps
# Conflicts: # .teamcity/Ribasim_Linux/buildTypes/Linux_TestRibasimBinaries.kt # .teamcity/Ribasim_Windows/buildTypes/Windows_TestDelwaqCoupling.kt
Jingru923
approved these changes
Jul 29, 2024
# Conflicts: # .teamcity/Ribasim_Windows/buildTypes/Windows_TestDelwaqCoupling.kt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a major PR reafctoring the teamcity pipelines.
The goal is:
The structure has changed slighlty
Both the windows and linux projects have a Main buildstep. This buildstep is a composite buildstep. That means that is isn't building anything directly, instead it triggers dependend buildsteps. This is the starting point of the pipeline and only this builstep is directly triggered from github
It then follows the chain and start the beginning.
Duplicate code have been extracted to Templates. The templates have been made in such a way that they can both be used by the linux build aswell as by the windows builds.