github

How to clean up TeamCity build configuration In this blog post I will describe how I went from roughly 150 build configuration, which were copy-pasted from each other, to all of them using a single template and only specifying the differences in each build configuration. TeamCity Kotlin DSL feature was used in order to simplify this normally unbelievably tedious task. The problem We run contract tests on TeamCity. With a big number of microservices, we had an even bigger number of contract tests, each with their own build configuration.

Reproducible Assets for CloudFormation Stacks When CloudFormation is used to create the infrastructure or application it is important to take a look at the artifacts that are generated and deployed. When it comes to artifacts and especially Java artifacts (jar or zip files) there are some important requirements that have to be followed. Otherwise, the deployment might take longer than required, or in cases where the CDK Pipeline is used to deploy the application the pipeline can go into an infinite loop updating itself over and over again.

Github reusable workflows and how to verify them In december 2022 GitHub added the ability to share workflows between private repositories, opening the doors for Enterprises to make use of this feature. In this post I will describe how I implemented this in my APISMART Team and how I developed a system to verify changes to the reusable workflow. Basic knowledge of GitHub Actions is assumed. A working example can be found here: reusable-workflows-with-ci and reusable-workflows-sample-project

Sections What are output variables Creating an output Get output values between steps Get output values between jobs Get output variables between workflows Output variables can be powerful and frustrating at the same time. This simple how to, can save you ages of try and error. What are output variables Output variables are like return values of a step which can be used in all down streams like jobs, , reusable workflows and more.

Europace und andere Gesellschaften aus dem Hypoport-Netzwerk setzen schon länger auf die Vorteile von InnerSource mit GitHub als Plattform. Um in dem schnell wachsenden Verbund von Unternehmen diese offene Form der Zusammenarbeit auch in Zukunft zu gewährleisten, nutzt Hypoport jetzt GitHub Enterprise Cloud. So haben die autonomen Teams und Gesellschaften von Hypoport die Möglichkeit ihren Code in eigenen GitHub-Organisationen zu verwalten, ohne den Zugang zu den Repositories der anderen Teams zu verlieren.