tchekai704
/
src-spring-framework
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Spring Framework
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
28232 Commits
19 Branches
274 Tags
318 MiB
Tree: 841448877a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '841448877a'
${ noResults }
src-spring-framework/ci/pipeline.yml

400 lines
11 KiB
Raw Normal View History Unescape

Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
anchors:
Polish CI pipeline
4 years ago
git-repo-resource-source: &git-repo-resource-source
uri: ((github-repo))
username: ((github-username))
Fix GitHub credentials to use token rather than password Closes gh-27402
3 years ago
password: ((github-ci-release-token))
Polish CI pipeline
4 years ago
branch: ((branch))
gradle-enterprise-task-params: &gradle-enterprise-task-params
GRADLE_ENTERPRISE_ACCESS_KEY: ((gradle_enterprise_secret_access_key))
GRADLE_ENTERPRISE_CACHE_USERNAME: ((gradle_enterprise_cache_user.username))
GRADLE_ENTERPRISE_CACHE_PASSWORD: ((gradle_enterprise_cache_user.password))
sonatype-task-params: &sonatype-task-params
Fix release pipeline for Maven Central publication This commit fixes the missing pieces in our Maven Central publication pipeline. Our first attempt at releasing with it showed a few problems: * the promote task did not have the artifacts downladed with the artifactory repository * we applied the wrong Sonatype credentials to the task * the github changelog task would fail because of docker rate limiting since we were not using the right type of resource, which is configured with the proper caching mechanism See gh-26654
4 years ago
SONATYPE_USERNAME: ((sonatype-username))
SONATYPE_PASSWORD: ((sonatype-password))
Polish CI pipeline
4 years ago
SONATYPE_URL: ((sonatype-url))
Upgrade CI to concourse-release-scripts 0.3.4
3 years ago
SONATYPE_STAGING_PROFILE: ((sonatype-staging-profile))
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
artifactory-task-params: &artifactory-task-params
ARTIFACTORY_SERVER: ((artifactory-server))
ARTIFACTORY_USERNAME: ((artifactory-username))
ARTIFACTORY_PASSWORD: ((artifactory-password))
Polish CI pipeline
4 years ago
build-project-task-params: &build-project-task-params
BRANCH: ((branch))
<<: *gradle-enterprise-task-params
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
docker-resource-source: &docker-resource-source
username: ((docker-hub-username))
password: ((docker-hub-password))
Configure Concourse release pipeline Closes gh-25911
4 years ago
slack-fail-params: &slack-fail-params
text: >
Remove Slack "here" mentions for failed builds This was introduced by mistake in 6b978cb5dc4
4 years ago
:concourse-failed: <https://ci.spring.io/teams/${BUILD_TEAM_NAME}/pipelines/${BUILD_PIPELINE_NAME}/jobs/${BUILD_JOB_NAME}/builds/${BUILD_NAME}|${BUILD_PIPELINE_NAME} ${BUILD_JOB_NAME} failed!>
Configure Concourse release pipeline Closes gh-25911
4 years ago
[$TEXT_FILE_CONTENT]
text_file: git-repo/build/build-scan-uri.txt
silent: true
icon_emoji: ":concourse:"
username: concourse-ci
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
changelog-task-params: &changelog-task-params
name: generated-changelog/tag
tag: generated-changelog/tag
body: generated-changelog/changelog.md
github-task-params: &github-task-params
GITHUB_USERNAME: ((github-username))
GITHUB_TOKEN: ((github-ci-release-token))
Configure Concourse release pipeline Closes gh-25911
4 years ago
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
resource_types:
Upgrade registry-image-resource in CI pipeline to 1.5.0 See spring-projects/spring-boot#30408
3 years ago
- name: registry-image
type: registry-image
source:
Rely only on Docker Hub for fetching OCI images
2 years ago
<<: *docker-resource-source
Upgrade registry-image-resource in CI pipeline to 1.5.0 See spring-projects/spring-boot#30408
3 years ago
repository: concourse/registry-image-resource
Upgrade CI Concourse resources
2 years ago
tag: 1.8.0
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- name: artifactory-resource
Pull images with registry-image resource in build
4 years ago
type: registry-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
source:
Rely only on Docker Hub for fetching OCI images
2 years ago
<<: *docker-resource-source
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
repository: springio/artifactory-resource
Upgrade to Artifactory Resource 0.0.18
2 years ago
tag: 0.0.18
Upgrade CI to github-release resource 1.5.5 Closes gh-27459
3 years ago
- name: github-release
type: registry-image
source:
Rely only on Docker Hub for fetching OCI images
2 years ago
<<: *docker-resource-source
Upgrade CI to github-release resource 1.5.5 Closes gh-27459
3 years ago
repository: concourse/github-release-resource
Upgrade CI Concourse resources
2 years ago
tag: 1.8.0
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- name: github-status-resource
Pull images with registry-image resource in build
4 years ago
type: registry-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
source:
Rely only on Docker Hub for fetching OCI images
2 years ago
<<: *docker-resource-source
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
repository: dpb587/github-status-resource
tag: master
- name: slack-notification
Pull images with registry-image resource in build
4 years ago
type: registry-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
source:
Rely only on Docker Hub for fetching OCI images
2 years ago
<<: *docker-resource-source
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
repository: cfcommunity/slack-notification-resource
tag: latest
resources:
- name: git-repo
type: git
Fix GitHub icon in build pipeline
4 years ago
icon: github
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
source:
Polish CI pipeline
4 years ago
<<: *git-repo-resource-source
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- name: ci-images-git-repo
type: git
Fix GitHub icon in build pipeline
4 years ago
icon: github
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
source:
uri: ((github-repo))
branch: ((branch))
paths: ["ci/images/*"]
Polish CI pipeline
4 years ago
- name: ci-image
Remove outdated docker-image resource from CI The docker-image resource is now replaced by the registry-image resource.
3 years ago
type: registry-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
icon: docker
source:
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
<<: *docker-resource-source
Polish CI pipeline
4 years ago
repository: ((docker-hub-organization))/spring-framework-ci
Rely only on Docker Hub for fetching OCI images
2 years ago
tag: ((milestone))
Add JDK18 variant to CI pipeline This commit adds a new JDK 18 variant to the CI build image and configures a JDK18 build (sources compiled with JDK17, tests compiled and run with JDK18) to the CI pipeline. Closes gh-27607
3 years ago
- name: every-morning
type: time
icon: alarm
source:
start: 8:00 AM
stop: 9:00 AM
location: Europe/Vienna
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- name: artifactory-repo
type: artifactory-resource
icon: package-variant
source:
uri: ((artifactory-server))
username: ((artifactory-username))
password: ((artifactory-password))
build_name: ((build-name))
- name: repo-status-build
type: github-status-resource
icon: eye-check-outline
source:
repository: ((github-repo-name))
access_token: ((github-ci-status-token))
branch: ((branch))
context: build
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
- name: repo-status-jdk21-build
Add Java 19 daily build to CI pipeline
2 years ago
type: github-status-resource
icon: eye-check-outline
source:
repository: ((github-repo-name))
access_token: ((github-ci-status-token))
branch: ((branch))
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
context: jdk21-build
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- name: slack-alert
type: slack-notification
icon: slack
source:
url: ((slack-webhook-url))
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
- name: github-pre-release
type: github-release
icon: briefcase-download-outline
source:
owner: spring-projects
repository: spring-framework
access_token: ((github-ci-release-token))
pre_release: true
release: false
- name: github-release
type: github-release
icon: briefcase-download
source:
owner: spring-projects
repository: spring-framework
access_token: ((github-ci-release-token))
pre_release: false
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
jobs:
Polish CI pipeline
4 years ago
- name: build-ci-images
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
plan:
Build CI image using oci-build-task resource
3 years ago
- get: git-repo
- get: ci-images-git-repo
trigger: true
- task: build-ci-image
privileged: true
file: git-repo/ci/tasks/build-ci-image.yml
output_mapping:
image: ci-image
vars:
ci-image-name: ci-image
Rely only on Docker Hub for fetching OCI images
2 years ago
<<: *docker-resource-source
Polish CI pipeline
4 years ago
- put: ci-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
params:
Build CI image using oci-build-task resource
3 years ago
image: ci-image/image.tar
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- name: build
serial: true
public: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- get: git-repo
trigger: true
- put: repo-status-build
params: { state: "pending", commit: "git-repo" }
- do:
- task: build-project
Polish CI pipeline
4 years ago
image: ci-image
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
file: git-repo/ci/tasks/build-project.yml
Fix task parameters in CI build pipeline Prior to this commit, the task parameters for the CI project checks were overridden by a task anchor. This commit splits the anchor declaration and ensures that the `TEST_TOOLCHAIN` setting is set for the JDK variant builds. See gh-25787
4 years ago
privileged: true
timeout: ((task-timeout))
params:
<<: *build-project-task-params
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
on_failure:
do:
- put: repo-status-build
params: { state: "failure", commit: "git-repo" }
- put: slack-alert
params:
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
<<: *slack-fail-params
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
- put: repo-status-build
params: { state: "success", commit: "git-repo" }
- put: artifactory-repo
params: &artifactory-params
Publish directly to Maven Central This commit skips the Bintray-related tasks in our CI pipeline and instead relies on Maven Central for publishing Spring Framework artifacts. This commit also updates the CI pipeline to sign the artifacts directly with the `artifactory-resource`. Closes gh-26654
4 years ago
signing_key: ((signing-key))
signing_passphrase: ((signing-passphrase))
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
repo: libs-snapshot-local
folder: distribution-repository
build_uri: "https://ci.spring.io/teams/${BUILD_TEAM_NAME}/pipelines/${BUILD_PIPELINE_NAME}/jobs/${BUILD_JOB_NAME}/builds/${BUILD_NAME}"
build_number: "${BUILD_PIPELINE_NAME}-${BUILD_JOB_NAME}-${BUILD_NAME}"
disable_checksum_uploads: true
threads: 8
artifact_set:
- include:
Stop publishing distribution zip artifact Prior to this commit, the Spring Framework build would publish several zip artifacts: * a "*-schema.zip" containing all the XSD schemas produced * a "*-docs.zip" containing the API docs * a "*-dist.zip" containing all of the above, plus module jars Since the reference docs are now produced by Antora in a separate process, the "*-docs.zip" does not contain the reference docs anymore. But it still contains the API docs which are automatically fetched from the artifact repository and published on the docs.spring.io website. This commit intends to update the current arrangement and optimize the build. First, the "*-dist.zip" is not published anymore, since it cannot be consumed anyway by the community: repo.spring.io does not distribute release artifacts publicly, developers are expected to get them from Maven Central. This arrangement is quite dated anyway and is not really useful in current application build setups. The generation of API docs is moved to a new "framework-api" module, separating it from the reference docs module ("framework-docs") which contains Java, Kotlin and Asciidoctor sources. This removes the custom javadoc aggregation task and instead uses a dedicated Gradle plugin. This change also adds a new `-PskipDocs` Gradle project property that skips entirely the documentation tasks (javadoc, kdocs) as well as the "distrbution" tasks managed in the framework-api module. This allows developers to publish locally a SNAPSHOT of Spring Framework without creating the entire documentation distribution. This is particularly useful for local testing. For example, `$ ./gradlew pTML -PskipDocs`. Closes gh-31049
2 years ago
- "/**/framework-api-*.zip"
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
properties:
"zip.name": "spring-framework"
"zip.displayname": "Spring Framework"
"zip.deployed": "false"
- include:
Update CI pipeline for api docs publication See gh-31049
1 year ago
- "/**/framework-api-*-docs.zip"
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
properties:
"zip.type": "docs"
- include:
Stop publishing distribution zip artifact Prior to this commit, the Spring Framework build would publish several zip artifacts: * a "*-schema.zip" containing all the XSD schemas produced * a "*-docs.zip" containing the API docs * a "*-dist.zip" containing all of the above, plus module jars Since the reference docs are now produced by Antora in a separate process, the "*-docs.zip" does not contain the reference docs anymore. But it still contains the API docs which are automatically fetched from the artifact repository and published on the docs.spring.io website. This commit intends to update the current arrangement and optimize the build. First, the "*-dist.zip" is not published anymore, since it cannot be consumed anyway by the community: repo.spring.io does not distribute release artifacts publicly, developers are expected to get them from Maven Central. This arrangement is quite dated anyway and is not really useful in current application build setups. The generation of API docs is moved to a new "framework-api" module, separating it from the reference docs module ("framework-docs") which contains Java, Kotlin and Asciidoctor sources. This removes the custom javadoc aggregation task and instead uses a dedicated Gradle plugin. This change also adds a new `-PskipDocs` Gradle project property that skips entirely the documentation tasks (javadoc, kdocs) as well as the "distrbution" tasks managed in the framework-api module. This allows developers to publish locally a SNAPSHOT of Spring Framework without creating the entire documentation distribution. This is particularly useful for local testing. For example, `$ ./gradlew pTML -PskipDocs`. Closes gh-31049
2 years ago
- "/**/framework-api-*-schema.zip"
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
properties:
"zip.type": "schema"
get_params:
threads: 8
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
- name: jdk21-build
Add Java 19 daily build to CI pipeline
2 years ago
serial: true
public: true
plan:
- get: ci-image
- get: git-repo
- get: every-morning
trigger: true
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
- put: repo-status-jdk21-build
Add Java 19 daily build to CI pipeline
2 years ago
params: { state: "pending", commit: "git-repo" }
- do:
- task: check-project
image: ci-image
file: git-repo/ci/tasks/check-project.yml
privileged: true
timeout: ((task-timeout))
params:
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
TEST_TOOLCHAIN: 21
Add Java 19 daily build to CI pipeline
2 years ago
<<: *build-project-task-params
on_failure:
do:
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
- put: repo-status-jdk21-build
Add Java 19 daily build to CI pipeline
2 years ago
params: { state: "failure", commit: "git-repo" }
- put: slack-alert
params:
<<: *slack-fail-params
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
- put: repo-status-jdk21-build
Add Java 19 daily build to CI pipeline
2 years ago
params: { state: "success", commit: "git-repo" }
Add Release pipeline for Milestone versions This commit finishes the first step for migrating our complete build and release pipeline to Concourse CI. We're creating here a new "Release" jobs group in our pipeline. We can now release Milestones from our pipeline with: * the "stage-milestone" job, which creates and tags a new Milestone version on the source repository, builds the artifacts and deploys them in a staging repository and updates the version to the next SNAPSHOT. * the "promote-milestone" fetches the build information from the staging repository and promotes the released milestone in the official milestone repository. Interactions with the Artifactory and Bintray REST APIs are done using the https://github.com/spring-io/concourse-release-scripts project. Closes gh-22490
5 years ago
- name: stage-milestone
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Add Release pipeline for Milestone versions This commit finishes the first step for migrating our complete build and release pipeline to Concourse CI. We're creating here a new "Release" jobs group in our pipeline. We can now release Milestones from our pipeline with: * the "stage-milestone" job, which creates and tags a new Milestone version on the source repository, builds the artifacts and deploys them in a staging repository and updates the version to the next SNAPSHOT. * the "promote-milestone" fetches the build information from the staging repository and promotes the released milestone in the official milestone repository. Interactions with the Artifactory and Bintray REST APIs are done using the https://github.com/spring-io/concourse-release-scripts project. Closes gh-22490
5 years ago
- get: git-repo
trigger: false
- task: stage
Polish CI pipeline
4 years ago
image: ci-image
Add Release pipeline for Milestone versions This commit finishes the first step for migrating our complete build and release pipeline to Concourse CI. We're creating here a new "Release" jobs group in our pipeline. We can now release Milestones from our pipeline with: * the "stage-milestone" job, which creates and tags a new Milestone version on the source repository, builds the artifacts and deploys them in a staging repository and updates the version to the next SNAPSHOT. * the "promote-milestone" fetches the build information from the staging repository and promotes the released milestone in the official milestone repository. Interactions with the Artifactory and Bintray REST APIs are done using the https://github.com/spring-io/concourse-release-scripts project. Closes gh-22490
5 years ago
file: git-repo/ci/tasks/stage-version.yml
params:
RELEASE_TYPE: M
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
<<: *gradle-enterprise-task-params
Add Release pipeline for Milestone versions This commit finishes the first step for migrating our complete build and release pipeline to Concourse CI. We're creating here a new "Release" jobs group in our pipeline. We can now release Milestones from our pipeline with: * the "stage-milestone" job, which creates and tags a new Milestone version on the source repository, builds the artifacts and deploys them in a staging repository and updates the version to the next SNAPSHOT. * the "promote-milestone" fetches the build information from the staging repository and promotes the released milestone in the official milestone repository. Interactions with the Artifactory and Bintray REST APIs are done using the https://github.com/spring-io/concourse-release-scripts project. Closes gh-22490
5 years ago
- put: artifactory-repo
params:
<<: *artifactory-params
repo: libs-staging-local
- put: git-repo
params:
repository: stage-git-repo
- name: promote-milestone
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Add Release pipeline for Milestone versions This commit finishes the first step for migrating our complete build and release pipeline to Concourse CI. We're creating here a new "Release" jobs group in our pipeline. We can now release Milestones from our pipeline with: * the "stage-milestone" job, which creates and tags a new Milestone version on the source repository, builds the artifacts and deploys them in a staging repository and updates the version to the next SNAPSHOT. * the "promote-milestone" fetches the build information from the staging repository and promotes the released milestone in the official milestone repository. Interactions with the Artifactory and Bintray REST APIs are done using the https://github.com/spring-io/concourse-release-scripts project. Closes gh-22490
5 years ago
- get: git-repo
trigger: false
- get: artifactory-repo
trigger: false
passed: [stage-milestone]
params:
download_artifacts: false
save_build_info: true
- task: promote
file: git-repo/ci/tasks/promote-version.yml
params:
RELEASE_TYPE: M
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
<<: *artifactory-task-params
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
- task: generate-changelog
file: git-repo/ci/tasks/generate-changelog.yml
params:
RELEASE_TYPE: M
<<: *github-task-params
Use Docker Hub credentials for CI release tasks
2 years ago
<<: *docker-resource-source
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
- put: github-pre-release
params:
<<: *changelog-task-params
Update CI pipeline to release RCs
5 years ago
- name: stage-rc
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Update CI pipeline to release RCs
5 years ago
- get: git-repo
trigger: false
- task: stage
Polish CI pipeline
4 years ago
image: ci-image
Update CI pipeline to release RCs
5 years ago
file: git-repo/ci/tasks/stage-version.yml
params:
RELEASE_TYPE: RC
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
<<: *gradle-enterprise-task-params
Update CI pipeline to release RCs
5 years ago
- put: artifactory-repo
params:
<<: *artifactory-params
repo: libs-staging-local
- put: git-repo
params:
repository: stage-git-repo
- name: promote-rc
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Update CI pipeline to release RCs
5 years ago
- get: git-repo
trigger: false
- get: artifactory-repo
trigger: false
passed: [stage-rc]
params:
download_artifacts: false
save_build_info: true
- task: promote
file: git-repo/ci/tasks/promote-version.yml
params:
RELEASE_TYPE: RC
Use Docker Hub credentials for CI release tasks
2 years ago
<<: *docker-resource-source
Refactor Concourse pipeline Extract duplicate snippets as document anchors.
4 years ago
<<: *artifactory-task-params
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
- task: generate-changelog
file: git-repo/ci/tasks/generate-changelog.yml
params:
RELEASE_TYPE: RC
<<: *github-task-params
- put: github-pre-release
params:
<<: *changelog-task-params
Configure Concourse release pipeline Closes gh-25911
4 years ago
- name: stage-release
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Configure Concourse release pipeline Closes gh-25911
4 years ago
- get: git-repo
trigger: false
- task: stage
Polish CI pipeline
4 years ago
image: ci-image
Configure Concourse release pipeline Closes gh-25911
4 years ago
file: git-repo/ci/tasks/stage-version.yml
params:
RELEASE_TYPE: RELEASE
<<: *gradle-enterprise-task-params
- put: artifactory-repo
params:
<<: *artifactory-params
repo: libs-staging-local
- put: git-repo
params:
repository: stage-git-repo
- name: promote-release
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Configure Concourse release pipeline Closes gh-25911
4 years ago
- get: git-repo
trigger: false
- get: artifactory-repo
trigger: false
passed: [stage-release]
params:
Fix release pipeline for Maven Central publication This commit fixes the missing pieces in our Maven Central publication pipeline. Our first attempt at releasing with it showed a few problems: * the promote task did not have the artifacts downladed with the artifactory repository * we applied the wrong Sonatype credentials to the task * the github changelog task would fail because of docker rate limiting since we were not using the right type of resource, which is configured with the proper caching mechanism See gh-26654
4 years ago
download_artifacts: true
Configure Concourse release pipeline Closes gh-25911
4 years ago
save_build_info: true
- task: promote
file: git-repo/ci/tasks/promote-version.yml
params:
RELEASE_TYPE: RELEASE
Use Docker Hub credentials for CI release tasks
2 years ago
<<: *docker-resource-source
Configure Concourse release pipeline Closes gh-25911
4 years ago
<<: *artifactory-task-params
Publish directly to Maven Central This commit skips the Bintray-related tasks in our CI pipeline and instead relies on Maven Central for publishing Spring Framework artifacts. This commit also updates the CI pipeline to sign the artifacts directly with the `artifactory-resource`. Closes gh-26654
4 years ago
<<: *sonatype-task-params
- name: create-github-release
Configure Concourse release pipeline Closes gh-25911
4 years ago
serial: true
plan:
Polish CI pipeline
4 years ago
- get: ci-image
Configure Concourse release pipeline Closes gh-25911
4 years ago
- get: git-repo
- get: artifactory-repo
trigger: true
passed: [promote-release]
params:
download_artifacts: false
save_build_info: true
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
- task: generate-changelog
file: git-repo/ci/tasks/generate-changelog.yml
params:
RELEASE_TYPE: RELEASE
Use Docker Hub credentials for CI release tasks
2 years ago
<<: *docker-resource-source
Generate release notes in release pipeline This commit adds new tasks to the release pipeline, generating release notes automatically using the issues in the current milestone and pushing that as the content of the GitHub release. Closes gh-25922
4 years ago
<<: *github-task-params
- put: github-release
params:
<<: *changelog-task-params
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
groups:
Configure Concourse release pipeline Closes gh-25911
4 years ago
- name: "builds"
Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339
2 years ago
jobs: ["build", "jdk21-build"]
Configure Concourse release pipeline Closes gh-25911
4 years ago
- name: "releases"
Polish CI pipeline
4 years ago
jobs: ["stage-milestone", "stage-rc", "stage-release", "promote-milestone", "promote-rc", "promote-release", "create-github-release"]
Configure Concourse release pipeline Closes gh-25911
4 years ago
- name: "ci-images"
Polish CI pipeline
4 years ago
jobs: ["build-ci-images"]