pipeline-templates | Generalized pipeline templates | Continuous Deployment library
kandi X-RAY | pipeline-templates Summary
kandi X-RAY | pipeline-templates Summary
This repository collects up all that tribal wisdom we’ve gained from building Concourse Pipelines for various different purposes. Each template provides a base ci/pipeline.yml that structures the pipeline, ci/settings.yml to override any parameters defined by the template, a set of scripts (in ci/scripts/) that are referenced from the pipeline, and a ci/repipe utility for putting all the pieces together into a functioning Concourse pipeline.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pipeline-templates
pipeline-templates Key Features
pipeline-templates Examples and Code Snippets
Community Discussions
Trending Discussions on pipeline-templates
QUESTION
I have a yml
file which calls a templated stage:
ANSWER
Answered 2022-Jan-24 at 19:41So if wanted to use a variable group need to define the group to be read in:
QUESTION
Long story short, I have a mono repo that I have been using for almost a year. I had a hard drive failure and had to reinstall my OS. Now, when I try to do anything with the CDK, I get this error every time.
...ANSWER
Answered 2021-Aug-10 at 15:20Okay, I was able to get this working but I am not sure why I had to do it this way after it's been working for over a year with the current system. I even have other devs using it with no issue. Very strange.
To get this working, I had to make a simple change.
I modified cdk.json
to be:
QUESTION
We have an Azure Repository which triggers a Release-Pipeline every time something is pushed to the main branch. When a Release is triggered it shows its status (succeeded) on the right side in the commits in Azure Repos like on the following Picture:
It even shows which stage is already promoted etc. which is awesome. This all works fine when configuring the Release Pipeline Manually with the following CD-Trigger Configuration:
Even when exporting the Pipeline JSON file and reimporting it everything works as expected.
However, when creating the Release with the exact same Settings via API i don't see the Status of the Release. The trigger itself works as expected but the status in the commits is simply not there:
Does someone know which exact Setting in the Release-Pipeline.json is responsible for this status?
Here are some parts of the json body I send via API which might be missing something?
Edit: A few more information needed i guess. I use a cli-tool to create the body and send the api request. The values are templated. The template gets its values either from previous api calls or from user inputs. Here is the complete template. I created it based on the manually configured relase-pipeline JSON (Which works fine and shows the status i want).
...ANSWER
Answered 2021-Apr-01 at 02:55According to your description, I tested it and everything works as expected.
Steps:
Get the release definition via the REST API Definitions - Get and copy the response body.
QUESTION
we are using the extend feature to reuse templates in our pipelines in a secure way. For easier defining the parameters for the template I would like to use variables but I feel this is not possible.
But since I could not find an answer in the official docs I am asking in this round.
My yml file looks like this:
...ANSWER
Answered 2021-Mar-10 at 01:59Do you mean you want to use the variables to help your define the template parameters? If yes, we recommend you can use the ${{variables.VariableName}}
Here is the demo script that I changed the stages to the key words(extends):
QUESTION
I have an AzurePowerShell script (powershell/gettenants.ps1) which sets the value of the tenants variable.
The following bash task successfully echos the new value BUT the following template recieves the default value (set at the top of the script). Note Im using expression syntax when specifying the template parameter value.
Any ideas what im doing wrong?
...ANSWER
Answered 2020-May-19 at 10:28when using ${{ }}
syntax that variable is being replace at the compile time.
Read more here:
QUESTION
So I'm trying to submit a parameter in to my template deployment not sure what's wrong the other parameters are working as expected is only the new one that's not working, but if i set it to a boolean value without parameters it works.
there seems to be som variable substitution that doesn't happen and i just can't figure out why it must be something simple but i just can't find it
It's usek8s
that's not working, image from variables tab
snippet from azure-pipelines.yml when it doesn't work
...ANSWER
Answered 2020-May-11 at 03:59variable replacement not happening when using templates azure pipelines
This is a known issue and has been reported to the MS team. You could check following thread for some details:
Queue Time Variables Do Not Override Default Variable
That because we could not use queue variables to overwrite the compile time parameters.
So, MS team recently rolled out a new feature Runtime parameters, allow you to inject data into the pre-processor phases of pipeline compilation:
parameters: - name: usek8s displayName: UseUsek8s? type: boolean default: False
When we queue the pipeline, we could select if we use the usek8s
:
Hope this helps.
QUESTION
I have the following config map:
...ANSWER
Answered 2020-Mar-03 at 15:43I think the symlinks starting with ".." are created by OpenShift as part of their rollback mechanism implementation.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install pipeline-templates
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page