Add support for REST services testing, if we have a directory in the tests
directory called `fixtures` with a yaml file that contains a responder
rules (see github-add-comments task example) it will add a sidecar task from
https://github.com/chmouel/go-rest-api-test/ so the test can point to it.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Rather than forcing task users to create a secret with a fixed
name, allow setting the secret name and key as parameter.
The new parameters are optional, in the sense that they default
to the previous hardcoded values.
This task can be used to builds Go binaries for several platforms,
creates a GitHub release and then pushes a Homebrew formula to a tap
repository using [goreleaser](https://github.com/goreleaser/goreleaser).
Signed-off-by: vinamra28 <vinjain@redhat.com>
When running on GCP, gsutil will try to infer identity from the GKE
metadata service instead of an explicitly defined credential file. The
easiest way to support this is to only set the credentials iff the file
is provided, otherwise just fallback to gsutils default behavior.
Also adds a simpler example that doesn't require credentials.
This task will be used to format python code after doing a lint check and will not complain for the errors.
Signed-off-by: vinamra28 <vinjain@redhat.com>
This add the github app token, this would help to get a user token from a github
app which can be perused to do github operations.
Flow would are usually going like this :
events -> triggers event listenner \
-> start pipeline
-> get user token from app (with this task)
-> do operation (like ci checks or others) on github with this
token.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
This PR is to add `servers` tag for the private repository server.
It is assumed to be used with `MAVEN_MIRROR_URL`, for example, when using a cached library on a private network.
Buildah image in few tasks was not pointing to latest
image release tag, so updated the image to point to
latest release.
Signed-off-by: Divyansh42 <diagrawa@redhat.com>
Earlier git-clone assumes `master` as default branch, but after #2835
`master` is no more default branch. Hence, updated the git clone task
fetch a remote repository's default branch instead of assuming "master"
when revision is "".
Signed-off-by: Divyansh42 <diagrawa@redhat.com>
The following task uses the released version of tekton operator to install tekton components on a new cluster. By default Tekton pipelines are installed but if we want to install other components as well then we can specify their version in the parameters of the task and respective component will get installed.
Signed-off-by: vinamra28 <vinjain@redhat.com>
This line queries twice to the github api in order to apply the tekton release yaml. It would increase readability if we just use the googleapi to fetch the yaml.
The end to end test attaches a sidecar with a image registry for tasks to push into to. However, the function add_sidecar_registry sets the sidecar registry instead of appending it. Removing the function from test to remove this bug. There is a local registry being added to the test that is deployed with deployment and svc. The svc is referenced during the test instead of the sidecar. #481
This PR is to improve the existing maven tasks and support context directory switch in case of multi-module maven projects. Also the settings.xml was being `cat` so removed that also. This is being added as version 0.2 in maven task
Signed-off-by: vinamra28 <vinjain@redhat.com>
CI was not able to monitor some pipelineruns for tasks in catalog example maven task and was getting "Could not find a created taskrun or pipelinerun in maven-0-1+ breakit=True" which is not the expected behaviour so with this patch we will iterate over it 5 times and check for it's status and reason
Signed-off-by: vinamra28 <vinjain@redhat.com>
This commit adds git-clone v0.2. One default behaviour has changed
and one new param has been introduced in this version:
1) Tasks that don't start their script with #! automatically receive
a preamble that includes `set -x`. This results in verbose output
because every command is printed while the Task is running.
This commit adds a new param, "verbose", that - when set to "false"
- prevents the commands run by the task from being printed to logs.
The default value is "true": the commands run by the task will be
printed in the log.
2) The git-clone Task offers a param, deleteExisting, that cleans
any existing directory before performing a clone into it. This
has previously been set to "false" by default since it's potentially
destructive. But it sounds like there's quite often a request for
how to enable this behaviour, so it seems like the more pragmatic
default would be "true".
This commit sets deleteExisting to be defaulted to "true" so that
any existing git checkout is removed prior to a new clone being
performed.
If the user want to use another image than what we release on gcr.io let give
this option by introducing the param `gitInitImage` to set this up which would
default to the gcr.io image as it was before.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
This script will allow the developer to test a task directly withouth having to
send it to the CI and wait that all tasks runs to test it.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Also, modify the git-batch-merge test to use actual changes - using
`kelseyhightower/nocode` was cute, but ended up masking the actual
problem that not setting `depth` to `0` by default was making all
merges fail. So let's use our own repo, two merged PRs, and the
ancestor of the first of those PRs.
fixes#477
Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Use variable $(workspaces.source.path) for path (pytest)
Add OWNERS file
Use latest tag for the python images as default
Signed-off-by: wumaxd <wurzer.maxi@gmx.de>
* Only intall the requirements when the file is here
(sometime we write pure python script that doesn't need external libs)
* fix installing pylint when needed
* Use variable $(workspaces.source.path) for path
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
To make sure the checklist is useful and folks don't ignore it, I think
it's important to keep only the items we need to in there.
If we can enforce something with CI, I suggest we do not include it in
the checklist - if we want to write down guidance somewhere else I think
that totally makes sense, but not in the checklist.
From https://github.com/tektoncd/catalog/issues/387 it looks like
linting should be applied automatically to each PR so I don't think we
need to include this checklist item.
This will refactor the namespace name to have version of task
in namespace name as current logic may create issue in case
of multiple versions running in same namespace as pid will
remain same
I added support for TaskRunResults for this task. This change adds four results:
- the sha256 hash of the bdist package and the sdist package.
- the package name
- the package version
I also fixed a permission issue in the sample - I could not get this to run as a non-root
user (even without my change). The git repo is cloned correctly, but the default user of the
twine image does not have write permissions in this directory.
