- 03 3月, 2017 2 次提交
-
-
由 Stephen Connolly 提交于
-
由 Stephen Connolly 提交于
-
- 16 3月, 2016 2 次提交
-
-
由 tfennelly 提交于
-
- 11 3月, 2016 2 次提交
- 09 3月, 2016 3 次提交
- 19 10月, 2015 1 次提交
-
-
由 Antonio Muñiz 提交于
(cherry picked from commit f63407a8)
-
- 06 10月, 2015 1 次提交
-
-
由 Antonio Muñiz 提交于
-
- 17 7月, 2013 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Since I don't think any other scripts depend on this one, I'm just giving it a low enough priority.
-
- 25 10月, 2012 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 22 8月, 2012 1 次提交
-
-
由 Jesse Glick 提交于
-
- 29 6月, 2012 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
One of the problems with the current way Jenkins puts JavaScripts is that most everything is in a single file. It doesn't highlight the relationship between those fragments and their corresponding tag files. So I'm experimenting with moving out these fragments into individual JavaScript files co-located with the tag file. They then get loaded into the page via <st:adjunct>. Each script is served with unique URL such that the browser will not even have to try conditional GET when loading different pages, so this should prevent the performance problem caused by the fact that there are now lots of <script> tags in the page. If for some reason even this turns out to be a problem, we can always add additional build steps to concatenate them all.
-