AGPUSH-937: optimize frontend cleaning workflow #355
Conversation
Could you please test this? 🏈 @matzew @secondsun @abstractj |
@@ -111,8 +108,17 @@ | |||
|
|||
<profiles> | |||
<profile> | |||
<!-- if you want to run tests, make sure you also enable 'test' profile --> | |||
<id>dev</id> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the dev
is mentioned on README (root
and admin-ui
folders). let's update those too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
@TadeasKriz @vibe13 @lholmquist Hey guys, just in case you would like to add your $0.02.. |
👍 perfect! Improved from around 2min, to 10 secs :-) |
@lfryc I still think, that the development mode is something to be opt-in, not the other way around and that "mvn clean package" should work each time without being affected by branch switches. If the second condition will be met even without the |
If you switch branches, all tooling we use will detect changes in the configuration files and behave accordiongly:
NPM/Bower won't remove packages that were downloaded before and are missing in the branch you switch to. That's where force-clean comes in. I have tested this on current versions of plugin we use and it works as expected. |
|
In that case I'm +1 on it. The main goal there is to be able to build without problems caused by uncleaned node.js caches when you checkout different commit and that should be now fixed as you said, so let's merge it! :) |
Testing it here |
It pretty much depends on network bandwidth + machine, but here I noticed the improvement
+1 Good to merge |
ZOMG ❤️ it
👍 👍 👍 👍 👍 👍 👍 👍 |
Landed at d61593d |
https://issues.jboss.org/browse/AGPUSH-937
first build of
admin-ui/
obviously takes time, but then it should cache as much things as possible, see the JIRA for reference times ^