bosh-cli | BOSH CLI v2+ | Cloud library
kandi X-RAY | bosh-cli Summary
kandi X-RAY | bosh-cli Summary
BOSH CLI v2+
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 bosh-cli
bosh-cli Key Features
bosh-cli Examples and Code Snippets
Community Discussions
Trending Discussions on bosh-cli
QUESTION
It's not clear for me from the documentation if it's even possible to pass one job's output to the another job (not from task to task, but from job to job).
I don't know if conceptually I'm doing the right thing, maybe it should be modeled differently in Concourse, but what I'm trying to achieve is having pipeline for Java project split into several granular jobs, which can be executed in parallel, and triggered independently if I need to re-run some job.
How I see the pipeline:
- First job:
- pulls the code from github repo
- builds the project with maven
- deploys artifacts to the maven repository (
mvn deploy
) - updates
SNAPSHOT
versions of the Maven project submodules - copies artifacts (jar files) to the output directory (
output
of thetask
)
- Second job:
- picks up
jar
's from theoutput
- builds docker containers for all of them (in parallel)
- picks up
- Pipeline goes on
I was unable to pass the output
from job 1 to job 2.
Also, I am curious if any changes I introduce to the original git repo resource will be present in the next job (from job 1 to job 2).
So the questions are:
- What is a proper way to pass build state from job to job (I know, jobs might get scheduled on different nodes, and definitely in different containers)?
- Is it necessary to store the state in a resource (say, S3/git)?
- Is the Concourse stateless by design (in this context)?
- Where's the best place to get more info? I've tried the manual, it's just not that detailed.
What I've found so far:
output
s are not passed from job to job- Any changes to the resource (
put
to the github repo) are fetched in the next job, but changes in working copy are not
Minimal example (it fails if commented lines are uncommented with error: missing inputs: gist-upd, gist-out
):
ANSWER
Answered 2018-Jun-30 at 19:25To answer your questions one by one.
- All build state needs to be passed from job to job in the form of a resource which must be stored on some sort of external store.
- It is necessary to store on some sort of external store. Each resource type handles this upload and download itself, so for your specific case I would check out this maven custom resource type, which seems to do what you want it to.
- Yes, this statelessness is the defining trait behind concourse. The only stateful element in concourse is a resource, which must be strictly versioned and stored on an external data store. When you combine the containerization of tasks with the external store of resources, you get the guaranteed reproducibility that concourse provides. Each version of a resource is going to be backed up on some sort of data store, and so even if the data center that your ci runs on is to completely fall down, you can still have strict reproducibility of each of your ci builds.
- In order to get more info I would recommend doing a tutorial of some kind to get your hands dirty and build a pipeline yourself. Stark and wayne have a tutorial that could be useful. In order to help understand resources there is also a resources tutorial, which might be helpful for you specifically.
Also, to get to your specific error, the reason that you are seeing missing inputs
is because concourse will look for directories (made by resource gets
) named each of those inputs. So you would need to get
resource instances named gist-upd
and gist-out
prior to to starting the task.
QUESTION
I have an issue with ansible. I am attempting to install some software which requires a auto-generated certificate. The certificate is auto-generated each time the install is run.
I run the command to pull the certificate out of a settings file.
...ANSWER
Answered 2017-Jun-26 at 12:29Your error is that the shell used (/bin/sh
) does not handle the '<(cmd)' syntax
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install bosh-cli
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