Automated Build Scripts

[feltnerm]

I'm working on a collection of scripts that will help automate the Fine Uploader release process. The priorities are to implement a flexible, cross-browser test strategy and to standardize a build process.

Tier 1

• 3 - Add automation to release process #811 Automated Releases - This is a priority for this issue. @rnicholus, can we discuss the goals of a "proper" release?
• 3 - Automated Testing Framework #810 Automated Tests - Test stories/scenarios must be determined. Methods for cross-browser testing need to be discussed as well.
• Provide an automated service associated with Fine Uploader that handles server-side tasks #835 Development/Sandbox Server - If we really want to do some heavy testing, then we are going to have to eventually have some kind of server (for testing chunking, pause/resume, etc.).

Tier 2

• Create and publish nightly or feature (unstable) builds #812 Nightly builds - I think this is a good idea. How do we want to think about automating this? Would there be a server running a cron job or something?
• 8 - Move readme/documentation to fineuploader.com #722 Automated Documentation Builds
• 8 - Create bootstrapped "version" #698 Bootstrapped Packages - A Bootstrap/Fine Uploader hybrid could be packaged as part of the build process and hosted/linked to from the main website. There could also be other supported packages (such as the jQuery plugin, 5 - Add Angular JS support #531 Angular.JS has been mentioned, ...). Or at least just a generic packager that could be extended. This would allow a user to quickly and easily get started with Fine Uploader. Very related to 8 - Boilerplate Generator #846.
• Add support for CommonJS & AMD #789 AMD/CommonJS Support - Questionable, but adding AMD/CommonJS could affect the build. Put here just in case.

[rnicholus]

Tier 1

can we discuss the goals of a "proper" release?
Yes, let's do that tomorrow. I should document the current release process. In fact, I will. Stub at #856.

After some thought, I'm not sure nightly builds are something we should deal with/worry about anytime in the near future. I'm guessing automated documentation fits in with this as well. We can discuss more on Tuesday.

As far as development is concerned, I currently use Jetty locally, running inside of IntelliJ Ultimate. This has worked pretty well for me so far. We will each probably need our own development environment/test server anyway. This will need to be portable, so I personally think this is the way to go.

Tier 2

This is probably fairly far off in the future. We can discuss more during or sometime after story pointing on Tuesday.

[feltnerm]

One part of this process was to have Travis automatically detect pull requests to master and issue a failed test to discourage that sort of contribution. As of 6422388 this is implemented and working.

[feltnerm]

This is on Huboard as an 'In Progress' task -- really it's sort of a meta task that is supposed to keep track of other cases. I'm thinking of closing this an moving the unchecked cases into their own stories. Objections @rnicholus ?

[feltnerm]

As far as "Automated Build Scripts" go. The build process done with Grunt is automated, and it builds the library properly...

[rnicholus]

👍