should I just push to the repo or would it be easier to re-fork as it's a
completely new code?
On Monday, November 3, 2014 9:26:16 AM UTC+2, Oleg Nenashev wrote:
Elad, you should have an access to the plugin now. As I see, R. Tyler also
supported changes in the plugin.
You can just start
(replies inline)
On Mon, 03 Nov 2014, Elad Shmitanka wrote:
should I just push to the repo or would it be easier to re-fork as it's a
completely new code?
I would force push a new history to the repo if I were in your shoes :)
On Monday, November 3, 2014 9:26:16 AM UTC+2, Oleg Nenashev
for some reason I can't access the repo, I get asked for credentials.
double checked my configuration and my rsa key, can you please check the
permissions again?
thanks
On Monday, November 3, 2014 8:22:16 PM UTC+2, R Tyler Croy wrote:
(replies inline)
On Mon, 03 Nov 2014, Elad Shmitanka
Elad, you should have an access to the plugin now. As I see, R. Tyler also
supported changes in the plugin.
You can just start merging your functionality into the plugin.
If you want to get a review for your changes, you can always create pull
requests to the plugin (and merge them on your
Thanks Tyler
About invoking vagrant on another process, are you referring to the fact
that Jenkins kills it's sub processes in the end of the build during
cleanup?
Oleg, How can we continue?
On Tuesday, October 28, 2014 5:50:30 PM UTC+2, R Tyler Croy wrote:
(replies inline)
On Wed, 22 Oct
Added R. Tyler to Cc.
Even if the plugin is not maintained now, I'm sure that he will provide
some feedback.
Best regards,
Oleg Nenashev
2014-10-22 9:45 GMT+04:00 Elad Shmitanka elad.shmita...@gmail.com:
The current vagrant plugin isn't mailntained and tries to run the vagrant
on the jenkins
I know there is one, it's old, not maintained and not working
I'd be happy to publish it, although it doesn't support ALL operations
(more to come)
Plugin name: vagrant
Github-ID: ShimiTaNaka
Existing github: https://github.com/myheritage/jenkins-vagrant
Thanks
--
You received this message
Hello Elad,
Jenkins already has a plugin for Vagrant:
https://wiki.jenkins-ci.org/display/JENKINS/Vagrant+Plugin
- What new functionality does your plugin introduce? Descriptions are
very similar
- Is it possible to merge the existing functionality to the existing
plugin?
BR,
The current vagrant plugin isn't mailntained and tries to run the vagrant
on the jenkins host and not on the node (according to what I've tries to
run)
The new plugin will also support more option such as creating a box,
suspend a box, and possibly also use vagrant cloud.
The current plugin
