It's been a while since I posted to this group and I'm not in a position where I can actually try this to verify so bear with me...
Sounds like what you need is to deploy the war exploded. Easiest way to do that us to just unzip it and deploy the resulting directory in tomcat or similar app server. There is probably a way to tell the embedded winstone to deploy the directory rather than the war but just using something like tomcat would be the quickest way. Anyway, once done all you have to do is edit the static files directly in the directory & refresh your browser. On Jun 4, 2014 7:47 PM, "Kevin Burke" <[email protected]> wrote: > Hello, > I'm trying to make some changes to Javascript and CSS files in the jenkins > project. Currently, this process looks something like: > > 1. Save the new changes to the file. > > 2. Run `mvn install -pl war -am -DskipTests && java -jar > war/target/jenkins.war ` > > 3. Reload my browser tab and view the changes. > > This is a pretty slow feedback loop - it takes roughly 1 minute and 20 > seconds between making changes and seeing them, on my 1-year old macbook > pro, which means you can make roughly 30 changes an hour, if you are > completely focused while Jenkins is building and know exactly what to do > when it's not. I believe that the static files are compiled into the > binary; if there was some way to edit them outside of the WAR this would > imply that the build step could be skipped. > > Tom Fennelly pointed me in the direction of intellij which can perform > incremental builds; this is an option but would require learning intellij > and leaving my preferred text editing tools. > > I was curious though if there is a build flag which leaves the static > assets alone, allowing them to be edited and linked without having to > recompile a WAR? Or maybe a different set of flags I could pass to mvn > which would complete builds faster? Or maybe I could comment out the > compiled asset link in lib/layout/layout.jelly, and then hard code in > lib/layout/layout.jelly a link to a server running on my own computer, with > a copy of the JS/CSS in question. > > In any event if there are best practices here, or a document which > outlines best practices, I would be really grateful. I tried Googling but > mostly found answers from people trying to implement incremental builds in > their Jenkins instances. > > Thanks, > Kevin > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
