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.
21146 Commits
19 Branches
274 Tags
318 MiB
Tree: 0584c289ab
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0584c289ab'
${ noResults }
src-spring-framework/ci/pipeline.yml

368 lines
12 KiB
Raw Normal View History Unescape

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:
- name: artifactory-resource
type: docker-image
source:
repository: springio/artifactory-resource
tag: 0.0.12-SNAPSHOT
- name: github-status-resource
type: docker-image
source:
repository: dpb587/github-status-resource
tag: master
- name: email
type: docker-image
source:
repository: pcfseceng/email-resource
tag: 1.0.19
- name: slack-notification
type: docker-image
source:
repository: cfcommunity/slack-notification-resource
tag: latest
resources:
- name: git-repo
type: git
icon: github-circle
source:
uri: ((github-repo))
username: ((github-username))
password: ((github-password))
branch: ((branch))
Run JDK variants builds once a day See gh-22490
5 years ago
- name: every-morning
type: time
Add link to Gradle build scan in Slack notifications See gh-22490
5 years ago
icon: alarm
Run JDK variants builds once a day See gh-22490
5 years ago
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: ci-images-git-repo
type: git
icon: github-circle
source:
uri: ((github-repo))
branch: ((branch))
paths: ["ci/images/*"]
- name: spring-framework-ci-image
type: docker-image
icon: docker
source:
repository: ((docker-hub-organization))/spring-framework-ci-image
username: ((docker-hub-username))
password: ((docker-hub-password))
tag: 5.3.x
- name: spring-framework-jdk11-ci-image
type: docker-image
icon: docker
source:
repository: ((docker-hub-organization))/spring-framework-jdk11-ci-image
username: ((docker-hub-username))
password: ((docker-hub-password))
tag: 5.3.x
- name: spring-framework-jdk14-ci-image
type: docker-image
icon: docker
source:
repository: ((docker-hub-organization))/spring-framework-jdk14-ci-image
username: ((docker-hub-username))
password: ((docker-hub-password))
tag: 5.3.x
- name: spring-framework-jdk15-ci-image
type: docker-image
icon: docker
source:
repository: ((docker-hub-organization))/spring-framework-jdk15-ci-image
username: ((docker-hub-username))
password: ((docker-hub-password))
tag: 5.3.x
- 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
- name: repo-status-jdk11-build
type: github-status-resource
icon: eye-check-outline
source:
repository: ((github-repo-name))
access_token: ((github-ci-status-token))
branch: ((branch))
context: jdk11-build
- name: repo-status-jdk14-build
type: github-status-resource
icon: eye-check-outline
source:
repository: ((github-repo-name))
access_token: ((github-ci-status-token))
branch: ((branch))
context: jdk14-build
- name: repo-status-jdk15-build
type: github-status-resource
icon: eye-check-outline
source:
repository: ((github-repo-name))
access_token: ((github-ci-status-token))
branch: ((branch))
context: jdk15-build
- name: slack-alert
type: slack-notification
icon: slack
source:
url: ((slack-webhook-url))
jobs:
- name: build-spring-framework-ci-images
plan:
- get: ci-images-git-repo
trigger: true
- in_parallel:
- put: spring-framework-ci-image
params:
build: ci-images-git-repo/ci/images
dockerfile: ci-images-git-repo/ci/images/spring-framework-ci-image/Dockerfile
- put: spring-framework-jdk11-ci-image
params:
build: ci-images-git-repo/ci/images
dockerfile: ci-images-git-repo/ci/images/spring-framework-jdk11-ci-image/Dockerfile
- put: spring-framework-jdk14-ci-image
params:
build: ci-images-git-repo/ci/images
dockerfile: ci-images-git-repo/ci/images/spring-framework-jdk14-ci-image/Dockerfile
- put: spring-framework-jdk15-ci-image
params:
build: ci-images-git-repo/ci/images
dockerfile: ci-images-git-repo/ci/images/spring-framework-jdk15-ci-image/Dockerfile
- name: build
serial: true
public: true
plan:
- get: spring-framework-ci-image
- get: git-repo
trigger: true
- put: repo-status-build
params: { state: "pending", commit: "git-repo" }
- do:
- task: build-project
privileged: true
timeout: ((task-timeout))
image: spring-framework-ci-image
file: git-repo/ci/tasks/build-project.yml
params:
BRANCH: ((branch))
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))
on_failure:
do:
- put: repo-status-build
params: { state: "failure", commit: "git-repo" }
- put: slack-alert
params:
Add link to Gradle build scan in Slack notifications See gh-22490
5 years ago
text: >
:concourse-failed: ${BUILD_PIPELINE_NAME} ${BUILD_JOB_NAME} failed!
[<https://ci.spring.io/teams/${BUILD_TEAM_NAME}/pipelines/${BUILD_PIPELINE_NAME}/jobs/${BUILD_JOB_NAME}/builds/${BUILD_NAME}|build log>]
[<$TEXT_FILE_CONTENT|build scan>]
text_file: git-repo/build/build-scan-uri.txt
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
silent: true
icon_emoji: ":concourse:"
username: concourse-ci
- put: repo-status-build
params: { state: "success", commit: "git-repo" }
- put: artifactory-repo
params: &artifactory-params
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:
Fix Artifactory properties on published artifacts This commit fixes the file pattern for the published zip artifacts. Prior to this commit, the pattern was wrong and properties were not applied to the published archives, preventing them from being published automatically (javadoc, reference documentation, schemas...). See gh-22490
5 years ago
- "/**/spring-*.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:
Fix Artifactory properties on published artifacts This commit fixes the file pattern for the published zip artifacts. Prior to this commit, the pattern was wrong and properties were not applied to the published archives, preventing them from being published automatically (javadoc, reference documentation, schemas...). See gh-22490
5 years ago
- "/**/spring-*-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:
Fix Artifactory properties on published artifacts This commit fixes the file pattern for the published zip artifacts. Prior to this commit, the pattern was wrong and properties were not applied to the published archives, preventing them from being published automatically (javadoc, reference documentation, schemas...). See gh-22490
5 years ago
- "/**/spring-*-dist.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": "dist"
- include:
Fix Artifactory properties on published artifacts This commit fixes the file pattern for the published zip artifacts. Prior to this commit, the pattern was wrong and properties were not applied to the published archives, preventing them from being published automatically (javadoc, reference documentation, schemas...). See gh-22490
5 years ago
- "/**/spring-*-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
- name: jdk11-build
serial: true
public: true
plan:
- get: spring-framework-jdk11-ci-image
Fix JDK variants jobs inputs The git repository input was missing. See gh-22490
5 years ago
- get: git-repo
Run JDK variants builds once a day See gh-22490
5 years ago
- get: every-morning
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
trigger: true
- put: repo-status-jdk11-build
params: { state: "pending", commit: "git-repo" }
- do:
Only run checks in pipelines with JDK variants This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490
5 years ago
- task: check-project
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
privileged: true
timeout: ((task-timeout))
image: spring-framework-jdk11-ci-image
Only run checks in pipelines with JDK variants This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490
5 years ago
file: git-repo/ci/tasks/check-project.yml
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:
BRANCH: ((branch))
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))
on_failure:
do:
- put: repo-status-jdk11-build
params: { state: "failure", commit: "git-repo" }
- put: slack-alert
params:
Add link to Gradle build scan in Slack notifications See gh-22490
5 years ago
text: >
:concourse-failed: ${BUILD_PIPELINE_NAME} ${BUILD_JOB_NAME} failed!
[<https://ci.spring.io/teams/${BUILD_TEAM_NAME}/pipelines/${BUILD_PIPELINE_NAME}/jobs/${BUILD_JOB_NAME}/builds/${BUILD_NAME}|build log>]
[<$TEXT_FILE_CONTENT|build scan>]
text_file: git-repo/build/build-scan-uri.txt
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
silent: true
icon_emoji: ":concourse:"
username: concourse-ci
- put: repo-status-jdk11-build
params: { state: "success", commit: "git-repo" }
- name: jdk14-build
serial: true
public: true
plan:
- get: spring-framework-jdk14-ci-image
Fix JDK variants jobs inputs The git repository input was missing. See gh-22490
5 years ago
- get: git-repo
Run JDK variants builds once a day See gh-22490
5 years ago
- get: every-morning
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
trigger: true
- put: repo-status-jdk14-build
params: { state: "pending", commit: "git-repo" }
- do:
Only run checks in pipelines with JDK variants This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490
5 years ago
- task: check-project
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
privileged: true
timeout: ((task-timeout))
image: spring-framework-jdk14-ci-image
Only run checks in pipelines with JDK variants This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490
5 years ago
file: git-repo/ci/tasks/check-project.yml
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:
BRANCH: ((branch))
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))
on_failure:
do:
- put: repo-status-jdk14-build
params: { state: "failure", commit: "git-repo" }
- put: slack-alert
params:
Add link to Gradle build scan in Slack notifications See gh-22490
5 years ago
text: >
:concourse-failed: ${BUILD_PIPELINE_NAME} ${BUILD_JOB_NAME} failed!
[<https://ci.spring.io/teams/${BUILD_TEAM_NAME}/pipelines/${BUILD_PIPELINE_NAME}/jobs/${BUILD_JOB_NAME}/builds/${BUILD_NAME}|build log>]
[<$TEXT_FILE_CONTENT|build scan>]
text_file: git-repo/build/build-scan-uri.txt
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
silent: true
icon_emoji: ":concourse:"
username: concourse-ci
- put: repo-status-jdk14-build
params: { state: "success", commit: "git-repo" }
- name: jdk15-build
serial: true
public: true
plan:
- get: spring-framework-jdk15-ci-image
Fix JDK variants jobs inputs The git repository input was missing. See gh-22490
5 years ago
- get: git-repo
Run JDK variants builds once a day See gh-22490
5 years ago
- get: every-morning
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
trigger: true
- put: repo-status-jdk15-build
params: { state: "pending", commit: "git-repo" }
- do:
Only run checks in pipelines with JDK variants This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490
5 years ago
- task: check-project
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
privileged: true
timeout: ((task-timeout))
image: spring-framework-jdk15-ci-image
Only run checks in pipelines with JDK variants This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490
5 years ago
file: git-repo/ci/tasks/check-project.yml
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:
BRANCH: ((branch))
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))
on_failure:
do:
- put: repo-status-jdk15-build
params: { state: "failure", commit: "git-repo" }
- put: slack-alert
params:
Add link to Gradle build scan in Slack notifications See gh-22490
5 years ago
text: >
:concourse-failed: ${BUILD_PIPELINE_NAME} ${BUILD_JOB_NAME} failed!
[<https://ci.spring.io/teams/${BUILD_TEAM_NAME}/pipelines/${BUILD_PIPELINE_NAME}/jobs/${BUILD_JOB_NAME}/builds/${BUILD_NAME}|build log>]
[<$TEXT_FILE_CONTENT|build scan>]
text_file: git-repo/build/build-scan-uri.txt
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
silent: true
icon_emoji: ":concourse:"
username: concourse-ci
- put: repo-status-jdk15-build
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:
- get: spring-framework-ci-image
- get: git-repo
trigger: false
- task: stage
image: spring-framework-ci-image
file: git-repo/ci/tasks/stage-version.yml
params:
RELEASE_TYPE: M
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))
- put: artifactory-repo
params:
<<: *artifactory-params
repo: libs-staging-local
- put: git-repo
params:
repository: stage-git-repo
- name: promote-milestone
serial: true
plan:
- get: spring-framework-ci-image
- get: git-repo
trigger: false
- get: artifactory-repo
trigger: false
passed: [stage-milestone]
params:
download_artifacts: false
save_build_info: true
- task: promote
image: spring-framework-ci-image
file: git-repo/ci/tasks/promote-version.yml
params:
RELEASE_TYPE: M
ARTIFACTORY_SERVER: ((artifactory-server))
ARTIFACTORY_USERNAME: ((artifactory-username))
ARTIFACTORY_PASSWORD: ((artifactory-password))
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:
- name: "Build"
jobs: ["build", "jdk11-build", "jdk14-build", "jdk15-build"]
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: "Release"
jobs: ["stage-milestone", "promote-milestone"]
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"
jobs: ["build-spring-framework-ci-images"]