Better separation of network, logging and pipeline

I have reverted some last changes to get logging and network extraction
from context separated from the pipeline again as it has been before.
Feels much better to have it separated within the generated plugins.
This commit is contained in:
Thomas Boerger 2020-01-20 22:58:54 +01:00
parent ffc6705536
commit c46cfdde19
No known key found for this signature in database
GPG Key ID: 09745AFF9D63C79B
4 changed files with 20 additions and 24 deletions

View File

@ -9,7 +9,6 @@ package drone
//
// Represents the full Drone environment that the plugin is executing in.
type Pipeline struct {
Network Network
Build Build
Repo Repo
Commit Commit

View File

@ -21,8 +21,8 @@ func loggingFlags() []cli.Flag {
}
}
// loggingFromContext sets the logrus logging level.
func loggingFromContext(ctx *cli.Context) {
// LoggingFromContext sets the logrus logging level.
func LoggingFromContext(ctx *cli.Context) {
lvl, err := logrus.ParseLevel(ctx.String("log-level"))
if err != nil {

View File

@ -29,8 +29,8 @@ func networkFlags() []cli.Flag {
}
}
// networkFromContext creates a drone.Network from the cli.Context.
func networkFromContext(c *cli.Context) drone.Network {
// NetworkFromContext creates a drone.Network from the cli.Context.
func NetworkFromContext(c *cli.Context) drone.Network {
dialer := &net.Dialer{
Timeout: 30 * time.Second,
KeepAlive: 30 * time.Second,

View File

@ -27,12 +27,9 @@ func Flags() []cli.Flag {
return flags
}
// FromContext creates a drone.Pipeline from the cli.Context.
func FromContext(ctx *cli.Context) drone.Pipeline {
loggingFromContext(ctx)
// PipelineFromContext creates a drone.Pipeline from the cli.Context.
func PipelineFromContext(ctx *cli.Context) drone.Pipeline {
return drone.Pipeline{
Network: networkFromContext(ctx),
Build: buildFromContext(ctx),
Repo: repoFromContext(ctx),
Commit: commitFromContext(ctx),