[
https://issues.apache.org/jira/browse/BEAM-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738610#comment-16738610
]
Scott Wegner commented on BEAM-6402:
------------------------------------
I previously came across this:
https://marcesher.com/2016/07/01/jenkins-as-code-creating-jobs-from-the-command-line-during-development/
Apparently, it's a tool/workflow someone built for testing Jenkins job DSL
changes locally without pushing changes to master. I won't have time to
investigate further, but this may be useful for us.
> Need ability to test Jenkins job changes without affecting live jobs
> --------------------------------------------------------------------
>
> Key: BEAM-6402
> URL: https://issues.apache.org/jira/browse/BEAM-6402
> Project: Beam
> Issue Type: New Feature
> Components: testing
> Reporter: Scott Wegner
> Priority: Minor
>
> Our Jenkins jobs are maintained in source code using the Groovy Job DSL, and
> kept up-to-date on our Apache Jenkins instance by regularly running the Seed
> Job.
> Updating jobs is pretty easy by modifying the Groovy code, but there's no way
> to validate changes other than running the Seed Job and affecting the live
> job definitions. We should have some way to validate job changes outside of
> running the Seed job on production.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
