In the concourse folder you can find all the necessary scripts and setup to run Concourse demo.
In the docs section you have the whole documentation of the project.
In the jenkins folder you can find all the necessary scripts and setup to run Jenkins demo.
This repository can be treated as a template for your pipeline. We provide some opinionated implementation that you can alter to suit your needs. The best approach to use it to build your production projects would be to download the Spring Cloud Pipelines repository as ZIP, then -init a Git project there and modify it as you wish.
$ curl -LOk https://github.com/spring-cloud/spring-cloud-pipelines/archive/v1.0.0.M6.zip -$ unzip v1.0.0.M6.zip -$ cd spring-cloud-pipelines-v1.0.0.M6 +init a Git project there and modify it as you wish.$ # pass the branch (e.g. master) or a particular tag (e.g. v1.0.0.RELEASE) +$ SC_PIPELINES_RELEASE=... +$ curl -LOk https://github.com/spring-cloud/spring-cloud-pipelines/archive/${SC_PIPELINES_RELEASE}.zip +$ unzip ${SC_PIPELINES_RELEASE}.zip +$ cd spring-cloud-pipelines-${SC_PIPELINES_RELEASE} $ git init $ # modify the pipelines to suit your needs $ git add . diff --git a/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_faq.html b/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_faq.html index 051f02d9..c951ef98 100644 --- a/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_faq.html +++ b/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_faq.html @@ -22,14 +22,14 @@ scripts without changing the whole pipeline.
git tag -l | xargs -n 1 git push --delete origin- by default we assume that you have jdk with id
jdk8configured - if you want a different one just override
JDK_VERSIONenv var and point to the proper one
![[Tip]](images/tip.png) | Tip |
|---|---|
The docker image comes in with Java installed at |
To change the default one just follow these steps:
-
-
-
-
+
+
+
+
And that’s it!
With scripted that but if you needed to this manually then this is how to do it:
-
-
-
No problem, just set the property / env var to true
AUTO_DEPLOY_TO_STAGEto automatically deploy to stageAUTO_DEPLOY_TO_PRODto automatically deploy to prod
No problem, just set the API_COMPATIBILITY_STEP_REQUIRED env variable
+
+
+
No problem, just set the property / env var to true
AUTO_DEPLOY_TO_STAGEto automatically deploy to stageAUTO_DEPLOY_TO_PRODto automatically deploy to prod
No problem, just set the API_COMPATIBILITY_STEP_REQUIRED env variable
to false and rerun the seed (you can pick it from the seed
job’s properties too).
When you get sth like this:
19:01:44 stderr: remote: Invalid username or password. 19:01:44 fatal: Authentication failed for 'https://github.com/marcingrzejszczak/github-webhook/' diff --git a/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_pipeline_common.html b/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_pipeline_common.html index f003a9bf..0b02713b 100644 --- a/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_pipeline_common.html +++ b/spring-cloud-pipelines/1.0.0.M7/multi/multi__jenkins_pipeline_common.html @@ -59,15 +59,15 @@ of Java installation and the others to another one.
Configure of the build step and modify the Git name / email.
If you want to set it globally you’ll have to remove the section from the build
step and follow these steps to set it globally.You can set Git email / user globally like this:
-
-
-
+
+
+
The scripts will need to access the credential in order to tag the repo.
You have to set credentials with id: git.
Below you can find instructions on how to set a credential (e.g. for Cloud Foundry cf-test credential but
remember to provide the one with id git).
-
-
-
-
Figure 7.7. Fill out the user / password and provide the git credential ID (in this example cf-test)
+
+
+
+
Figure 7.7. Fill out the user / password and provide the git credential ID (in this example cf-test)
![[Warning]](images/warning.png)
![[Important]](images/important.png)
