dotnetcore / flubucore Goto Github PK

GetToken is now working.

For security reasons there should be implemented email notifications for each action executed.

Implement FlubuCore web api for executing scripts through api

http://stackoverflow.com/questions/43371142/scaffold-asp-net-core-with-full-framework-and-unit-test-projects

Method for calling web api Scripts/Execute

Option to add custom code before and after task exection.

Will be added if there is enough upvotes.

Could not load file or assembly 'System.Reflection.TypeExtensions, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
dotnet/standard#282

If project version is increased flubu should be published to nuget after system tests are completed.

Might work with:
https://wiki.jenkins.io/display/JENKINS/Parameterized+Trigger+Plugin

At the moment only one target is executed if more targets have DefaultTarget label.

There seems to be permission issue with deleting repository files on jenkins

Zip file in windows explorer and then unzip it with Unzip task.

• Standard Sc commands
• sc specific tasks by command.

Issue is just for reminder to investigate

Needs to be ported from Flubu. .Net standard 2.0 is required because Enviroment.SpecialFolder is not supported in .net standard 1.6

Change would be ITaskOf to ITaskOf<TResult, TTask>

Then we could change for example(and other methods):

ITaskOfT NoLog(); to TTask NoLog();

This would improve fluent interface but tasks would be a little bit more complicated.

If u use any method from ItaskOf at the moment u can't use anymore task specific fluent interface

@zoroz is it worth it?

Sugestions:

• Detailed script execution reports should be implemented
• Detailed test reports should be implemented.

Add token based authentication to web api. Should also be configurable so authentication can be disabled through config.

Some methods on TaskBase are poorly covered with unit tests.

CommonAssemblyInfo.cs should start with the <auto-generated/> header and not with the using directives. Otherwise analysers will still analyse the file. AFAIK analysers only check for the <auto-generated /> tag in the leading trivia of the first token.

Currently, StyleCopAnalyzers report SA1512 A single-line comment within C# code is followed by a blank line for the generated CommonAssemblyInfo.cs file.

https://docs.microsoft.com/en-us/dotnet/core/tools/custom-templates

on different members

context.CreateTarget("Deploy.Local")
.SetDescription("Deployes web api locally.")

Deploy.Local :

On nuget package update, flubu.runner script should check if BuildScript.cs already exists on target folder and should not try to overwrite it.