11

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.

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.

  • 1
    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 – ᴳᵁᴵᴰᴼ Feb 28 '17 at 21:31
  • 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. – Gepser Feb 28 '17 at 21:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.