Create project on internal Jenkins instance that would build extension package, upload it to internal server for verification and then ask confirmation before publishing. This way we would verify exactly the same bits we are about to publish to marketplace.

We also need a svg image for tekton icon in grayscale, so that it looks better in dark theme.

Add action to be able to start a pipeline and select the PipelineResources that already exist in the namespace. The flow should allow user to select resources from a dropdown list that is filtered based on the resource type that the pipeline requires.

Add actions in order to create PipelineResources. The flow should get input from the user regarding the type of pipeline resource to be created and the values required for each pipeline resource type

Check if Tekton APIs are available on the cluster and display a message that indicates that Tekton is not available.

Additionally we should also cover the case where tekton is installed but the current user does not have the privileges to interact with tekton resources.

Resource names should be capitalised to TastRun, PipelineRun, etc.

'Follow Log' command should be provided along with 'Show Logs'

TreeDataProvider fails with error User "Developer" cannot list resource "clustertasks".

/feature

The plugin should have an ability to create pipeline by choosing the list of tasks via the explorer.

Tasks belong to namespace/project. Tekton Pipelines Explorer does not show projects, so content for Tasks node should rely on current context. That means it should show tasks for current namespace printed out with tkn list task command without -n workspace_name option. To switch namespace Clusters View or cli tool should be used.

Reference to Containters instead of Containers

There is a race condition where a pipeline resource event is received before a pipeline event is received and therefore not yet created in the tree. This prevents the pipeline resource from being added to the tree.

Currently, it does only a tkn taskrun list, thus showing all the taskrun instead of the one related to the selected pipeline.

Add action to be able to start a pipeline and create new PipelineResources as part of the start flow which are then used for starting the pipeline.

The user should be able to start PipelineRuns for any Pipeline definition they have created

'Load' command should able to open yaml file in text editor.

Now context menu items for nodes in Tekton Pipelines Veiw have long redundant names. When context menu requested for Pipleline almost every item includes 'Pipelines' in its name:

• Describe Pipelines
• Start Pipeline
  Should be:
• Describe
• Start

This extension will cause tkn 0.3.0 to be downloaded; but tkn is now 0.5.0. We should update the tkn metadata

add support for snippets that allows to create tekton resource yamls quickly.

The Tekton Pipelines tree currently requires a manual refresh to display the latest state of the pipelines and pipelineruns. This would leave the user thinking the pipeilnerun is running for a long time.

User should be able to see the logs for a pipeline and task run.

When user selects Show pipeilnerun logs, the logs should stream and follow if the pipeline is still running. Currently it shows the available logs and exits.

Available from https://marketplace.visualstudio.com/items?itemName=redhat.vscode-tekton-pipelines

Thanks for making this!! :D ❤️

I tried to install it today but ran into trouble because though I do have tkn installed (built from source), the extension thought it was not installed (p.s. I really like the design, how the extension uses the cli, very cool!) b/c the version was "dev" and not v0.3.0

What I did was:

1. Installed the latest build (Nov 3?) (instructions from https://github.com/redhat-developer/vscode-tekton#warning-nightly-builds-are-by-definition-unstable-install-at-you-own-risk)
2. Tried to run > Tekton: About
3. Got the error: "Cannot find A CLI for interacting with Tekton v0.3.0."
4. Hit the "help" button
5. A terminal popped up, when I tried to run tkn it wasn't found, and also I didnt recognize the $PATH, it doesn't seem to be the one I usually see when I run /bin/bash or similar

I finally worked around this by installing version 0.3.0 of the CLI instead of the dev version - is it possible for there to be a mode that allows me to use the dev CLI and/or not care what version of the CLI is installed?

For example if at early stages it is good to have all nodes visible while developing pipeline. When pipeline is created and running on regular basis it might make sense to hide everything except Pipelines node.

Instead of using metadata.name which include pipeline name and suffix run and hash and task name, metadata.labels["tekton.dev/pipelineTask"] value should be used.
This will require to change the way nodes created and change of lable attribute get method.

Default user have no permission to push image, `-s pipeline' should be used to run pipeline command.

The color of a running pipelinerun and taskrun is very close to a failed one which makes is difficult to distinguish.

Those commands do not work for pipeline resource objects.

Every kind of node should have default template. There should be preference that allows to modify default template per node kind.

Would be good to have limit, because list can grow over time.

Would be good to have it documented for early access and provide:

1. Location to download the build
2. Animated gif with installation from .vsix file

This is upstream issue with 'hasha' module version > 5.0.0 or electron which fails in latest vscode release.

This is taking to much time when number of objects grows over time.

Show this gif on top of README.md the same way other extension do.
Animated gif should show repositories cloned and added to workspace:

1. https://github.com/openshift/pipelines-tutorial
2. https://github.com/openshift/pipelines-catalog
3. https://github.com/tektoncd/catalog

Create project.
Create all resources required to deploy spring-petclinic in created project.
Create required tasks, pipeline and pipeline resources with Kubernetes: Create command.
Run pipeline.
Open deployed application after pipeline execution is finished.

C:\git\vscode-tekton>npm run compile

> [email protected] compile C:\git\vscode-tekton
> tsc -p ./

src/extension.ts:3:28 - error TS2307: Cannot find module './explainer'.

3 import * as explainer from './explainer';
                             ~~~~~~~~~~~~~

src/extension.ts:5:32 - error TS2307: Cannot find module './yaml-navigation'.

5 import { findParentYaml } from './yaml-navigation';
                                 ~~~~~~~~~~~~~~~~~~~

src/tkn.ts:346:57 - error TS2339: Property 'metadata' does not exist on type 'TektonNode'.

346         let tasks: string[] = data.map((value) => value.metadata.name);
                                                            ~~~~~~~~

src/tkn.ts:375:61 - error TS2339: Property 'metadata' does not exist on type 'TektonNode'.

375         let pipelines: string[] = data.map((value) => value.metadata.name);
                                                                ~~~~~~~~

test/tekton/pipeline.test.ts:52:41 - error TS2554: Expected 3 arguments, but got 1.

52             expect(execStub).calledWith(Command.startPipeline(pipelineItem.getName()));
                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  src/tkn.ts:57:40
    57     static startPipeline(name: string, resource: string, param: string) {
                                              ~~~~~~~~~~~~~~~~
    An argument for 'resource' was not provided.

types/json-stream.d.ts:3:16 - error TS2665: Invalid module name in augmentation. Module 'json-stream' resolves to an untyped module at 'C:/git/vscode-tekton/node_modules/json-stream/lib/json-stream.js', which cannot be augmented.

3 declare module "json-stream"{
                 ~~~~~~~~~~~~~


Found 6 errors.

npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] compile: `tsc -p ./`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] compile script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Aurelien Pupier\AppData\Roaming\npm-cache\_logs\2019-07-25T07_53_23_070Z-debug.log

seems there are a lot of unused import, some of them doesn't exist anymore
metadata is effectively not defined in tektonNode which is a class of this project
npm run compile is reporting same errors

take care that npm install is not triggering the compilation (and so not reporting the error)

Tekton Triggers add the following CRDs:

• TriggerTemplate
• TriggerBinding
• EventListener

The extension should be able to show these CRs alongside other Tekton CRs.

Currently the only way to create resource is to use oc or kubectl tools form command line, there should be command to do that from context menu on Pipeline Resources node and command palette.
New Git resource workflow should let you select from repositories presented in workspace.
New Image resource workflow should let you slect form ImageStreams presented in cluster.

tkn delete commands have -f option to suppress confirmation from user. Rather than using terminal to run the command, extension should ask for confirmation as info message and then run delete command with progress and -f option.

On a cluster with a few pipelines and a whole lot of taskrun, I'm running into the following issue. It still loads the pipelines but…

/kind bug

Tile: Tekton Pipelines
Full name on page (description): Tekton Pipelines extension by Red Hat

Show ClusterTasks as top level items.

After .vsix file assembled it should be accompanied by .sha256 file. See example below:

• tekton-pipelines-0.1.2-420.vsix
• tekton-pipelines-0.1.2-420.vsix.sha256

The command to generate would be for example:

sha256sum tekton-pipelines-0.1.2-420.vsix > tekton-pipelines-0.1.2-420.vsix.sha256

Both files .vsix and .vsix.sha256 should be uploaded to nightly or stable builds.

This is happening because copy pasted code to detect message from odo about newer version available

For CI instances and PR Check, adding Azure Pipelines for all 3 OS variants.

tkn should now work with active context, so user can switch it using k8s extension Clusters view.

The Tekton extensions looks for tkn v0.3. It should be updated to latest which is 0.6 right now