-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"make snapshot" target for building packages from develop branch #209
Comments
Why don't you update the version with current date and time and use make rpm. |
The point here is to achieve unification of the build process for all tendrl packages, so that we can move on and build ci jobs on top of that, as has been agreed on. As far as I know, only dashboard and api packages out of all tendrl packages doesn't implement this. |
Agree!, Are you ok with the release version format to %m_%d_%Y_%H_%M_%S. |
tendrl-bug-id: Tendrl#209 Signed-off-by: Timothy Asir J <tjeyasin@redhat.com>
I have two points related to the version format:
Also please check the Package Versioning on Fedora Wiki - mainly the Snapshots section. I think that is the best format for package versioning (as it was mentioned also here usmqe/usmqe-centos-ci#1 (comment)). Just side note: as git hash is "pseudo random" string, it is not properly sortable, so it will not be possible to distinguish older and newer packages. One solution is to add full timestamp (as described above) before the hash, second solution is to prepended the hash by the number of commits from the last marked version (similarly as what |
tendrl-bug-id: Tendrl#209 Signed-off-by: Timothy Asir J <tjeyasin@redhat.com>
This issue can be closed. |
make snapshot
target is not implemented and because of that the build trigger jobs are failing:https://ci.centos.org/view/tendrl-build/job/tendrl-build-1-develop-api/
It would be good if it will be possible to build snapshot version package (usable mainly for packages from develop and prospectively from feature branches).
The text was updated successfully, but these errors were encountered: