janik/hydra
0
0
Fork 0
forked from lix-project/hydra
Code Pull requests Activity
hydra/src/lib/Hydra/Plugin.pm

38 lines
988 B
Perl
Raw Normal View History

Add a plugin mechanism You can now add plugins to Hydra by writing a module called Hydra::Plugin::<whatever> and putting it in Perl's search path. The only plugin operation currently supported in buildFinished, called when hydra-build has finished doing a build. For instance, a Twitter notification plugin would look like this: package Hydra::Plugin::TwitterNotification; sub buildFinished { my ($self, $db, $config, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # send tweet... } 1;
2013-05-08 15:30:30 +00:00
package Hydra::Plugin;
Use OO-style plugins This is mostly so we don't have to pass around common parameters like "db" and "config", and we don't have to check for the existence of methods. A plugin now looks like this: package Hydra::Plugin::TwitterNotification; use parent 'Hydra::Plugin'; sub buildFinished { my ($self, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # Send tweet... # Hydra database is $self->{db}. }
2013-05-08 16:34:18 +00:00
use strict;
Add a plugin mechanism You can now add plugins to Hydra by writing a module called Hydra::Plugin::<whatever> and putting it in Perl's search path. The only plugin operation currently supported in buildFinished, called when hydra-build has finished doing a build. For instance, a Twitter notification plugin would look like this: package Hydra::Plugin::TwitterNotification; sub buildFinished { my ($self, $db, $config, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # send tweet... } 1;
2013-05-08 15:30:30 +00:00
use Module::Pluggable
search_path => "Hydra::Plugin",
Use OO-style plugins This is mostly so we don't have to pass around common parameters like "db" and "config", and we don't have to check for the existence of methods. A plugin now looks like this: package Hydra::Plugin::TwitterNotification; use parent 'Hydra::Plugin'; sub buildFinished { my ($self, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # Send tweet... # Hydra database is $self->{db}. }
2013-05-08 16:34:18 +00:00
instantiate => 'new';
sub new {
my ($class, %args) = @_;
my $self = { db => $args{db}, config => $args{config} };
bless $self, $class;
return $self;
}
Add a plugin mechanism You can now add plugins to Hydra by writing a module called Hydra::Plugin::<whatever> and putting it in Perl's search path. The only plugin operation currently supported in buildFinished, called when hydra-build has finished doing a build. For instance, a Twitter notification plugin would look like this: package Hydra::Plugin::TwitterNotification; sub buildFinished { my ($self, $db, $config, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # send tweet... } 1;
2013-05-08 15:30:30 +00:00
# Called when build $build has finished. If the build failed, then
# $dependents is an array ref to a list of builds that have also
# failed as a result (i.e. because they depend on $build or a failed
# dependeny of $build).
Use OO-style plugins This is mostly so we don't have to pass around common parameters like "db" and "config", and we don't have to check for the existence of methods. A plugin now looks like this: package Hydra::Plugin::TwitterNotification; use parent 'Hydra::Plugin'; sub buildFinished { my ($self, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # Send tweet... # Hydra database is $self->{db}. }
2013-05-08 16:34:18 +00:00
sub buildFinished {
my ($self, $build, $dependents) = @_;
}
Add a plugin mechanism You can now add plugins to Hydra by writing a module called Hydra::Plugin::<whatever> and putting it in Perl's search path. The only plugin operation currently supported in buildFinished, called when hydra-build has finished doing a build. For instance, a Twitter notification plugin would look like this: package Hydra::Plugin::TwitterNotification; sub buildFinished { my ($self, $db, $config, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # send tweet... } 1;
2013-05-08 15:30:30 +00:00
Support revision control systems via plugins
2013-05-25 19:36:58 +00:00
# Called to determine the set of supported input types. The plugin
# should add these to the $inputTypes hashref, e.g. $inputTypes{'svn'}
# = 'Subversion checkout'.
sub supportedInputTypes {
my ($self, $inputTypes) = @_;
}
# Called to fetch an input of type ‘$type’. ‘$value’ is the input
# location, typically the repository URL.
sub fetchInput {
my ($self, $type, $name, $value) = @_;
return undef;
}
Add a plugin mechanism You can now add plugins to Hydra by writing a module called Hydra::Plugin::<whatever> and putting it in Perl's search path. The only plugin operation currently supported in buildFinished, called when hydra-build has finished doing a build. For instance, a Twitter notification plugin would look like this: package Hydra::Plugin::TwitterNotification; sub buildFinished { my ($self, $db, $config, $build, $dependents) = @_; print STDERR "tweeting about build ", $build->id, "\n"; # send tweet... } 1;
2013-05-08 15:30:30 +00:00
1;
Copy permalink