subpointsolutions / cakebuildtools Goto Github PK

Action-Restore-NuGet-Package never got called. Build fails while missing restored packages.
All default tasks need to be updated with correct flow including Action-Restore-NuGet-Package

ci.github.releaseversion variable or the first NuSpec version must never be null or empty.
Vsix projects should have an alternative way to get this variable auti-set

CakeBuildTools becomes more complex aiming to simplify many build operations. Dummy CSharp projects with basic build scenarios need to be added to cover "regression" testing as well as provide more documentation and getting started examples.

The following tasks are to be added to support docs/web site generation. All actions should work with multiple "web sites" so that not only documentation but also additional web sites can be generated with Action-StaticSite-XXX commands.

Action-StaticSite-Build

This action is meant to generate a static site. It hides an implementation (currently Wyam) providing a high level abstraction - source folder and output folder exposed via config. The rest of the things have to follow a name convention.

Current implementation should incorporate the following actions:

• Run sample generation from DocsBuildTools
• Run Wyam site generation

Action-StaticSite-ZIP-Packaging

This action should create a zip archive packaging data from Action-StaticSite-Build "output" folder. Checksums and zip archive is to be created so that later it can be used with other static site generators, npm, docker, etc.

Current implementation should incorporate the following actions:

• Create a ZIP archive with checksums based on the Action-Docs-Build output folder

Action-StaticSite-Netlify-Publishing

This action should support static site publishing to Netlify.

Current implementation should incorporate the following actions:

• Publishes data from Action-Docs-Build output folder to Netlify.
• Follows dev/beta/master workflow to lookup correct creds for publishing similar to choco/nuget

Action-Git-Merge (ex-Action-Docs-Merge)

This is a support action to merge various docs repos into a centralized repo so that many projecs and docs can be compiled into a single web site.

Current implementation should incorporate the following actions:

• Merges data from Action-StaticSite-Build output folder into a predefined repo

defaultSolutionFilePath setting should be optional. But default, build should auto-detect *.sln file looking in the current folder and the moving up several levels until the solution is found.

Exactly like this:
https://github.com/enkafan/Cake.Figlet

There should be a task "Action-GitHub-ReleaseNotes" which would craft github release notes for every CI based build. The following flow is recommended:

• Get all closed tasks in open milestones up to the current date
• Categorize tasks as per suggested labels
• Put together Razor based templates and fetched tasks
• Update release notes in github, use the first NuSpec package number as the build number

CI action is to be enhanced later.

releaseVersion for GitHub release should be read from ENV variable, default nuspec if any, and then from JSON config.

CakeBuildTools should support automated packaging and deployment to Azure web sites. The scope is hard to define yet but the drivers are two tickets to support automated MetaPack Gallery packaging and deployment:

Enhance build process with automated CD
SubPointSolutions/MetaPackGallery#2

Migrate to the recent CakeBuildTools
SubPointSolutions/MetaPackGallery#1

CakeBuildTools should be adjusted to support these scenarios.

Normally, chocolatey packaging and publishing is enabled for dev builds. However, if no packages are found (non CLI projects), cake build should succeed.

Right now it fails while fetching creds for choco publishing.

JSON based configuration needs to be migrated to YAML. Main reason is that YAML is least verbose and allows to use comments.

Both JSON and YAML configs are still to be supported, hover YAML is to be the primary choice.

Implement Action-CLI-Chocolatey-Publishing to support Chocolatey push.

"Action-Build" should be able to build custom csharp profiles from the *.json config. The following example needs to be implemented:

 "customProjectBuildProfiles": [
        {
            "ProfileName": "SP2010 + NET35",
            "ProjectFiles": [
                "SPMeta2.Reverse/SPMeta2.Reverse.csproj",

                "SPMeta2.Reverse.CSOM/SPMeta2.Reverse.CSOM.csproj",
                "SPMeta2.Reverse.CSOM.Standard/SPMeta2.Reverse.CSOM.Standard.csproj"
            ],
            "BuildParameters": [
                "/p:spRuntime=14",
                "/p:Configuration=Debug35",
                "/p:DefineConstants=NET35",

                "/t:Build",
                "/p:Platform=AnyCPU",
                "/p:WarningLevel=0",
                "/verbosity:quiet",
                "/clp:ErrorsOnly",
                "/nologo"
            ]
        }
]

git push should not produce output working in pure silent mode.