Roadmap to 1.0

[KostyaSha]

Let's try summarise what is really required to be 1.0:

• unbundle launchers and add JNLP launcher (allows choosing connection variant with different credentials) Launchers #234
• connection robustness (reconnections, etc) Wait for SSH Connectivity before delegating to SSH Launcher. #150 Waiter until ssh connection can be estabilished #230
• pulling improvements Feature request: A check box for specifying whether to pull the corresponding repository before launching the container #79 Refactor for pull strategy + pull strategy #289 (0.11.0)
• integrational tests and ath
• release JNLP launcher as experimental (should bypass Running Jenkins on Docker and using docker-plugin #206 jenkins server and slaves are running as containers in the same host #219)
• actions for tagging, pushing to registry https://github.com/jenkinsci/docker-plugin/labels/tag
• Support for TLS Feature Request: Support for TLS #245 (review as it should work but doesn't?)
• rework docker builder ( UI fix + Builder readable text output #296 ...)
• swarm integration ( feat(DockerCloud): option to use docker hostname as slave display name #299 )
• unbundle docker connection credentials (?)
• review steps integrations into possible flows (Connect between docker slave to created container as a build step #301)
• load/performance Docker overloaded jenkins with slaves #221
• imho migrate to Lists instead arrays and keep data migration (or even wrote new DockerContainerConfiguration or DockerTemplateBase2 class that will have Lists, Describable, migrate to it and simply reuse from other places)
• share templates configuration between clouds share templates configuration between clouds #238
• other refactoring move all logic for getting docker client to separate class #231
• Review security
• check API exposing
• logging (Docker cloud provisioning is good now, but time measurement logging TODO)
• ...
• functional tests (@lanwen very want to help), after code base will be stable/simplified
• check/update documentation

I think we can slowly releasing 0.10.0, 0.11.0 and etc with small portions of changes and when everything will work do final 1.0

[KostyaSha]

@magnayn @thomassuckow 📟
First item was picked suddenly, i found this very interesting and started PoC, then found that UI and Templates part can be simplified.

[magnayn]

+1 for doing 0.10.0 etc.

[] It strikes me that the templates should be defined outside of the clouds so they can be reused. (I have a 'build cluster' of 5 or 6 machines, and I end up having to specify the jenkins image for each.

[KostyaSha]

@magnayn i think you must use swarm that is compatible by API and can spread containers load.
Btw i will do 0.9.0 today, have good feedback for current master.

[KostyaSha]

@magnayn seems i got your idea.
UPD created separate issue

[KostyaSha]

If launchers unbundling failure, i will skip it and merge @lanwen commit and continue doing other items.

[KostyaSha]

Didn't end small few things, 0.10.1 will be released as soon as i can.

[KostyaSha]

Moved integration tests on the first place, i'm slowly designing them, hope other features implementation will be unlocked after it.

[KostyaSha]

Shifting 0.16.0 on this weekend as i was very busy :(

[KostyaSha]

As soon as @magnayn don't care in cooperation work on this plugin and doing commits into master i don't want maintain/enhance this plugin. Good luck with ASAP commits into master.