the grunt build should produce a file specifying the build settings and information

Description

When a custom build is produced, a file should be generated specifying the date, version, revision, and command used to create it.

Environment

None

Attachments

1

Activity

Show:

Justin Obara July 16, 2024 at 5:57 PM

This was resolved with which not only moved away from using Grunt but also includes metadata about the build in a built file.

Justin Obara April 5, 2018 at 1:40 PM

I've only had time to skim over your branch so far. I think it would be easier to review as a PR though. So yes, please file one. Thanks.

Mohamed Shadab April 3, 2018 at 1:30 PM

Hey, so did you check the changes i made? If yes, should I make a PR?

Mohamed Shadab March 20, 2018 at 8:46 PM

Hey, 

I made the changes; please check them out - https://github.com/shadxx7/infusion/tree/FLUID-4731

Cheers

Justin Obara March 20, 2018 at 2:22 PM

 I took a quick look at the Gruntfile.js in your branch. Some of the values are already available in the grunt config, such as pkg, revision, branch. Can you just access these from there instead of having to recall the methods to populate the values. Also what will happen in the case of running a "grunt buildDists" which runs several custom builds and outputs them to the dist directory? It would also be good if you could add the name of the build to the header and also probably as the file name. 

Unresolved

Details

Assignee

Reporter

Components

Affects versions

Priority

Created July 19, 2012 at 6:59 PM
Updated July 16, 2024 at 5:57 PM