go-vela / community Goto Github PK
View Code? Open in Web Editor NEWCommunity Information for Vela (Target's official Pipeline Automation Framework)
Home Page: https://go-vela.github.io/docs/
License: Apache License 2.0
Community Information for Vela (Target's official Pipeline Automation Framework)
Home Page: https://go-vela.github.io/docs/
License: Apache License 2.0
Original story: go-vela/vela-tutorials#3
Add Groovy section for plugin tutorials
Decrease barrier to entry for creating plugins
Show Groovy developers how to create a plugin
A groovy plugin tutorial section exists
2 days
users who prefer Groovy
Original story: go-vela/docs#131
mikebeckel commented 23 days ago
Please don't place EXE's in C:\Windows\System32. It's a OS folder and while it makes it easy to make your executable accessible as it's included in the System Path it's not the correct approach for several reasons.
- It obfuscates the origin of your executable and can be interpreted as malware.
- It requires that users have Administrative rights to modify
The best approach is to create an installer so that it can be installed to Program Files. The next best approach is for the user to place in into a directory of their choosing, such as their user profile, and update the User Path so that it's accessible from anywhere for that user.
A better location for installing the Windows executable is provided in the documentation
1 day
users
Original story: go-vela/vela-kubernetes#34
Improve test coverage to > 90% for go-vela/vela-kubernetes
NOTE: This includes nested packages!
The plugin and all nested pkgs have > 90% test coverage
2 days
users of vela-kubernetes
Original story: https://github.com/go-vela/sdk-node/issues/1
Build a Software Development Kit (SDK) for the Node.js language.
The SDK is implemented and usable inside a Node.js application.
1 week
users who prefer Node.js
Original story: go-vela/cli#52
Implement hooks management via the Vela CLI
Offer the same functionality presented in the UI at /org/repo/hooks
but via the CLI.
eg.
vela get hooks --org octocat --repo hello-world
vela view hook --org octocat --repo hello-world --hook-number 10
A user can view hooks through the CLI
2 days
users
Original story: go-vela/ui#141
Log output that contains ANSI control sequence to colorize text is unhandled resulting in them being rendered as-is. Let's convert them and treat affected output respectively.
Cleaner log output
Control characters/escape sequences are converted to respective color. In addition, colors are accessible for currently supported themes.
2 days
Log output viewers
Original story: go-vela/cli#71
After upgrading to urfave/cli v2, we should investigate auto-completion again to make the CLI easier to use.
auto-completion docs in v2 library:
https://github.com/urfave/cli/blob/master/docs/v2/manual.md#bash-completion
improves usability
We have options for deciding if we want to move forward with auto-completion.
2 days
users
Original story: go-vela/vela-tutorials#4
Add Kotlin section for plugin tutorials
Decrease barrier to entry for creating plugins
Show Kotlin developers how to create a plugin
A kotlin plugin tutorial section exists
2 days
users who prefer Kotlin
Original story: go-vela/.github#3
Many testing tools and frameworks like Cypress, JUnit, Spock, etc...can generates screenshots or small video clips that capture the steps leading to the runtime error. How can developers access that info on CI Server?
It helped pin point the root cause of failure during integration or end-2-end testing. Having the exact reproducible steps with visual assistance allows developers troubleshoot and fix the bug faster.
Users can navigate, view or download the artifacts for each build.
N/A
users
Original story: go-vela/vela-docker#40
Add the ability to use the registry-mirror
flag in kaniko
Flag documentation:
https://github.com/GoogleContainerTools/kaniko#--registry-mirror
Allow users to pull from a different registry mirrors
The registry-mirror
flag is useable in the plugin.
2 days
users of vela-docker
Original story: go-vela/ui#94
Add ability to see services used in pipeline, including their log output.
Enhance the experience of visually tying the user's pipeline to what the user has defined it to be.
User is able to see what services were created in their pipeline and is able to view their respective logs.
1 week
users
Original story: go-vela/server#95
If a repo is deleted from git, it will still appear in Vela and cannot be removed. Please allow repositories that have been deleted from git to be removed from vela.
The current workaround is to recreate the repo, remove from vela, and re-delete. These added steps cost time.
If a git repo no longer exists, a user will still be able to remove them
1 day
users
Original story: go-vela/server#88
Provide a consumable stream of events generated from build activity.
Enable third party services and integrations
A stream of events in relation to build activity can be consumed.
2 weeks
users
Original story: go-vela/types#70
Current ruleset matching utilizes a file match pattern utility. This does not allow for more stringent matching, particularly with version tags. Use regex pattern matching since it allows for greater control and it commonly known.
Allows more control over step ruleset matchers
Current ruleset must have one or more exclude clause to eliminate greedy matches for tags with trailing data. e.g. -SNAPSHOT, -rc, -prod, etc.
ruleset:
if:
event: [ tag ]
tag: [ "[0-9].*" ]
unless:
event: [ tag ]
tag: [ "[0-9].*-prod" ]
After enhancement regex can be used to explicitly identify start/end of match
if:
branch: master
event: tag
tag: [ "^refs/tags/(\\d+\\.)+\\d+$" ]
4 days
users
Enable the ability to execute a Vela pipeline on a local workstation
A Vela pipeline can be ran on a local workstation
2 weeks
everyone
Original story: go-vela/vela-git#32
Improve test coverage to > 90% for go-vela/vela-git
NOTE: This includes nested packages!
The plugin and all nested pkgs have > 90% test coverage
2 days
users
Original story: go-vela/vela-downstream#14
Improve test coverage to > 90% for go-vela/vela-downstream
NOTE: This includes nested packages!
The plugin and all nested pkgs have > 90% test coverage
2 days
users of vela-downstream
Original story: go-vela/server#110
Respond to Label events to trigger builds
Support more diverse workflows
A user can successfully trigger a build via a label on GitHub.
1 week
users
Original story: go-vela/types#67
Create a JSON schema to allow code editors to parse the .vela.yml
and help users understand if the format is valid or not.
The simple steps to test the JSON schema:
.vela.yml
from yaml to json.vela.yml
Users able to configure code editor to utilize published JSON schema for file validation
2 days
All users modifying .vela.yml
within any code editor
Original story: go-vela/docs#105
Add information on how to paginate through multi-page results with the CLI
To let users know that there's a way to get to further results
Information about the pagination parameters is added to the docs
1 day
users
Original story: go-vela/vela-artifactory#38
Improve test coverage to > 90% for go-vela/vela-artifactory
NOTE: This includes nested packages!
The plugin and all nested pkgs have > 90% test coverage
2 days
users of vela-artifactory
Currently the filter on the builds page doesn't account for comment
events.
Allow users to filter by all currently supported events.
User is able to filter builds by selecting "comment" in the filter control.
Original story: go-vela/docs#119
galacticgumshoe commented on Apr 7
I had noticed that older secrets were no longer appearing on my list when doing vela get secret --org data-engineering-fieldops --type org --repo '*'. After posting this to #vela on Slack, I came to learn about two flags which are not documented. These do allow me to view secrets beyond my initial page, so should be added to the documentation https://go-vela.github.io/docs/cli/secret/:
--page
--per-page
To let users know that there's a way to get to further results
Information about the pagination parameters is added to the docs
1 day
users
Original story: go-vela/vela-tutorials#5
Add Rust section for plugin tutorials
Decrease barrier to entry for creating plugins
Show Rust developers how to create a plugin
A rust plugin tutorial section exists
2 days
users who prefer Rust
Add some well-placed notes about the importance of making sure to use case-sensitive values (matching SCM conventions), eg. if the organization is MyOrg
, use the same case-sensitive version in your CLI commands.
Original story: go-vela/server#134
Note: This change will be taking place in multiple places/repos - other stories to follow.
Currently, JWT returned by the server lives indefinitely. The client is responsible for retiring it. This change will introduce expiration for the JWT to make it short-lived and introduce a long-lived refresh token.
Improved security
2 weeks
users
Original story: go-vela/server#111
Respond to PR Reactions to trigger builds
Support more diverse workflows
A user can successfully trigger a build via a PR reaction on GitHub.
1 week
users
Original story: go-vela/vela-artifactory#44
[Error] [Thread 2] Artifactory response: 409 Conflict
[Error] Failed uploading 1 artifacts.
this example output would still leave the step it was used on as a successful step
vela --version
?Original story: https://github.com/go-vela/sdk-rust/issues/1
Build a Software Development Kit (SDK) for the Rust language.
The SDK is implemented and usable inside a Rust application.
1 week
users who prefer Rust
Original story: go-vela/server#77
I purpose that vela should support more secret engines besides key/value, like gcp, aws, and azure. This change could easily allow administrators to provide a set of credentials to be utilized by tools like terraform without needing to provide long lived credentials.
Some specific design considerations to think of:
My initial thought on changes to the pipeline to accomplish this looks like:
version: "1"
steps:
- name: test
image: alpine
secrets: [ aws ]
commands:
- env | grep AWS_
secrets:
- name: aws
key: aws/sts/foo
engine: vault
ttl: 60m
With the step of test
returning the output of:
AWS_LEASE_ID=<value>
AWS_LEASE_DURATION=<value>
AWS_LEASE_RENEWABLE=<value>
AWS_ACCESS_KEY=<value>
AWS_SECRET_KEY=<value>
AWS_SECURITY_TOKEN=<value>
The above example showcases that vela will retrieve the credentials through the aws secrets engine and convert all of the returned values to be in the format of <secret name in vela.yml>_<key returned in vault>
=<key value>
.
My proposed workflow to accomplish the above looks like:
vault secrets enable aws
and vault write aws/config/root access_key=<access key> secret_key=<secret key> region=<region>
vault write aws/roles/<role name> credential_type=<credential type> ...
vela map secret <name of secret within vault> --name <name of secret within vela> --org <org> --repo <repo> ...
Looking for feedback on this before I attempt to write the code to accomplish it.
1 week
Vault users
Original story: go-vela/docs#103
Add content for https://go-vela.github.io/docs/install/
To let users know how they can install and setup Vela
Information about installing and setting up Vela is added to the docs
2 days
users
filter changes url to <baseurl>/<org>/<repo>?event=deploy
instead of <baseurl>/<org>/<repo>?event=deployment
. also adjust filter name from deploy
to deployment
.
users are able to filter deployment
events appropriately
vela --version
?Original story: https://github.com/go-vela/sdk-ruby/issues/1
Build a Software Development Kit (SDK) for the Ruby language.
The SDK is implemented and usable inside a Ruby application.
1 week
users who prefer Ruby
Original story: go-vela/server#123
Enable the ability to limit the concurrent running vela pipelines for a given repository and/or given branches within the repository.
Some extra thoughts needed for considerations:
This is primarily helpful for repositories that are implementing deployments, and having multiple run at the same time can cause unintended behavior.
Users are able to define the concurrency of running vela pipelines within the API.
1 week
users
Original story: go-vela/server#86
Provide a mechanism for users to manage (cancel/kill) a running build
Terminate a long running (potentially rogue?) process
Prevent a misconfigured build from harming the system(s) it interacts with
A user can send an API call to the server that will handle the communication with the worker to manage the build.
2 weeks
users
Original story: go-vela/ui#95
Add ability to see stages used in pipeline, including their log output.
Enhance the experience of visually tying the user's pipeline to what the user has defined it to be.
User is able to see what stages were created in their pipeline and is able to view their respective logs.
1 week
users
Original story: https://github.com/go-vela/sdk-kotlin/issues/1
Build a Software Development Kit (SDK) for the Kotlin language.
The SDK is implemented and usable inside a Kotlin application.
1 week
users who prefer Kotlin
Original story: go-vela/server#127
In a pull request event, BUILD_BRANCH
is populated with the name of the base branch that the PR is targeting, but it would be nice to have access to the pull request branch name as well.
A user can successfully reference the original PR branch name in a pipeline.
1 day
users
Original story: go-vela/vela-tutorials#2
Add content for the templates section.
Decrease barrier to entry with templates
Increase clarity around intended use-cases for templates
Create a guide for other organizations to create their own templates
The tutorials
section of this repository contains content.
2 days
users who use templates
Original stories:
Update our gopkg.in/yaml library to the v3 functionality.
https://github.com/go-yaml/yaml/tree/v3
This repo is using the v3
release of the gopkg.in/yaml
library.
1 week
everyone
Original story: go-vela/vela-docker#30
Improve test coverage to > 90% for go-vela/vela-docker
NOTE: This includes nested packages!
The plugin and all nested pkgs have > 90% test coverage
2 days
users of vela-docker
Original story: go-vela/sdk-python#1
Build a Software Development Kit (SDK) for the Python language.
The SDK is implemented and usable inside a Python application.
1 week
users who prefer Python
Original story: go-vela/docs#135
wass3r commented 19 days ago
Consider enumerating the different methods to retrieve the token to use in API calls and add them to: https://go-vela.github.io/docs/api/authentication/
Make it clear where a user can retrieve their user token
Documentation has been added to explain where a user can find their token.
1 day
users
Original story: go-vela/cli#55
The worker api should be documented.
This will make interacting with the api easier, especially for server <-> worker communication
There is a spec for the workers in the worker repo.
Couple days
Original story: go-vela/types#65
Update the ruleset
to allow include and exclude logic for the path
element.
Both of the below proposed design changes to the .vela.yml
would have the same underlying results of:
cool-code/foo.js
will triggercool-code/docs/foo.md
will not triggerAdd ignore
and include
underneath path
to allow the following configuration:
ruleset:
path:
include:
- [ "cool-code/**" ]
exclude:
- [ "cool-code/docs/**"]
This could lead to breaking behavior due to the current structure of the yaml so extra consideration is needed.
Utilize some ignore character(s) to allow updating the existing path
to handle both scenarios. The following example utilizes the ignore character of !
:
ruleset:
path: [ "!cool-code/docs/**", "cool-code/** ]
Greatly simplifies scenarios where you want to exclude a specific file(s) or folder(s), and not need to call out includes for everything else.
ruleset
for path
updated to allow include and exclude logic
1 day
All users utilizing the path
element of ruleset
Original story: go-vela/cli#53
Implement repo favorites management via the Vela CLI
Offer the same functionality presented in the UI at /
(home page) but via the CLI.
eg.
vela get favorites or update functionality for vela get repos
vela add favorite --org octocat --repo hello-world
A user can manage favorites through the CLI
2 days
users
Original issue: go-vela/vela-docker#35
Currently, auto_tag
, when applied during a tag event, will simply tag the container with BUILD_TAG
, but it would be nice if it would create a series of tags based on the tag provided, if it is recognized as a semantic version number.
Example: If BUILD_TAG
is v2.1.24
, the following tags would be created (the "v", if present, will be stripped):
2.1.24
2.1
2
latest
This will allow container users to "subscribe" to a particular version scope, depending on their comfort level, and receive updates without knowing exact patch numbers, for example.
The auto_tag
parameter should cause tagging to behave as described above.
1 day
users of vela-docker
Original story: go-vela/vela-s3-cache#11
for applications using npm or yarn that want to cache their dependencies (ie. node_modules
folder), the restored cache resolves symlinks incorrectly.
example restored cache items:
$ ls -la node_modules/.bin
total 16
drwxr-xr-x 2 root root 4096 Apr 14 19:33 .
drwxr-xr-x 313 root root 12288 Apr 14 19:33 ..
lrwxrwxrwx 1 root root 23 Apr 14 19:33 acorn -> node_modules/.bin/acorn
lrwxrwxrwx 1 root root 22 Apr 14 19:33 atob -> node_modules/.bin/atob
lrwxrwxrwx 1 root root 23 Apr 14 19:33 errno -> node_modules/.bin/errno
lrwxrwxrwx 1 root root 38 Apr 14 19:33 import-local-fixture -> node_modules/.bin/import-local-fixture
lrwxrwxrwx 1 root root 23 Apr 14 19:33 json5 -> node_modules/.bin/json5
lrwxrwxrwx 1 root root 30 Apr 14 19:33 miller-rabin -> node_modules/.bin/miller-rabin
lrwxrwxrwx 1 root root 24 Apr 14 19:33 mkdirp -> node_modules/.bin/mkdirp
lrwxrwxrwx 1 root root 24 Apr 14 19:33 rimraf -> node_modules/.bin/rimraf
lrwxrwxrwx 1 root root 24 Apr 14 19:33 semver -> node_modules/.bin/semver
lrwxrwxrwx 1 root root 24 Apr 14 19:33 sha.js -> node_modules/.bin/sha.js
lrwxrwxrwx 1 root root 24 Apr 14 19:33 terser -> node_modules/.bin/terser
lrwxrwxrwx 1 root root 25 Apr 14 19:33 webpack -> node_modules/.bin/webpack
lrwxrwxrwx 1 root root 29 Apr 14 19:33 webpack-cli -> node_modules/.bin/webpack-cli
lrwxrwxrwx 1 root root 23 Apr 14 19:33 which -> node_modules/.bin/which
expected output should be:
$ ls -la node_modules/.bin
total 16
drwxr-xr-x 2 root root 4096 Apr 14 19:34 .
drwxr-xr-x 313 root root 12288 Apr 14 19:34 ..
lrwxrwxrwx 1 root root 18 Apr 14 19:34 acorn -> ../acorn/bin/acorn
lrwxrwxrwx 1 root root 19 Apr 14 19:34 atob -> ../atob/bin/atob.js
lrwxrwxrwx 1 root root 15 Apr 14 19:34 errno -> ../errno/cli.js
lrwxrwxrwx 1 root root 31 Apr 14 19:34 import-local-fixture -> ../import-local/fixtures/cli.js
lrwxrwxrwx 1 root root 19 Apr 14 19:34 json5 -> ../json5/lib/cli.js
lrwxrwxrwx 1 root root 32 Apr 14 19:34 miller-rabin -> ../miller-rabin/bin/miller-rabin
lrwxrwxrwx 1 root root 20 Apr 14 19:34 mkdirp -> ../mkdirp/bin/cmd.js
lrwxrwxrwx 1 root root 16 Apr 14 19:34 rimraf -> ../rimraf/bin.js
lrwxrwxrwx 1 root root 20 Apr 14 19:34 semver -> ../semver/bin/semver
lrwxrwxrwx 1 root root 16 Apr 14 19:34 sha.js -> ../sha.js/bin.js
lrwxrwxrwx 1 root root 20 Apr 14 19:34 terser -> ../terser/bin/terser
lrwxrwxrwx 1 root root 25 Apr 14 19:34 webpack -> ../webpack/bin/webpack.js
lrwxrwxrwx 1 root root 25 Apr 14 19:34 webpack-cli -> ../webpack-cli/bin/cli.js
lrwxrwxrwx 1 root root 18 Apr 14 19:34 which -> ../which/bin/which
potentially related to this: mholt/archiver#202
vela --version
?Original story: go-vela/server#112
Respond to more PR comment events to trigger builds
Support more diverse workflows
A user can successfully trigger a build via a PR comment on GitHub.
1 week
users
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.