I have a problem with the use of the spira plugin for jenkins. We have automated tests, running everyday in jenkins, now i need to get the results of those tests (result of the jobs in jenkins) into spiratest. But I cannot fill in a variable that specifies the latest deploy number. The plugin is apparently not able to translate jenkins variables, filling in the "Release Version Number" field with for example $VAR , gives as result in the log: Error sending results to SpiraTest server (Unable to locate a release with version number '$VAR' in project PR12) You can replicate this quite easily, setup a jenkins job, create a string parameter with default value filled in, fill in the spira config with project number and release version number , execute job and check the log. Right now the plugin is quite useless for us, we do NOT want to change the version number by hand every new release, deploy,... Another thing that would be nice is to specify a non-existant release version number. Now this gives the following error: A release with the version number '...' does not exist in the Spira project PR12 It would be nice if it just creates the release instead. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/integrations/bug-trackers/1090.aspxthreadId=1090Ruben Isenborghs (ruben.isenborghs@vrt.be)jenkins automation variables I have a problem with the use of the spira plugin for jenkins. We have automated tests, running everyday in jenkins, now i need to get the results of those tests (result of the jobs in jenkins) into spiratest. But I cannot fill in a variable that specifies the latest deploy number. The plugin is apparently not able to translate jenkins variables, filling in the "Release Version Number" field with for example $VAR , gives as result in the log: Error sending results to SpiraTest server (Unable to locate a release with version number '$VAR' in project PR12) You can replicate this quite easily, setup a jenkins job, create a string parameter with default value filled in, fill in the spira config with project number and release version number , execute job and check the log. Right now the plugin is quite useless for us, we do NOT want to change the version number by hand every new release, deploy,... Another thing that would be nice is to specify a non-existant release version number. Now this gives the following error: A release with the version number '...' does not exist in the Spira project PR12 It would be nice if it just creates the release instead. Thu, 04 Dec 2014 08:52:05 -05002017-05-10T08:29:19-04:00/Support/Forum/integrations/bug-trackers/1090.aspxmessageId=1945David J (adam.sandman+support@inflectra.com) Hi Ruben The ability to use variables in the release version number is a known enhancement that we are tracking. If you need it sooner than that we can supply you with the source code to the Jenkins plugin, just let us know! Regards Adam Thu, 04 Dec 2014 14:45:00 -05002014-12-04T14:45:00-05:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply1945messageId=1948Ruben Isenborghs (ruben.isenborghs@vrt.be) Hello Adam, Providing the source code of the plugin would be of great help to us! Thanks in advance Ruben Fri, 05 Dec 2014 07:29:04 -05002014-12-05T07:29:04-05:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply1948messageId=2759Patric Fox (patric.fox@onelogin.com) Any update on this enhancement? I'm in the same boat as Ruben with automation. Thu, 15 Sep 2016 18:24:17 -04002016-09-15T18:24:17-04:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply2759messageId=2761Kat A (elise.brooks@inflectra.com) Hi Patric, I looked into it and found that this enhancement has not yet been implemented. In fact, the Jenkins plugin has not been updated at all. I added a note to the enhancement in our internal SpiraTeam instance, saying that you are also interested in this feature. Regards, Elise Fri, 16 Sep 2016 13:56:06 -04002016-09-16T13:56:06-04:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply2761messageId=2805Michael Yousif (myousif@evertz.com) Any progress made on the plugin? I'm also interested in the auto-increment feature added to the plugin. Fri, 11 Nov 2016 13:45:05 -05002016-11-11T13:45:05-05:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply2805messageId=2933Jefry Denny (jefry.denny@sap.com) Any update on this feature? The original post was way back in 2014 ... ;-) Be finally nice to have this feature available. Tue, 07 Mar 2017 17:40:26 -05002017-03-07T17:40:26-05:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply2933messageId=3012Juan A Ruzafa (juanantonioruzafa@goldcar.com) Any updates on this one? Having to update manually the release number is not an option fot me. Wed, 10 May 2017 08:29:19 -04002017-05-10T08:29:19-04:00/Support/Forum/integrations/bug-trackers/1090.aspx#reply3012