helix-publishing-pipeline | Unified publishing for Sitecore Helix solutions

by richardszalay PowerShell Version: v1.5.6 License: MIT

X-Ray Key Features Code Snippets(3)Community Discussions Vulnerabilities Install Support

kandi X-RAY | helix-publishing-pipeline Summary

helix-publishing-pipeline is a PowerShell library. helix-publishing-pipeline has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Helix Publishing Pipeline (HPP) allows Helix solutions to be published as a single unit, with content from modules (like views and config patches) being automatically included. It also contains optimisations and guidance around local development deployments. Because the project extends the standard Web Publishing Pipeline it should work with any supported target (package, file system, Azure, Docker) via either Visual Studio or the command line.

Support

Quality

Security

License

Reuse

Support

helix-publishing-pipeline has a low active ecosystem.

It has 56 star(s) with 13 fork(s). There are 15 watchers for this library.

It had no major release in the last 12 months.

There are 17 open issues and 29 have been closed. On average issues are closed in 25 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of helix-publishing-pipeline is v1.5.6

Quality

helix-publishing-pipeline has 0 bugs and 0 code smells.

Security

helix-publishing-pipeline has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

helix-publishing-pipeline code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

helix-publishing-pipeline is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

helix-publishing-pipeline releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 2255 lines of code, 0 functions and 42 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of helix-publishing-pipeline

Get all kandi verified functions for this library.

helix-publishing-pipeline Key Features

No Key Features are available at this moment for helix-publishing-pipeline.

helix-publishing-pipeline Examples and Code Snippets

Helix Publishing Pipeline,Extensibility,Including additional content

PowerShell

Lines of Code : 27

License : Permissive (MIT)

Copy



  
    ..\serialization\**\*.yml
    App_Data\unicorn\^(HelixModule.Filename)\^(RecursiveDir)^(Filename)^(Extension)
  



  
    
    Foundation
  



  
  
    
    ^(?'Namespace'.+)\.(?'Layer'.+?)\.(?'Module'.+)$

Helix Publishing Pipeline,Installation,Publishing on build

PowerShell

Lines of Code : 17

License : Permissive (MIT)

Copy


  true
  Local




  true

  
    $(AutoPublishDependsOn);
    WebPublish

Helix Publishing Pipeline,Installation,Excluding Sitecore assemblies

PowerShell

Lines of Code : 16

License : Permissive (MIT)

Copy

Community Discussions

No Community Discussions are available at this moment for helix-publishing-pipeline.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install helix-publishing-pipeline

Before you begin, choose a project that will act as the web root (i.e., owns the Web.config) for publishing. For solutions with multiple "Project" modules, it's best to explicitly create a "Website" project.
Install the RichardSzalay.Helix.Publishing.WebRoot NuGet package in the web root project.
Add a project reference to all Project, Feature, and Foundation module projects, or apply auto-discovery as described below.
To trigger a publish after each build, add the following to your web root .csproj (anywhere before the Web.Publishing.targets import):. The example above triggers the Local publish profile when building as Debug within Visual Studio. It has been designed to minimise impact on build timings. This behavior is currently described via opt-in guidance, but may be configured automatically in a future release. NOTE: When publishing to FileSystem, Helix Publishing Pipeline detects unchanged Web.config transformation outputs and skips them to prevent an unnecessary app pool recycle.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: