Artur: Thank you for your response. Knowing that another project (thanks for the heads up on that one, too!) is working fine in the same manner gives me great comfort I won't be introducing any systemic problems.
Thank you again! On Wednesday, March 22, 2017 at 6:33:43 AM UTC-5, Artur Szostak wrote: > > Sounds like you implementing something similar to Jenkins Job Builder ( > https://docs.openstack.org/infra/jenkins-job-builder/ > <https://www.google.com/url?q=https%3A%2F%2Fdocs.openstack.org%2Finfra%2Fjenkins-job-builder%2F&sa=D&sntz=1&usg=AFQjCNG6uk2foDvEHr4FvDXDypyQhUaxPQ> > ). > That tool does not add plugin version numbers to the XML and it works. > Presumably as long as there is nothing particularly strange going on > between plugin upgrades. > > ------------------------------ > *From:* [email protected] <javascript:> [ > [email protected] <javascript:>] on behalf of Adam Levine [ > [email protected] <javascript:>] > *Sent:* 20 March 2017 20:45 > *To:* Jenkins Users > *Subject:* manually created config.xml and plugin version numbers > > I've templated out some jobs, using gradle file copy/token replacement and > the cli create-job with my config.xml, and all is working fine. My > question is on pieces that are plugins. > > ie > <hudson.plugins.heavy__job.HeavyJobProperty plugin="heavy-job@XXXX"> > <weight>1</weight> > </hudson.plugins.heavy__job.HeavyJobProperty> > > > I already have a process in place to extract all the current plugins and > versions and supply them, ie plugin="heavy-job@${heavy_job_plugin_version}" > > When I'm creating the config.xml to pass to the CLI create-job, does it > matter if I include the plugin version or not? I saw on a prior thread > that the version number is merely a reference to the plugin version present > when the job was created. I can't see that it's breaking anything if I > don't include the version, but I want to make sure I'm not going to shoot > myself in the foot. > > Any insight is welcome. > > Thank you ! > > > > -- > 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 [email protected] > <http://redir.aspx?REF=7jidoDN0MEb6gPXQLiZAkZ53gfFELmBu9Yhh6qejKkq8iNjAFnHUCAFtYWlsdG86amVua2luc2NpLXVzZXJzK3Vuc3Vic2NyaWJlQGdvb2dsZWdyb3Vwcy5jb20.> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/161cc74f-c219-47fe-af06-542536880682%40googlegroups.com > > <http://redir.aspx?REF=Y2HvJ6uqNLQmK9EA3WnfIpwzrFXoknKMgbO4g3vLwD68iNjAFnHUCAFodHRwczovL2dyb3Vwcy5nb29nbGUuY29tL2QvbXNnaWQvamVua2luc2NpLXVzZXJzLzE2MWNjNzRmLWMyMTktNDdmZS1hZjA2LTU0MjUzNjg4MDY4MiU0MGdvb2dsZWdyb3Vwcy5jb20_dXRtX21lZGl1bT1lbWFpbCZ1dG1fc291cmNlPWZvb3Rlcg..> > . > For more options, visit https://groups.google.com/d/optout > <http://redir.aspx?REF=nIIoI5avfs2lykk3BQbAILpWGHZvRebgEYtzVqJig3y8iNjAFnHUCAFodHRwczovL2dyb3Vwcy5nb29nbGUuY29tL2Qvb3B0b3V0> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c7cf0abd-c0e0-4d4e-953a-6e31a21b2b9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
