On Tuesday, March 22, 2016 at 3:25:17 PM UTC-4, Patrick van der Velde wrote: > > Hi Victor > > Well that's a good start. Being able to verify that the configuration > works is good. However I would really prefer having some kind of UI to > create the configurations to make it easier for users to edit their > configurations. I'm guessing there are no plug-ins that allow me to achieve > this. > > Thanks > > We do a variant of this where our makefiles contain a build timestamp which is needed by our application and we want it captured so if we ever rebuild, we can exactly reproduce the binary (sha1 match on binary)
1) Setup your build job as normal, except do NOT use the delete workspace before building option. If you do, this strategy wont work. 2) Run the build once to initialize your workspace to the scm you are connecting to. 3) Update your build job to have a pre-scm step that compares the job's config.xml with a copy that exists in your workspace repository: If the config.xml does not exist in the workspace, copy it local and commit it to your repository. If the config,xml exists in the workspace, and is different, then copy it local and commit the changes to the repository. If the config.xml exists and is the same as the workspace, do nothing. After adding the pre-scm step, your config.xml will be evaluated and saved to the repository if modified. Since this happens before the SCM step, then the revision that actually gets built will contain the correct config.xml for the build. -- 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/34b8a930-1934-4a12-b3ab-6addfdb65ef1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
