jenkins-plugin-ansicolor
No description set
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:tools:building/jenkins-plugin-ansicolor && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
ansicolor.hpi | 0000037638 36.8 KB | |
jenkins-plugin-ansicolor.changes | 0000000143 143 Bytes | |
jenkins-plugin-ansicolor.spec | 0000001456 1.42 KB |
Latest Revision
Martin Pluskal (pluskalm)
accepted
request 573079
from
Tomas Cech (sleep_walker)
(revision 1)
I'd like to push some packaged plugins to devel:tools:building. This is my approach so the most work is done on writing summary and description as the build is just packaging hpi file. Why to package it? To not rely on web services and version changes, to have the file tracked by RPM for changes, to have package signed. If this is OK for you, I'd push more of them (~50). I was also thinking if that can be done in some more elegant way via OBS service taking latest URL (which is redirect to location with version in path). I'd like to hear any recommendations.
Comments 0