photon-ci / photon Goto Github PK

Implement a feature in the Photon.Server application to allow pushing the current security configuration to all attached agents. This allows users to define security configurations one time, and not have to apply settings to each agent individually.

A command-line interface application is required for executing tasks.

• Build (project, ref, script)
• Deploy (project, version, script)
• Package
  • Pack (in?, out, version)
  • Unpack (file, out)

Add features for managing the archive of build and deployment artifacts. Items should be removed after a specified time-to-live.

Convert the Package ID text on the Build Summary page to hyperlinks that link directly to the package for downloading. If/when a package summary page is created, then the link can be directed there instead.

This project has no readme file describing its purpose or how to use it.

Add interface for viewing and managing installed Applications to the Agent web interface.

Add file monitoring to Agent and Server configuration files to allow settings to be modified at runtime without restarting the services.

A feature is required for grouping agents by environment, where environment refers to a collection of servers/agents that define an application. Ex: QA, Model, Production

Include LICENSE file. Type of license needs to be determined, currently GNU GPv3.

A web user interface needs to be designed and developed for the Photon.Agent application. The initial implementation should include:

• Dashboard
• Build History
• Deployment History

The Agent application uses PiServerLite for it's HTTP web interface.

This is not currently implemented. The goal is to support a syntax similar to NuGet's nuspec files:

• ** - Match any directory name.
• * - Match any range of filename characters.

Ex:
The filter bin\Debug\**\*.dll should match all *.dll files in any directory under bin\Debug

Integrate Photon with GitHub status updates. This includes a webhook for triggering a project-defined hookTask (BuildTask). The application should send commit status updates to GitHub notifying that the task is 'In Progress', 'Successful', 'Failed', or 'Cancelled'.

A package system needs to be implemented for creating, storing, and unpacking Project and Application packages.

A wiki needs to be created before the initial release.

Add option to IDomainContext.RunCommand() method to disable the printing of the command that is being executed.

• Avoids output clutter.
• Prevent secure information from being logged.
• Reduces duplication of information.

Several extra builds are occurring because the type of push event is not being considered. The request payload must be inspected for the deleted (bool) property.

Replace current Application Domain functionality with a separate worker application. This will require migrating current remoting communication between Agent and user-process to use Photon.Communication library. This will also allow the future migration to .NET core, which does not support separate Application Domains.

Add features to verify JSON data after submitting. This may include:

• Verifying relational object ID's.
• Verify agent connectivity.
• Ping endpoints to verify accessibility.
• ...

A web user interface needs to be designed and developed for the Photon.Server application. The initial implementation should include:

• Dashboard
• Build History
• Deployment History
• View/Download Build/Deploy Artifacts

The Server application uses PiServerLite for it's HTTP web interface.

Add features to Agent index page to show the connection/busy status of agents. Currently, only a static green checkbox is shown.

Add features for managing the archive of applications. Items should be removed after a specified time-to-live.

The TCP messaging system requires support for file/binary transfers, so that packages can be deployed to agents and artifacts can be collected by the server. This will also require a 'packet distribution' mechanism to prevent file transfers from blocking short messages.

The exclusion filters for creating packages have not been implemented, at all. This should be fixed before the initial release.

Add an option for using Git from the command-line rather than the integrated NuGet.Core assembly. This should allow git commands to be used on ARM and Linux x32 platforms, or any platform not supported directly by libgit2.

Creating a new project is resetting the 'load-complete' lock and causing no builds to be shown until restart. Requires investigation.

libgit2/libgit2sharp#1572

To allow the Photon Agent application to use the native LibGit2 libraries on the Raspberry PI, LibGit2Sharp needs a compiled 32 bit Linux ARM binary. Currently there is only a 64-bit version of the linux library available.

Add support for collecting user defined artifacts from the server and agent deploy workspace, and copying them to the server for archival.

Add a collection of scripts to the repository for public use as Pre-Build Command templates.

The server application should include a feature for performing an automated update of any and all defined agents.

Add utility classes to framework library for working with XML transformations, using the same XDT specification that Visual Studio uses.

Add support for collecting user defined artifacts from the agent build workspace, and copying them to the server for archival.