Eventually we want to be able to have Tasks declare what versions they
are compatible with and test against those
(https://github.com/tektoncd/catalog/issues/373) but in the meantime, it
seems reasonable to bump the version every time we do a release (and
even once we have #373, we would want to be running tests against new
versions as well - and this could have the benefit of giving us
information about issues in a release early, before users notice them!)
This task allows you to generate Kythe annotation metadata for a given
Go project. This follows the workspace model as presented by the `git`
Task. The expectation is that any results place in the workspace will be
exported by another Task in the pipeline for remote storage (e.g. GCS,
etc).
(cherry picked from commit 20d449cd43)
Since the "master" branch has been renamed to "main", let's make sure we pin to
a revision and fix if there is other rename going on.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
create curl task to request response from internet
Add a readme file to specify how to run curl task
Modify parts of the readme file
create two simple taskruns to test curl
change spec for url value
change spec to re-push
change image place to be param
users now can pin the version of image as they want
Add a new param
add a curl image option so users now can use different version of curl image at will
update readme file on param description
- This was to update to the new standard for issue templates for github.
- Also added a `.config.yml` which is also part of the new version
Signed-off-by: JJ Asghar <jjasghar@gmail.com>
The requirements discussed in #233
- action: ['get', 'create', 'apply', 'delete', 'replace', 'patch'] -- the action to perform to the resource
- merge_strategy: ['strategic', 'merge', 'json'] -- the strategy used to merge a patch, defaults to "strategic"
- success_condition: a label selector expression which describes the success condition
- failure_condition: a label selector expression which describes the failure condition
- manifest: the kubernetes manifest"
… also talk a little bit about `privileged` and how to be explicit in
the task if it needs to be run as root and/or privileged.
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
This change makes it possible for users to provide
environment variables to buildpacks via a volume with
appropriately configured directories.
Also includes some fixes for v1beta1 compatibility.
See https://buildpacks.io/docs/reference/buildpack-api/
for more info on how PLATFORM_DIR is used.
Resolves#160
Signed-off-by: Natalie Arellano <narellano@vmware.com>
This task can be used to make a release on the Gitlab.
Assets or binaries of the released version can also be uploaded with the release.
Signed-off-by: Divyansh42 <diagrawa@redhat.com>
Test would be failing if there is a directory but no yaml template in there,
which in reality we should not have this happening but it happens sometime.
let's make sure we skip the test if there is no yaml files then.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Current task doesn't support merge requests. Added support
for merge requests in the same task.
Now we can add labels to merge requests as well.
Signed-off-by: Divyansh42 <diagrawa@redhat.com>
The git-clone example only demonstrated the very simplest of behaviour
and didn't provide much in the way of instruction on using its features.
This PR adds examples for cloning a branch, cloning a specific commit,
and cloning tags. Each example includes clear description of its purpose
and the features it demonstrates.
I've removed the inline git-clone example from the README because it's
really long and the README needs to serve the purpose of documenting
multiple Tasks (git-clone as well as git-batch-merge, and any future
Tasks we add as well). Rather than bloat the README with many examples
which can go stale if we modify git-clone's behaviour I've simply linked
to the new example files.
Parameterized the UPI image so that if anybody wants to use their image then they can use it and also updated the README
Signed-off-by: vinamra28 <vinjain@redhat.com>
The following task can be used to do static analysis of the source code by taking SonarQube server URL as the input.
Signed-off-by: vinamra28 <vinjain@redhat.com>
