geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <>
Subject [jira] [Commented] (GEODE-42) Remove hard-coded SCM metadata from build
Date Tue, 02 Jun 2015 05:27:18 GMT


Anthony Baker commented on GEODE-42:

I probably wasn't very clear in the original description.  We *know* that the hard-coded source
info in the build file is incorrect and needs to be fixed.  I'm not sure what the desired
state should we *need* source info in the version properties file, particularly if
it requires a more complicated release workflow?

I think we should figure out the end state before moving forward with the patch.

> Remove hard-coded SCM metadata from build
> -----------------------------------------
>                 Key: GEODE-42
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.0.0-incubating
>            Reporter: Anthony Baker
>            Assignee: Mark Bretl
>            Priority: Minor
>         Attachments: GEODE-42-1.patch
> In gemfire-core/build.gradle the createVersionPropertiesFile task uses hard-coded source
> {code}
>     ext.gitBranch = 'master'
>     ext.commitId = '1366ff2d4fcbf54bfad684e9ba9822db2a2b0ff5'
>     ext.sourceDate = '2015-04-06 14:54:51 -0700'
> {code}
> Previously this information was obtained from SCM (e.g. invoking the git command directly).
 However, we will be releasing src tarballs and need to build from source without access to
SCM metadata.

This message was sent by Atlassian JIRA

View raw message