Hi Mark—

That’s a good point… I’m publishing to Artifactory though, and was hoping to 
use the build number as a folder name. Looks like the build description is 
available so I could use that to set the folder on Artifactory.

Thanks for the link.

Allen



From: [email protected] 
[mailto:[email protected]] On Behalf Of Mark Waite
Sent: Thursday, March 30, 2017 11:07 AM
To: [email protected]
Subject: Re: Custom build number in pipeline

Wouldn't it be better to set the build description to that value, rather than 
the build number?  Keeping the build number as entirely managed by Jenkins 
seems more likely to always generate unique values for the build number.

http://stackoverflow.com/questions/36501203/jenkins-pipeline-plugin-set-the-build-description
 describes how to set build description.

Mark Waite

On Thu, Mar 30, 2017 at 10:03 AM Allen Fisher 
<[email protected]<mailto:[email protected]>> wrote:
Hi All—

We have a peculiar version numbering scheme that we use for some of our 
products… it comes from the particular world that our products live in:

R02M3210101

This “build number” comes from a database lookup after a component is built. 
The gradle/ant build that packages the build looks up this number no problem 
and uses it to build the installer. Is it possible to have the gradle build 
pass this up to the pipeline and set it as the Jenkins build number? I’m 
looking ahead to when I roll out this system to testers and support and the 
need to look at a build and know which one it is… the normal Jenkins build 
number doesn’t convey the right amount of information necessary to post.

Thanks!

Allen

[http://static.helpsystems.com/hs/email/templates/signatures-final/images/hs-logo2.png]

Allen Fisher
Build and Release Engineer


[http://static.helpsystems.com/hs/email/templates/signatures-final/images/social-linkedin.jpg]<https://www.linkedin.com/company/helpsystems-llc>
 
[http://static.helpsystems.com/hs/email/templates/signatures-final/images/social-twitter.jpg]
 <https://twitter.com/HelpSystemsMN>



--
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]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/83cee047f5464ef2905895c3dec6e051%40EDPREXCH01.helpsystems.com<https://groups.google.com/d/msgid/jenkinsci-users/83cee047f5464ef2905895c3dec6e051%40EDPREXCH01.helpsystems.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEpr1q1DUn%2B_Fvph2EtR5okjkY6yNt6TrRuyFMRhtfP3Q%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEpr1q1DUn%2B_Fvph2EtR5okjkY6yNt6TrRuyFMRhtfP3Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
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/4b509855b5dc4496a8a2924dba37bfa9%40EDPREXCH01.helpsystems.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to