Please forgive is this is something obvious. I'm pretty new to jenkins. First relevant configuration info: Jenkins 1.608 Java 1.6.0_39 (but 1.7 and 1.8 are installed if needed)
Here's the scenario. We have a list of jobs that build software projects. These are 'golden' (production) and we don't want to take a chance on playing with these live until tested first. These jobs call pre/post build scripts from a hard coded directory. We'd like to let people working with the builds to make changes without changing anything in that "golden" architecture (pre/post build scripts or the job's config.xml). Additionally, we have a good amount of jobs in jenkins and don't want to add 'test' versions for every job that is in there as it would be visually cumbersome. What I'd like to do: Run a one-off job that doesn't have an entry in the jenkins UI and get output all from command line. One that we'd have a config.xml for as a copy of the one on the system with maybe tweaks if needed. I was hoping something like "build <testjobname> <config.xml>" where the user can tweak the config.xml to point to a test directory for the pre/post build scripts (parts that change most). Any suggestions? Is this possible and I'm missing it or do we "have" to have a test entry in the jenkins UI as a container? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4a527b89-4a53-4f72-9a1b-e48bb934d8ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
