Drone is a Container-Native, Continuous Delivery Platform
Go to file
Dhruv e92962b06d
fix: [CDE-540]: Adding a check for user name and email during code clone operation. (#3596)
### Description

This PR introduces two changes
1. Adding a check for user's name and email before cloning the code
inside the gitspace container. This will non-block non-harness repos.
2. Adding an explicit check for the media folder's path during VSCode
web setup.

---------
2024-12-05 13:50:34 +05:30
.githooks [MISC] Fix Linting/Formatting/Generated Files (#697) 2023-10-19 00:36:07 +00:00
.github/workflows pull request import (#2121) 2024-07-06 00:46:36 +00:00
.vscode feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
app fix: [CDE-540]: Adding a check for user name and email during code clone operation. (#3596) 2024-12-05 13:50:34 +05:30
audit feat: [AH-309]: Artifact Registry integration (#2318) 2024-08-22 00:28:17 +00:00
blob feat: Update token source impersonation and add expiration check (#815) 2023-11-27 14:41:39 +00:00
cache feat: [CODE-2232]: Branch Rules: UserGroup support: Create and List (#2640) 2024-09-11 08:04:31 +00:00
charts/gitness feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
cli feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
client remove internal package and move to app - might be refactored more in the coming weeks 2023-09-26 11:25:15 -07:00
cmd/gitness feat: [AH-231]: Upstream features (#3560) 2024-09-25 01:16:26 -07:00
contextutil [CODE-1287] Improve PR Merge for canceled Request (#963) 2024-01-12 20:25:16 +00:00
encrypt [OPEN-SOURCE] Prepare Repository (#605) 2023-09-24 07:33:16 +00:00
errors Fix merge related issues (#2012) 2024-04-25 22:00:53 +00:00
events fix lint errors (#1034) 2024-02-09 01:15:15 +00:00
genai feat: [ML-302]: Framework For Harness Intelligence APIs (#2547) 2024-08-20 22:05:29 +00:00
git feat: [CODE-2335]: add dryrun option for rebase API (#2721) 2024-09-23 14:46:17 +00:00
http feat: [CODE-2212]: Improve SSH Configuration (#2446) 2024-08-09 16:21:41 +00:00
infraprovider feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
job [MISC] fix repo delete for older repos that failed import (#972) 2024-01-17 19:10:10 +00:00
livelog fix: [CDE-150]: In logstream, adding locking and panic recovery around a subscriber's publish method. Adding check in the stream's publish method to not publish if the sub is closed. Closing the err channel in the log stream API handler. (#2218) 2024-07-15 08:10:59 +00:00
lock fix lint errors (#1034) 2024-02-09 01:15:15 +00:00
logging [CODE-1287] Improve PR Merge for canceled Request (#963) 2024-01-12 20:25:16 +00:00
profiler [MISC] Fix Linting/Formatting/Generated Files (#697) 2023-10-19 00:36:07 +00:00
pubsub [Pubsub] handle closed redis channel (#800) 2023-11-15 00:04:34 +00:00
registry feat: [AH-231]: Upstream features (#3560) 2024-09-25 01:16:26 -07:00
resources [OPEN-SOURCE] Prepare Repository (#605) 2023-09-24 07:33:16 +00:00
scripts [MISC] Fix Linting/Formatting/Generated Files (#697) 2023-10-19 00:36:07 +00:00
secret [AH-310]: temp push; need to check (#2607) 2024-08-29 19:42:22 +00:00
ssh [SSH] Minor Server Changes (#2088) 2024-06-10 20:09:35 +00:00
store feat: [AH-309]: Artifact Registry integration (#2318) 2024-08-22 00:28:17 +00:00
stream add logging for redis history sanning (#2417) 2024-08-07 00:15:34 +00:00
types feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
version prepare open-source 2023-09-25 19:07:35 -07:00
web feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
.dockerignore [SSH] Minor Server Changes (#2088) 2024-06-10 20:09:35 +00:00
.gitignore [fix]: [AH-283]: Fixed distribution-spec build issue (#2725) 2024-09-24 04:09:46 +00:00
.golangci.yml feat: [AH-309]: Artifact Registry integration (#2318) 2024-08-22 00:28:17 +00:00
.local.env feat: [AH-307]: GC interface Integration, event framework; schema changes; UI changes (#2688) 2024-09-24 12:47:53 +00:00
CONTRIBUTING.md feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
Dockerfile feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
LICENSE prepare open-source 2023-09-25 19:07:35 -07:00
Makefile feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
NOTICE feat: [AH-309]: Artifact Registry integration (#2318) 2024-08-22 00:28:17 +00:00
README.md feat: [CODE-2402] : Update all occurences of 'gitness' to 'harness' within comments and markdown. Updated the logo reference (did not delete the Gitness logo directory yet). No active code changes except display strings. (#2684) 2024-09-25 00:13:28 +00:00
go.mod feat: [CODE-2352]: update gitleaks with latest master (#2682) 2024-09-12 20:57:01 +00:00
go.sum feat: [CODE-2352]: update gitleaks with latest master (#2682) 2024-09-12 20:57:01 +00:00

README.md

Harness

Harness is an open source development platform packed with the power of code hosting, automated DevOps pipelines, Gitspaces, and artifact registries.

Overview

Harness is an open source development platform packed with the power of code hosting, automated DevOps pipelines, Gitspaces, and artifact registries.

Running Harness locally

The latest publicly released docker image can be found on harness/harness.

To install Harness yourself, simply run the command below. Once the container is up, you can visit http://localhost:3000 in your browser.

docker run -d \
  -p 3000:3000 \
  -p 22:22 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /tmp/harness:/data \
  --name harness \
  --restart always \
  harness/harness

The Harness image uses a volume to store the database and repositories. It is highly recommended to use a bind mount or named volume as otherwise all data will be lost once the container is stopped.

// TODO: @Dewan - let me know the correct doc URL See developer.harness.com to learn how to get the most out of Harness.

Where is Drone?

Harness Open Source represents a massive investment in the next generation of Drone. Where Drone focused solely on continuous integration, Harness adds source code hosting, developer environments (gitspaces), and artifact regestries; providing teams with an end-to-end, open source DevOps platform.

The goal is for Harness to eventually be at full parity with Drone in terms of pipeline capabilities, allowing users to seemlessly migrate from Drone to Harness.

But, we expect this to take some time, which is why we took a snapshot of Drone as a feature branch drone (README) so it can continue development.

As for Harness, the development is taking place on the main branch.

For more information on Harness, please visit developer.harness.com.

For more information on Drone, please visit drone.io.

Harness Open Source Development

Pre-Requisites

Install the latest stable version of Node and Go version 1.20 or higher, and then install the below Go programs. Ensure the GOPATH bin directory is added to your PATH.

Install protobuf

  • Check if you've already installed protobuf protoc --version
  • If your version is different than v3.21.11, run brew unlink protobuf
  • Get v3.21.11 curl -s https://raw.githubusercontent.com/Homebrew/homebrew-core/9de8de7a533609ebfded833480c1f7c05a3448cb/Formula/protobuf.rb > /tmp/protobuf.rb
  • Install it brew install /tmp/protobuf.rb
  • Check out your version protoc --version

Install protoc-gen-go and protoc-gen-go-rpc:

  • Install protoc-gen-go v1.28.1 go install google.golang.org/protobuf/cmd/protoc-gen-go@v1.28.1 (Note that this will install a binary in $GOBIN so make sure $GOBIN is in your $PATH)

  • Install protoc-gen-go-grpc v1.2.0 go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.2.0

$ make dep
$ make tools

Build

First step is to build the user interface artifacts:

$ pushd web
$ yarn install
$ yarn build
$ popd

After that, you can build the Harness binary:

$ make build

Run

This project supports all operating systems and architectures supported by Go. This means you can build and run the system on your machine; docker containers are not required for local development and testing.

To start the server at localhost:3000, simply run the following command:

./gitness server .local.env

Auto-Generate Harness API Client used by UI using Swagger

Please make sure to update the autogenerated client code used by the UI when adding new rest APIs.

To regenerate the code, please execute the following steps:

  • Regenerate swagger with latest Harness binary ./gitness swagger > web/src/services/code/swagger.yaml
  • navigate to the web folder and run yarn services

The latest API changes should now be reflected in web/src/services/code/index.tsx

Run Registry Conformance Tests

make conformance-test

For running conformance tests with existing running service, use:

make hot-conformance-test

User Interface

This project includes a full user interface for interacting with the system. When you run the application, you can access the user interface by navigating to http://localhost:3000 in your browser.

REST API

This project includes a swagger specification. When you run the application, you can access the swagger specification by navigating to http://localhost:3000/swagger in your browser (for raw yaml see http://localhost:3000/openapi.yaml). For registry endpoints, currently swagger is located on different endpoint http://localhost:3000/registry/swagger/ (for raw json see http://localhost:3000/registry/swagger.json). These will be later moved to the main swagger endpoint.

For testing, it's simplest to just use the cli to create a token (this requires Harness server to run):

# LOGIN (user: admin, pw: changeit)
$ ./gitness login

# GENERATE PAT (1 YEAR VALIDITY)
$ ./gitness user pat "my-pat-uid" 2592000

The command outputs a valid PAT that has been granted full access as the user. The token can then be send as part of the Authorization header with Postman or curl:

$ curl http://localhost:3000/api/v1/user \
-H "Authorization: Bearer $TOKEN"

CLI

This project includes VERY basic command line tools for development and running the service. Please remember that you must start the server before you can execute commands.

For a full list of supported operations, please see

$ ./gitness --help

Contributing

Refer to CONTRIBUTING.md

License

Apache License 2.0, see LICENSE.