Possibility to customize build version with Jenkins?

We have several versions as released versions and sometimes have to fix the same issue in multiple versions. Currently we have YouTrack pulling build numbers from Jenkins and this works, however it only works for one version/branch. We don't duplicate tickets for each version where the issue will be implemented, we just use one.

Is there some way we can instruct YouTrack to prepend version numbers from Jenkins with the branch name? Then we could have tickets show "Fixed in Build: v1-234, v2.2-123" etc. We wouldn't want to add a new field for every single version and add a build system integration to monitor each build branch and have support look at several fields to know what was changed and where.

In general how do people handle multiple versions? Manually updating information?

5 comments
Comment actions Permalink

Hello,
It is not possible to add branch name before version number, unfortunately.
I can suggest using builds in Jenkins like v1-234, v2.2-123, i.e., the name itself should contain the version number.

-1
Comment actions Permalink

How would I do that? I have builds in Jenkins include the branch in the display name but YouTrack only uses the number when synchronizing the data. So even if my builds are called "v1-1234" and "v2-1234" YouTrack only shows "1234" in the list and I can't distinguish between versions.

0
Comment actions Permalink

Hello,

I'm terribly sorry for the radio silence here.

It seems that the integration indeed pulls only the build number, and not the whole build name. I've asked our developers to check it. I will keep you posted with the results.

0
Comment actions Permalink

Thank you, that would be very useful change. Then we could pull the correct build names and everything would track correcly on YouTrack.

0
Comment actions Permalink

Sami Kuhmonen

The developers have changed the way the build name is shown in YouTrack, and the corresponding fix will be released in the next major release. Feel free to subscribe to our blog to get notified once it is available.

0

Please sign in to leave a comment.