Hi all,
I am working on a plugin (https://github.com/jenkinsci/dotnet-sdk-plugin)
which includes a tool installer.
Currently, I am using json files as resources as a basis of this installer;
this is because I ran into two roadblocks:
- the existing DownloadFromUrlInstaller assumes architecture-independent
processing and therefore:
- does not offer label configuration
- uses a very simple flat list of install packages (and a simple 'id'
value)
- there are currently over 1000 SDK packages for .NET, so a flat
list really is not workable
- while there is code available in Jenkins core and plugins that uses
DownloadFromUrlInstaller or Downloadable, it is rather unclear to me how
the downloadable file gets on the update center to begin with (for example,
the ANt plugin does not seem to include any code that looks on
ant.apache.org for the available downloads)
The first issue is easily overcome by writing a custom installer, which I
have done.
The second is still a question mark. I found one page somewhere about
needing to write a scraper to generate the file, but that did not go into
details on what that would look like, or how to get an update center to use
it.
So, I would appreciate if you could point me to a document describing
what's involved in getting one or more Downloadables(*), or if no such
document exists, the steps required.
I would prefer having this in place before my 1.0 release.
(*) is Downloadable intended strictly for ToolInstallers only? I have two
other JSON files, now as resources, used as source for auto-completion.
They too would benefit from being kept up to date outside of a plugin
release cycle.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/ca767f7e-d5d8-4c99-973e-976199564e87%40googlegroups.com.
