{"id":15065235,"url":"https://github.com/spring-cloud/spring-cloud-build","last_synced_at":"2025-05-14T04:07:58.860Z","repository":{"id":21519350,"uuid":"24838496","full_name":"spring-cloud/spring-cloud-build","owner":"spring-cloud","description":"Common build concerns, shared plugin configuration, etc. for Spring Cloud modules","archived":false,"fork":false,"pushed_at":"2025-05-09T21:01:03.000Z","size":15492,"stargazers_count":208,"open_issues_count":19,"forks_count":283,"subscribers_count":32,"default_branch":"main","last_synced_at":"2025-05-11T09:26:01.482Z","etag":null,"topics":["build","java","maven","microservices","spring","spring-boot","spring-cloud","spring-cloud-core"],"latest_commit_sha":null,"homepage":null,"language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/spring-cloud.png","metadata":{"files":{"readme":"README.adoc","changelog":null,"contributing":".github/CONTRIBUTING.md","funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2014-10-06T08:21:51.000Z","updated_at":"2025-05-09T21:01:07.000Z","dependencies_parsed_at":"2023-12-19T01:21:49.353Z","dependency_job_id":"cdff841f-760e-4be7-8114-b7ed2f364528","html_url":"https://github.com/spring-cloud/spring-cloud-build","commit_stats":{"total_commits":1292,"total_committers":53,"mean_commits":24.37735849056604,"dds":0.8568111455108359,"last_synced_commit":"d10ec2df90e957836db395b22084cff5c1d9f0c7"},"previous_names":[],"tags_count":151,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-cloud%2Fspring-cloud-build","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-cloud%2Fspring-cloud-build/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-cloud%2Fspring-cloud-build/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-cloud%2Fspring-cloud-build/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/spring-cloud","download_url":"https://codeload.github.com/spring-cloud/spring-cloud-build/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254036821,"owners_count":22003659,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["build","java","maven","microservices","spring","spring-boot","spring-cloud","spring-cloud-core"],"created_at":"2024-09-25T00:35:33.618Z","updated_at":"2025-05-14T04:07:58.831Z","avatar_url":"https://github.com/spring-cloud.png","language":"Shell","readme":"////\nDO NOT EDIT THIS FILE. IT WAS GENERATED.\nManual changes to this file will be lost when it is generated again.\nEdit the files in the src/main/asciidoc/ directory instead.\n////\n\n\nimage::https://github.com/spring-cloud/spring-cloud-build/workflows/Build/badge.svg?branch=main\u0026style=svg[\"Build\",link=\"https://github.com/spring-cloud/spring-cloud-build/actions\"]\n\nSpring Cloud Build is a common utility project for Spring Cloud\nto use for plugin and dependency management.\n\n[[building-and-deploying]]\n= Building and Deploying\n\nTo install locally:\n\n----\n\n$ mvn install -s .settings.xml\n----\n\nand to deploy snapshots to repo.spring.io:\n\n----\n$ mvn deploy -DaltSnapshotDeploymentRepository=repo.spring.io::default::https://repo.spring.io/snapshot\n----\n\nand for Maven Central use\n\n----\n$ mvn deploy -P central -DaltReleaseDeploymentRepository=sonatype-nexus-staging::default::https://oss.sonatype.org/service/local/staging/deploy/maven2\n----\n\n(the \"central\" profile is available for all projects in Spring Cloud and it sets up the gpg jar signing, and the repository has to be specified separately for this project because it is a parent of the starter parent which users in turn have as their own parent).\n\n[[contributing]]\n= Contributing\n\n:spring-cloud-build-branch: main\n\nSpring Cloud is released under the non-restrictive Apache 2.0 license,\nand follows a very standard Github development process, using Github\ntracker for issues and merging pull requests into main. If you want\nto contribute even something trivial please do not hesitate, but\nfollow the guidelines below.\n\n[[developer-certificate-of-origin]]\n== Developer Certificate of Origin (DCO)\n\nAll commits must include a __Signed-off-by__ trailer at the end of each commit message to indicate that the contributor agrees to the Developer Certificate of Origin.\nFor additional details, please refer to the blog post https://spring.io/blog/2025/01/06/hello-dco-goodbye-cla-simplifying-contributions-to-spring[Hello DCO, Goodbye CLA: Simplifying Contributions to Spring].\n\n[[code-of-conduct]]\n== Code of Conduct\nThis project adheres to the Contributor Covenant https://github.com/spring-cloud/spring-cloud-build/blob/main/docs/modules/ROOT/partials/code-of-conduct.adoc[code of\nconduct]. By participating, you  are expected to uphold this code. Please report\nunacceptable behavior to code-of-conduct@spring.io.\n\n[[code-conventions-and-housekeeping]]\n== Code Conventions and Housekeeping\nNone of these is essential for a pull request, but they will all help.  They can also be\nadded after the original pull request but before a merge.\n\n* Use the Spring Framework code format conventions. If you use Eclipse\n  you can import formatter settings using the\n  `eclipse-code-formatter.xml` file from the\n  https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/spring-cloud-dependencies-parent/eclipse-code-formatter.xml[Spring\n  Cloud Build] project. If using IntelliJ, you can use the\n  https://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter\n  Plugin] to import the same file.\n* Make sure all new `.java` files to have a simple Javadoc class comment with at least an\n  `@author` tag identifying you, and preferably at least a paragraph on what the class is\n  for.\n* Add the ASF license header comment to all new `.java` files (copy from existing files\n  in the project)\n* Add yourself as an `@author` to the .java files that you modify substantially (more\n  than cosmetic changes).\n* Add some Javadocs and, if you change the namespace, some XSD doc elements.\n* A few unit tests would help a lot as well -- someone has to do it.\n* If no-one else is using your branch, please rebase it against the current main (or\n  other target branch in the main project).\n* When writing a commit message please follow https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html[these conventions],\n  if you are fixing an existing issue please add `Fixes gh-XXXX` at the end of the commit\n  message (where XXXX is the issue number).\n\n[[checkstyle]]\n== Checkstyle\n\nSpring Cloud Build comes with a set of checkstyle rules. You can find them in the `spring-cloud-build-tools` module. The most notable files under the module are:\n\n.spring-cloud-build-tools/\n----\n└── src\n    ├── checkstyle\n    │   └── checkstyle-suppressions.xml \u003c3\u003e\n    └── main\n        └── resources\n            ├── checkstyle-header.txt \u003c2\u003e\n            └── checkstyle.xml \u003c1\u003e\n----\n\u003c1\u003e Default Checkstyle rules\n\u003c2\u003e File header setup\n\u003c3\u003e Default suppression rules\n\n[[checkstyle-configuration]]\n=== Checkstyle configuration\n\nCheckstyle rules are *disabled by default*. To add checkstyle to your project just define the following properties and plugins.\n\n.pom.xml\n----\n\u003cproperties\u003e\n\u003cmaven-checkstyle-plugin.failsOnError\u003etrue\u003c/maven-checkstyle-plugin.failsOnError\u003e \u003c1\u003e\n        \u003cmaven-checkstyle-plugin.failsOnViolation\u003etrue\n        \u003c/maven-checkstyle-plugin.failsOnViolation\u003e \u003c2\u003e\n        \u003cmaven-checkstyle-plugin.includeTestSourceDirectory\u003etrue\n        \u003c/maven-checkstyle-plugin.includeTestSourceDirectory\u003e \u003c3\u003e\n\u003c/properties\u003e\n\n\u003cbuild\u003e\n        \u003cplugins\u003e\n            \u003cplugin\u003e \u003c4\u003e\n                \u003cgroupId\u003eio.spring.javaformat\u003c/groupId\u003e\n                \u003cartifactId\u003espring-javaformat-maven-plugin\u003c/artifactId\u003e\n            \u003c/plugin\u003e\n            \u003cplugin\u003e \u003c5\u003e\n                \u003cgroupId\u003eorg.apache.maven.plugins\u003c/groupId\u003e\n                \u003cartifactId\u003emaven-checkstyle-plugin\u003c/artifactId\u003e\n            \u003c/plugin\u003e\n        \u003c/plugins\u003e\n\n    \u003creporting\u003e\n        \u003cplugins\u003e\n            \u003cplugin\u003e \u003c5\u003e\n                \u003cgroupId\u003eorg.apache.maven.plugins\u003c/groupId\u003e\n                \u003cartifactId\u003emaven-checkstyle-plugin\u003c/artifactId\u003e\n            \u003c/plugin\u003e\n        \u003c/plugins\u003e\n    \u003c/reporting\u003e\n\u003c/build\u003e\n----\n\u003c1\u003e Fails the build upon Checkstyle errors\n\u003c2\u003e Fails the build upon Checkstyle violations\n\u003c3\u003e Checkstyle analyzes also the test sources\n\u003c4\u003e Add the Spring Java Format plugin that will reformat your code to pass most of the Checkstyle formatting rules\n\u003c5\u003e Add checkstyle plugin to your build and reporting phases\n\nIf you need to suppress some rules (e.g. line length needs to be longer), then it's enough for you to define a file under `${project.root}/src/checkstyle/checkstyle-suppressions.xml` with your suppressions. Example:\n\n.projectRoot/src/checkstyle/checkstyle-suppresions.xml\n----\n\u003c?xml version=\"1.0\"?\u003e\n\u003c!DOCTYPE suppressions PUBLIC\n\t\t\"-//Puppy Crawl//DTD Suppressions 1.1//EN\"\n\t\t\"https://www.puppycrawl.com/dtds/suppressions_1_1.dtd\"\u003e\n\u003csuppressions\u003e\n\t\u003csuppress files=\".*ConfigServerApplication\\.java\" checks=\"HideUtilityClassConstructor\"/\u003e\n\t\u003csuppress files=\".*ConfigClientWatch\\.java\" checks=\"LineLengthCheck\"/\u003e\n\u003c/suppressions\u003e\n----\n\nIt's advisable to copy the `${spring-cloud-build.rootFolder}/.editorconfig` and `${spring-cloud-build.rootFolder}/.springformat` to your project. That way, some default formatting rules will be applied. You can do so by running this script:\n\n```bash\n$ curl https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/.editorconfig -o .editorconfig\n$ touch .springformat\n```\n\n[[ide-setup]]\n== IDE setup\n\n[[intellij-idea]]\n=== Intellij IDEA\n\nIn order to setup Intellij you should import our coding conventions, inspection profiles and set up the checkstyle plugin.\nThe following files can be found in the https://github.com/spring-cloud/spring-cloud-build/tree/main/spring-cloud-build-tools[Spring Cloud Build] project.\n\n.spring-cloud-build-tools/\n----\n└── src\n    ├── checkstyle\n    │   └── checkstyle-suppressions.xml \u003c3\u003e\n    └── main\n        └── resources\n            ├── checkstyle-header.txt \u003c2\u003e\n            ├── checkstyle.xml \u003c1\u003e\n            └── intellij\n                ├── Intellij_Project_Defaults.xml \u003c4\u003e\n                └── Intellij_Spring_Boot_Java_Conventions.xml \u003c5\u003e\n----\n\u003c1\u003e Default Checkstyle rules\n\u003c2\u003e File header setup\n\u003c3\u003e Default suppression rules\n\u003c4\u003e Project defaults for Intellij that apply most of Checkstyle rules\n\u003c5\u003e Project style conventions for Intellij that apply most of Checkstyle rules\n\n.Code style\n\nimage::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/docs/modules/ROOT/assets/images/intellij-code-style.png[Code style]\n\nGo to `File` -\u003e `Settings` -\u003e `Editor` -\u003e `Code style`. There click on the icon next to the `Scheme` section. There, click on the `Import Scheme` value and pick the `Intellij IDEA code style XML` option. Import the `spring-cloud-build-tools/src/main/resources/intellij/Intellij_Spring_Boot_Java_Conventions.xml` file.\n\n.Inspection profiles\n\nimage::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/docs/modules/ROOT/assets/images/intellij-inspections.png[Code style]\n\nGo to `File` -\u003e `Settings` -\u003e `Editor` -\u003e `Inspections`. There click on the icon next to the `Profile` section. There, click on the `Import Profile` and import the `spring-cloud-build-tools/src/main/resources/intellij/Intellij_Project_Defaults.xml` file.\n\n.Checkstyle\n\nTo have Intellij work with Checkstyle, you have to install the `Checkstyle` plugin. It's advisable to also install the `Assertions2Assertj` to automatically convert the JUnit assertions\n\nimage::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/docs/modules/ROOT/assets/images/intellij-checkstyle.png[Checkstyle]\n\nGo to `File` -\u003e `Settings` -\u003e `Other settings` -\u003e `Checkstyle`. There click on the `+` icon in the `Configuration file` section. There, you'll have to define where the checkstyle rules should be picked from. In the image above, we've picked the rules from the cloned Spring Cloud Build repository. However, you can point to the Spring Cloud Build's GitHub repository (e.g. for the `checkstyle.xml` : `https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/spring-cloud-build-tools/src/main/resources/checkstyle.xml`). We need to provide the following variables:\n\n- `checkstyle.header.file` - please point it to the Spring Cloud Build's, `spring-cloud-build-tools/src/main/resources/checkstyle-header.txt` file either in your cloned repo or via the `https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/spring-cloud-build-tools/src/main/resources/checkstyle-header.txt` URL.\n- `checkstyle.suppressions.file` - default suppressions. Please point it to the Spring Cloud Build's, `spring-cloud-build-tools/src/checkstyle/checkstyle-suppressions.xml` file either in your cloned repo or via the `https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/main/spring-cloud-build-tools/src/checkstyle/checkstyle-suppressions.xml` URL.\n- `checkstyle.additional.suppressions.file` - this variable corresponds to suppressions in your local project. E.g. you're working on `spring-cloud-contract`. Then point to the `project-root/src/checkstyle/checkstyle-suppressions.xml` folder. Example for `spring-cloud-contract` would be: `/home/username/spring-cloud-contract/src/checkstyle/checkstyle-suppressions.xml`.\n\nIMPORTANT: Remember to set the `Scan Scope` to `All sources` since we apply checkstyle rules for production and test sources.\n\n[[duplicate-finder]]\n== Duplicate Finder\n\nSpring Cloud Build brings along the  `basepom:duplicate-finder-maven-plugin`, that enables flagging duplicate and conflicting classes and resources on the java classpath.\n\n[[duplicate-finder-configuration]]\n=== Duplicate Finder configuration\n\nDuplicate finder is *enabled by default* and will run in the `verify` phase of your Maven build, but it will only take effect in your project if you add the `duplicate-finder-maven-plugin` to the `build` section of the project's `pom.xml`.\n\n.pom.xml\n[source,xml]\n----\n\u003cbuild\u003e\n    \u003cplugins\u003e\n        \u003cplugin\u003e\n            \u003cgroupId\u003eorg.basepom.maven\u003c/groupId\u003e\n            \u003cartifactId\u003eduplicate-finder-maven-plugin\u003c/artifactId\u003e\n        \u003c/plugin\u003e\n    \u003c/plugins\u003e\n\u003c/build\u003e\n----\n\nFor other properties, we have set defaults as listed in the https://github.com/basepom/duplicate-finder-maven-plugin/wiki[plugin documentation].\n\nYou can easily override them but setting the value of the selected property prefixed with `duplicate-finder-maven-plugin`. For example, set `duplicate-finder-maven-plugin.skip` to `true` in order to skip duplicates check in your build.\n\nIf you need to add `ignoredClassPatterns` or `ignoredResourcePatterns` to your setup, make sure to add them in the plugin configuration section of your project:\n\n[source,xml]\n----\n\u003cbuild\u003e\n    \u003cplugins\u003e\n        \u003cplugin\u003e\n            \u003cgroupId\u003eorg.basepom.maven\u003c/groupId\u003e\n            \u003cartifactId\u003eduplicate-finder-maven-plugin\u003c/artifactId\u003e\n            \u003cconfiguration\u003e\n                \u003cignoredClassPatterns\u003e\n                    \u003cignoredClassPattern\u003eorg.joda.time.base.BaseDateTime\u003c/ignoredClassPattern\u003e\n                    \u003cignoredClassPattern\u003e.*module-info\u003c/ignoredClassPattern\u003e\n                \u003c/ignoredClassPatterns\u003e\n                \u003cignoredResourcePatterns\u003e\n                    \u003cignoredResourcePattern\u003echangelog.txt\u003c/ignoredResourcePattern\u003e\n                \u003c/ignoredResourcePatterns\u003e\n            \u003c/configuration\u003e\n        \u003c/plugin\u003e\n    \u003c/plugins\u003e\n\u003c/build\u003e\n\n\n----\n\n\n[[flattening-the-poms]]\n= Flattening the POMs\n\nTo avoid propagating build setup that is required to build a Spring Cloud project, we're using the maven flatten plugin. It has the advantage of letting you use whatever features you need while publishing \"clean\" pom to the repository.\n\nIn order to add it, add the `org.codehaus.mojo:flatten-maven-plugin` to your `pom.xml`.\n\n[source,xml]\n----\n\u003cbuild\u003e\n    \u003cplugins\u003e\n        \u003cplugin\u003e\n            \u003cgroupId\u003eorg.codehaus.mojo\u003c/groupId\u003e\n            \u003cartifactId\u003eflatten-maven-plugin\u003c/artifactId\u003e\n        \u003c/plugin\u003e\n    \u003c/plugins\u003e\n\u003c/build\u003e\n----\n\n[[reusing-the-documentation]]\n= Reusing the documentation\n\nSpring Cloud Build publishes its `spring-cloud-build-docs` module that contains\nhelpful scripts (e.g. README generation ruby script) and css, xslt and images\nfor the Spring Cloud documentation. If you want to follow the same convention\napproach of generating documentation just add these plugins to your `docs` module\n\n[source,xml]\n----\n\u003cprofiles\u003e\n    \u003cprofile\u003e\n        \u003cid\u003edocs\u003c/id\u003e\n        \u003cbuild\u003e\n            \u003cresources\u003e\n                \u003cresource\u003e\n                    \u003cdirectory\u003esrc/main/antora/resources/antora-resources\u003c/directory\u003e\n                    \u003cfiltering\u003etrue\u003c/filtering\u003e\n                \u003c/resource\u003e\n            \u003c/resources\u003e\n            \u003cplugins\u003e\n                \u003cplugin\u003e\n                    \u003cgroupId\u003epl.project13.maven\u003c/groupId\u003e\n                    \u003cartifactId\u003egit-commit-id-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n                \u003cplugin\u003e\n                    \u003cgroupId\u003eorg.apache.maven.plugins\u003c/groupId\u003e\n                    \u003cartifactId\u003emaven-dependency-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n                \u003cplugin\u003e\n                    \u003cgroupId\u003eorg.codehaus.mojo\u003c/groupId\u003e\n                    \u003cartifactId\u003eexec-maven-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n                \u003cplugin\u003e\n                    \u003cgroupId\u003eio.spring.maven.antora\u003c/groupId\u003e\n                    \u003cartifactId\u003eantora-component-version-maven-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n                \u003cplugin\u003e\n                    \u003cgroupId\u003eorg.antora\u003c/groupId\u003e\n                    \u003cartifactId\u003eantora-maven-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n                \u003cplugin\u003e\n                    \u003cgroupId\u003eorg.apache.maven.plugins\u003c/groupId\u003e\n                    \u003cartifactId\u003emaven-antrun-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n                \u003cplugin\u003e\n                    \u003cartifactId\u003emaven-deploy-plugin\u003c/artifactId\u003e\n                \u003c/plugin\u003e\n            \u003c/plugins\u003e\n        \u003c/build\u003e\n    \u003c/profile\u003e\n----\n\nIMPORTANT: The order of plugin declaration is important!\n\nIn order for the build to generate the `adoc` file with all your configuration properties, your `docs` module should contain all the dependencies on the classpath, that you would want to scan for configuration properties.\n\nIf you want to modify which of the configuration properties are put in the table, you can tweak the `configprops.inclusionPattern` pattern to include only a subset of the properties (e.g. `\u003cconfigprops.inclusionPattern\u003espring.sleuth.*\u003c/configprops.inclusionPattern\u003e`).\n\nSpring Cloud Build Docs comes with a set of attributes for asciidoctor that you can reuse.\n\n[source,yml]\n----\nversion: @antora-component.version@\nprerelease: @antora-component.prerelease@\n\nasciidoc:\n  attributes:\n    attribute-missing: 'warn'\n    chomp: 'all'\n    project-root: @maven.multiModuleProjectDirectory@\n    github-repo: @docs.main@\n    github-raw: https://raw.githubusercontent.com/spring-cloud/@docs.main@/@github-tag@\n    github-code: https://github.com/spring-cloud/@docs.main@/tree/@github-tag@\n    github-issues: https://github.com/spring-cloud/@docs.main@/issues/\n    github-wiki: https://github.com/spring-cloud/@docs.main@/wiki\n    spring-cloud-version: @project.version@\n    github-tag: @github-tag@\n    version-type: @version-type@\n    docs-url: https://docs.spring.io/@docs.main@/docs/@project.version@\n    raw-docs-url: https://raw.githubusercontent.com/spring-cloud/@docs.main@/@github-tag@\n    project-version: @project.version@\n    project-name: @docs.main@\n----\n\n[[updating-the-guides]]\n= Updating the guides\n\nWe assume that your project contains guides under the `guides` folder.\n\n```\n.\n└── guides\n\t├── gs-guide1\n\t├── gs-guide2\n\t└── gs-guide3\n```\n\nThis means that the project contains 3 guides that would\ncorrespond to the following guides in Spring Guides org.\n\n- https://github.com/spring-guides/gs-guide1\n- https://github.com/spring-guides/gs-guide2\n- https://github.com/spring-guides/gs-guide3\n\nIf you deploy your project with the `-Pguides` profile like this\n\n```\n$ ./mvnw clean deploy -Pguides\n```\n\nwhat will happen is that for GA project versions, we will clone `gs-guide1`, `gs-guide2` and `gs-guide3` and update their contents with the ones being under your `guides` project.\n\nYou can skip this by either not adding the `guides` profile, or passing the `-DskipGuides` system property when the profile is turned on.\n\nYou can configure the project version passed to guides via the `guides-project.version` (defaults to `${project.version}`). The phase at which guides get updated can be configured by `guides-update.phase` (defaults to `deploy`).\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspring-cloud%2Fspring-cloud-build","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fspring-cloud%2Fspring-cloud-build","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspring-cloud%2Fspring-cloud-build/lists"}