My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 18: version number?
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by codeto...@gmail.com, Nov 21, 2011

What is the current version number for Funcito?

We should strive to have it in one place, but it might be two places (build.gradle file and a Java constants file) for the short-term.


Nov 22, 2011
Project Member #1 kandpwel...@gmail.com
(No comment was entered for this change.)
Labels: Type-Enhancement Priority-Medium Component-Scripts
Dec 1, 2011
Project Member #2 codeto...@gmail.com
Introduced ~/resources/Funcito.properties which contains the version property. This file is distributed with binary and src jars.


Status: CodeComplete
Dec 15, 2011
Project Member #3 kandpwel...@gmail.com
Please look at:

https://funcito.ci.cloudbees.com/env-vars.html

I would like to somehow append extra build descriptors on (and in ?) the build jars when built on CloudBees, using the supplied variables.  For local builds we would just use the build target names as you have already specified.  I am trying to figure what we want to append... probably "-r${BUILD_NUMBER}" but maybe "-SNAPSHOT-${BUILD_NUMBER}".  Also, maybe use BUILD_TAG instead of BUILD_NUMBER, but that's probably too long.  Folks may rename a jar they have downloaded, so it would be good to get the build number in the jar(s) itself, perhaps in the MANIFEST or wherever it is appropriate.  I'm open to ideas.

This will be *very* good to know exactly which snapshot someone is using.  I wish we could get the GIT version id.  But we can always backtrack CB Jenkins version number to a GoogleCode GIT version, so long as we keep the version numbers around (have to look at those settings some more).
Owner: codeto...@gmail.com
Dec 16, 2011
Project Member #5 kandpwel...@gmail.com
adding milestone
Labels: Milestone-Release0.1
Dec 16, 2011
Project Member #6 codeto...@gmail.com
As a strawman, the jars will now contain buildInfo.txt which should have all of the env vars specified on that page (when built on Jenkins).

I need more specifics on the filename for the jars. That should be easy. My guess is that the MANIFEST is a better place than buildInfo.txt but this will get us started.
Status: Started
Dec 16, 2011
Project Member #7 kandpwel...@gmail.com
Awesome.  Can you put some newlines in there?

For the jar file names, I am open to suggestions.  I don't know if I am using the term snapshot properly, but I see a lot of projects that get their daily builds as:

funcito-0.1-SNAPSHOT-someVersionString.jar

others I have seen with a simple build revision #

funcito-0.1-r123-.jar

I think BUILD_NUMBER is a good starting point, and *maybe* a date-string too.

Just in case I wasn't clear, I want the name changed only when these environment variables are defined.  Otherwise (for local builds) just

funcito-0.1.jar
Dec 19, 2011
Project Member #8 codeto...@gmail.com
This has been implemented. The CI files are (by example):

funcito-SNAPSHOT-r45-19.Dec.2011.jar
funcito-src-SNAPSHOT-r45-19.Dec.2011.jar

where BUILD_NUMBER=r45

Status: CodeComplete
Dec 19, 2011
Project Member #9 kandpwel...@gmail.com
Good job. 
Status: Fixed
Dec 19, 2011
Project Member #10 kandpwel...@gmail.com
Oh, I also set CB to archive the last 60 days of build jars. 

Powered by Google Project Hosting