Branch: refs/heads/master
Home: https://github.com/jenkinsci/backend-update-center2
Commit: af11a39575b023d5220dfa1b732528c87c6e4d0b
https://github.com/jenkinsci/backend-update-center2/commit/af11a39575b023d5220dfa1b732528c87c6e4d0b
Author: Kohsuke Kawaguchi <[email protected]>
Date: 2014-11-05 (Wed, 05 Nov 2014)
Changed paths:
M src/main/java/org/jvnet/hudson/update_center/Main.java
Log Message:
-----------
Generaet the file that captures the cap information
Commit: de28fd5dc3d8c6170f46f2b3f3b8ffda784ec396
https://github.com/jenkinsci/backend-update-center2/commit/de28fd5dc3d8c6170f46f2b3f3b8ffda784ec396
Author: Kohsuke Kawaguchi <[email protected]>
Date: 2014-11-05 (Wed, 05 Nov 2014)
Changed paths:
M src/main/java/org/jvnet/hudson/update_center/Main.java
M
src/main/java/org/jvnet/hudson/update_center/VersionCappedMavenRepository.java
Log Message:
-----------
Control the cap for plugins and the core separately.
For example, UC for mainline Jenkins (1.532,1.545] should only show plugins
that are compatible up to 1.545,
but it should still advertise the latest core release, say 1.590.
This is different from UC for LTS Jenkins 1.545.x, which should only show
plugins that are compatible up to 1.545.x,
and it should only advertise core up to 1.545.x
To control this separately, we need two switches.
Compare:
https://github.com/jenkinsci/backend-update-center2/compare/8b7b031ae2b9...de28fd5dc3d8
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" 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.
