Answers: <p>No, there still isn't any common practice for this since this is not very common.</p>
  
  <p>I would recommend you to create a <code>Development Jenkins Environment</code> and run tests against it. Right now you will have to do that from scratch since there are not many open source repositories that could help you.</p>
  
  <p>So, how does this <code>Jenkins Development Environment</code> look like?</p>
  
  <p>For me it is a <code>docker-compose</code> file that you can run and get everything you need. If you can automate the creation of the jobs it will be a plus.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-02-28T21:31:33.253Z
Answers: actually we have a quite large infrastructure, deployed via ansible, and we got a verification environment which is topologically equivalent to production, so that would not be a problem. I was more interested in validation practices we could automate, as we build more from than 300 project repositories, there are a few thousand jobs spread across a few jenkins masters. still get my +1 as running such a task on a test environment is totally necessary
Answers: ᴳᵁᴵᴰᴼ
Answers: CC BY-SA 3.0
Answers: 2017-02-28T21:47:18.850Z
Answers: Oh, I see. And as long as I could know and image, I don't think that what you are asking exists. But maybe I am wrong.
Answers: Gepser Hoil
Answers: CC BY-SA 3.0
Answers: 2017-02-28T21:14:45.287Z
Answers: 2017-02-28T21:53:53.553Z
Answers: 2017-02-28T21:53:53.553Z
Answers: Gepser Hoil
Body: <p>Is there a common practice for migrating a large repository of Jenkins job-dsl to Jenkins2 pipelines? I am looking for ways to test the behaviour of builds, that go a little further than comparison of generated artifact from same code base.</p>
  
  <p>Actually we have a quite large infrastructure, deployed via Ansible, and we got a verification environment which is topologically equivalent to production, so that would not be a problem. I am more interested in validation practices we could automate, as we build more from than 300 project repositories, there are a few thousand jobs spread across a few Jenkins masters.</p>
  
Tags: <jenkins><job-dsl><jenkins2>
Title: How to upgrade job-dsl files to Jenkins 2 pipelines?
UserDisplayName: ᴳᵁᴵᴰᴼ
ThreadText: # How to upgrade job-dsl files to Jenkins 2 pipelines?
  
  (Asked by: username_0 on 2017-02-28)
  
  Is there a common practice for migrating a large repository of Jenkins job-dsl to Jenkins2 pipelines? I am looking for ways to test the behaviour of builds, that go a little further than comparison of generated artifact from same code base.
  
  Actually we have a quite large infrastructure, deployed via Ansible, and we got a verification environment which is topologically equivalent to production, so that would not be a problem. I am more interested in validation practices we could automate, as we build more from than 300 project repositories, there are a few thousand jobs spread across a few Jenkins masters.
  
  **Tags:** jenkins, job-dsl, jenkins2
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-02-28. Score: 6
  
  No, there still isn't any common practice for this since this is not very common.
  
  I would recommend you to create a `Development Jenkins Environment` and run tests against it. Right now you will have to do that from scratch since there are not many open source repositories that could help you.
  
  So, how does this `Jenkins Development Environment` look like?
  
  For me it is a `docker-compose` file that you can run and get everything you need. If you can automate the creation of the jobs it will be a plus.
  
  > **Comments:**
  > **username_0**: actually we have a quite large infrastructure, deployed via ansible, and we got a verification environment which is topologically equivalent to production, so that would not be a problem. I was more interested in validation practices we could automate, as we build more from than 300 project repositories, there are a few thousand jobs spread across a few jenkins masters. still get my +1 as running such a task on a test environment is totally necessary  
  > **username_1**: Oh, I see. And as long as I could know and image, I don't think that what you are asking exists. But maybe I am wrong.  
  
  ---
  
  