[jbosstools-issues] [JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
Nick Boldt (JIRA)
issues at jboss.org
Fri Apr 29 14:54:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199282#comment-13199282 ]
Nick Boldt commented on JBIDE-13671:
------------------------------------
I'd be OK dropping the Alpha/Beta/CR/Final/GA thing too, but that's a harder one to sell. In that case if nothing changes between an Alpha and a Beta build, the install delta would be that much smaller, rather than requiring users to install everything all over again simply because we decided identical commit in Github should now be called "Beta" instead of "Alpha".
The problem with the "w" prefix is that once you've done a `mvn install` to get those bits into your local ~/,m2 so they're available for a downstream build to use (eg., API change in Base, build Base, then build Server to verify) you can't easily remove them from your ~/.m2 cache, and newer builds from remote will be seen as older because the "w" will always beat the "v". So... it's more manual cleanup required (and more downloading the internet). Our current workflow using "v" for both local and remote is better -- it will work for the exact usecase you describe: "install nightly build and then update it [from] local build to test your fixes."
The major benefit here is that as we start releasing more frequently (eg., weekly integration builds for QE & downstream consumption by DP installer), the changes between each build will be literally smaller, rather than just looking smaller, Auditing will be simpler because we won't have to check plugins' contents for changes - we can trust that the timestamp shows when the plugin was ACTUALLY last changed in Github.
So yes, it's worth it. We've been trying to make this change for 3 years. We tested it for Locus and it works great there. No reason not to roll it out to the rest of the team.
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list