Opened on 09/29/2015 at 12:41:16 PM
Closed on 09/29/2015 at 03:43:01 PM
Last modified on 04/11/2017 at 04:22:36 PM
#3133 closed change (fixed)
[build] Always perform a clobber before creating a release build or devbuild
| Reported by: | fhd | Assignee: | fhd |
|---|---|---|---|
| Priority: | P3 | Milestone: | Adblock-Browser-for-Android-1.1.0 |
| Module: | Adblock-Browser-for-Android | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
Background
Our release/devbuild build automation currently doesn't perform a clobber (i.e. clean) before creating the build. This does have some side effects, however, such as the build number not changing between builds. We should always perform a clobber.
What to change
Run ./mach clobber before every build in adblockbrowser-build.
Attachments (0)
Change History (5)
comment:1 Changed on 09/29/2015 at 12:42:25 PM by fhd
- Owner set to fhd
comment:2 Changed on 09/29/2015 at 12:43:25 PM by fhd
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:3 Changed on 09/29/2015 at 03:43:01 PM by fhd
- Resolution set to fixed
- Status changed from reviewing to closed
comment:4 Changed on 04/11/2017 at 04:21:32 PM by fhd
- Milestone set to Adblock-Browser-for-Android-1.1.1
comment:5 Changed on 04/11/2017 at 04:22:36 PM by fhd
- Milestone changed from Adblock-Browser-for-Android-1.1.1 to Adblock-Browser-for-Android-1.1.0
Note: See
TracTickets for help on using
tickets.
Pushed: https://bitbucket.org/adblockplus/adblockbrowser-build/commits/e1be3e5dc0acb3f6b1b12a5c5889f8f6b1d60de3