These changes introduce the Buildpacks Pipeline. This pipeline
builds source into a container image using Cloud Native Buildpacks.
To do that, it uses builders to run buildpacks against your application source.
It relies on git-clone, buildpacks, and buildpacks-phases tasks to perform
it's tasks.
Signed-off-by: Javier Romero <rjavier@vmware.com>
Following TEP 70, tekton.dev/platforms annotation can be used to
specify on which platforms the resource can be run.
- add best practices for platform information in the recommendations.md
- add example of usage for tekton.dev/platforms annotation
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
Add a parameter through which we can set the `HOME` env variable which
if not provided will default to `/tekton/home`. Also set the default
`workingDir` as `/workspace`.
Signed-off-by: vinamra28 <vinjain@redhat.com>
git-clone 0.1:
Add a parameter through which we can set the `HOME` env variable which
if not provided will default to `/tekton/home`
git-clone 0.4:
Changed the default value of userHome param from `/root` to
`/tekton/home` as it was not matching the README.
Signed-off-by: vinamra28 <vinjain@redhat.com>
Add a parameter through which we can set the `HOME` env variable which
if not provided will default to `/tekton/home`
Signed-off-by: vinamra28 <vinjain@redhat.com>
Add a parameter through which we can set the `HOME` env variable which
if not provided will default to `/tekton/home`
Signed-off-by: vinamra28 <vinjain@redhat.com>
logining in from one container and having sync and wait run in a
separate containers does not work. Authenticate once and reuse the connection
across the containers in a pod is not supported. Sync and wait fails with
authentication error. Either we login at each step or collapse
sync and wait along with the login step. Or we could authenticate once and
find a way to how to reuse the same connection across the containers.
For now, combining everything into a single step.
Fix trailing space
Fix version obviously
Fix text typo
Add Test for Github Open PR
Fix hosts
Update test fixture
Add better and more tests
Use localhost
Fix HTTP and HTTPS
Fix typo
Add PR number and URL results
Fix tests and use correct URL
Remove duplicate line
Set correct URL over here as well
This will add a new version 0.4 in jib-maven task which
have only one change of different mounth rather than /etc/ssl/certs
as mounting at that location is overidding the default certs of
the image. This will make the certs to mount at different path
/tekton-custom-certs
This commit introduces a 0.4 version of git-clone, fixing several
problems with the 0.3 git-clone Task:
1. Credentials in 0.3 could not be passed directly to the Task via
a Workspace.
2. There was no support for running as a non-root user.
This commit introduces a new version of git-clone that fixes both
of these issues. Credentials (either basic-auth or ssh-directory)
can now be supplied directly using a Secret workspace. A nonroot
user is provided with UID 65532 that can clone repos without
requiring root permissions.
This use python multi string when getting the comment
params so we don't bug out on multi lines comments.
Signed-off-by: vinamra28 <vinjain@redhat.com>
Allow overriding the GO cache, GO mod caching and golangci-lint caching.
Optimize golang-build and golang-test to not do a fulll copy of the source
inside the GOPATH if we have a go.mod in source root directory.
Bumped task since we add a bunch into it.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
The regexp was catching up golang-test/ task so it will always test
everything when there is in golang-test/
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Update title with copy paste err
Add quotes to get rid of lint issues
Fix some more issues with shell linting
Linting - Add double quotes over here as well
Setup the incoming webhook as a secret due to it's sensitivity
* Allow defining the github api url
* Handle Exception better by showing the error message.
(i.e: in case if ntp is not syncronized the jwt token would not be issued)
Few task's README contains some url links which had
invalid directory path and was pointing to a invalid page
Signed-off-by: Shiv Verma <shverma@redhat.com>
In write-file task's tests we are checking whether file permission is
equal to `--w--wxr-T`. These permissions may vary depending on rbac
enforced cluster. Example on some cluster we can get the value as
`-rw-rwxr-T` thus failing the test.
In this commit I am removing the `grep -- '--w--wxr-T'` so that the
tests doesn't fail on other clusters.
Signed-off-by: vinamra28 <vinjain@redhat.com>
When the optional dockerconfig workspace is set, set the
DOCKER_CONFIG env variable accordingly.
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
The syntax of the find command was not correct, and the error was not
caught by CI because of the missing "set -o pipefail".
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
Add a new task that uses tkn bundle to publish a Tekton catalog as
bundles to a container registry. Each task corresponds to a dedicated
bundle, which task versions available as tags.
Optionally, bundles are tagged with an extra tag provided as an input
parameter.
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
Add a catalog task to write a parameter out as a file, creating
intermediate directories and setting permissions as necessary. While it
is possible today to have a workspace that is a mounted config map
variable, that provides limited support for expanding parameters into
the file (i.e. the [replace-tokens](https://hub.tekton.dev/tekton/task/replace-tokens) task).
Ultimately, my argument for adopting this task into the catalog is that
I believe others will also look for a file-writing task and their
experience of Tekton will be better if they find one.
Previously we passed params directly into the `script` block of
the clone step. Because Pipelines doesn't escape variable values
when interpolating them the behaviour of the task could be changed
by the contents of a param.
This commit changes the way params are provided to the script;
instead of being interpolated directly they are converted first
into environment variables and accessed through shell's `${}`
construct.
Writing my first contribution to the catalog, I failed to find the
authoring recommendations, resulting in unnecessary Slack noise.
This adds references to parts of the documentation that I did
read in the hope that others will see them in time.
I removed the recommendations list that was inlined in CONTRIBUTING.md
as it is covered by the linked recommendations.md.
Added a new params to allow getting the application_id from the secrets
workspace, still allowing as params directly if user would like to use
this instead.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
