The version of circle CI has been part of the problem in the question as I first linked to a 1.0 documentation which obvisouly didn't answer the question
@Aurora0001 I'm convinced someone interested in circleci 1.0 questions would not wish to see circleci2.0, and if they wish, they just have to favorite both tags
The question about "Upgrade from job-dsl to Jenkins 2 pipelines" contains these tags:
jenkins
jenkins2
Even though jenkins2 does not have any tag details yet, I bet it has to do with some specific version (or should I say release?) of Jenkins.
If my educated guess is right, then my real ques...
Agreed - sometimes the OP just dosn't know how to use the documentation to get the solution.
@Tensibai I suspect the desire to have a circleci and a circleci-2.0 will be a temporary thing. From what I understand CircleCI 1.0 users will eventually migrate to 2.0 at which point we can make 2.0 a synonym of the sans-version tag.
I've done / created lots of SCM related presentations, and now I'm trying to "upgrade" to a DevOps successor of it.
What I always try to do in my presentations, is to come up with an introduction slide which somehow includes the message I want to deliver (and which I then elaborate on in the res...
DevOps Stack Exchange is a question and answer site for software engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure.
I am working with a private repository from my organization and the Deploy key approach for authentication. The tutorials for deploy key configuration are pretty straight forward. It's just there is one confusion I have. The slave instances don't actually have jenkins installed, so is not possibl...