Looks like the `context` param is never used in 0.2 which fails builds that don't have the golang sources at the workspace root. Seems like a regression from 0.1.
Specification of Docker config location allows to point jib tool to the
Docker config file with registry auth information, provided by Tekton
via
https://github.com/tektoncd/pipeline/blob/main/docs/auth.md#configuring-docker-authentication-for-docker .
Without this fix jib is not able to find credentialss for private registries or
registries will limited pulls and build fails.
Fix is provided for all 3 existing versions of the task.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
The recipients of the email are extracted from a variable using the
split() function on a blank space (' '). If there are additional blanks,
either before, after or in the middle of the receivers_email variable the
sendmail function will cause an exception. This patch makes sure that blanks
won't cause the exception.
This will fix the issue of jib-maven task not passing digest to results
if the clone has happened in sub-directory and directory passed to
jib-maven task
It is because the directory param is not handled in path creation for digest
It will not break the existing the behaviour but fixing the issue for directory scenario
so doing the change in latest version
When no args are passed, we run pytest "" <path> which does not
work as expected. Only pass the args to pytest when there are
some defined.
Fixes#864
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
Update contributiong guide with guidance on how to bump a task and pipeline
make it easy for reviewers and have a clean git log.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Add a optional workspace for custom CAs. This will use pass down the optional
workspace path to git's GIT_SSL_CAPATH env variable (and subsequently to
libcurl).
Closes#660
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
This will add home env with value /tekton/home to the kn-apply task
as it throws warning sometime like
2021/11/03 12:18:36 warning: unsuccessful cred copy: .docker from
/tekton/creds to /: unable to create destination directory:
mkdir /.docker: permission denied
This env does not break the task so adding it in same version
Annotation about linux/amd64, linux/s390x, linux/arm64 and linux/ppc64le
platforms is added to the 0.1 version of the pylint task.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
PLATFORM env variable is introduced. This variable allows to run
tests for specific platform (for insance, "linux/s390x" or "linux/ppc64le").
If the environment variable is specified
- some tests are updated with different image values/other parameter
values, required for specific platform, using yq tool.
Custom values should be specified in the script file, separate for each
platform. In the current code script file for linux/s390x is proposed.
- only tasks, which have mention about corresponding platform support
in the annotation, will be tested.
If PLATFORM env variale is no specified, the behaviour of test scripts
will be similar to the one before the PR.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
Github markdown allows using 4 (or more) backticks to differentiate
between triple backticks inside the code blocks. Seeing as how most
task-diffs will probably have some form of markdown with codeblocks
inside them, this will escape that.
At this moment all tasks which can be executed on linux/s390x or
linux/ppc64le are tested and labelled accordingly.
The rest of the tasks can be labelled as `linux/amd64`, which
is default platform and where tasks are already tested via
default PR testing cycle.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
Annotation about linux/amd64,linux/s390x,linux/ppc64le and linux/arm64
platforms was added to the latest versions of curl, kn, kn-apply,
sendmail, and generate-build-id tasks.
Annotation about linux/amd64,linux/s390x,linux/ppc64le
platforms was added to the latest version of jib-gradle task.
For several tasks shas of the images were changed from amd64 specific
ones to multi-arch ones.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
Annotation about linux/amd64, linux/s390x, and linux/ppc64le platforms
was added to the latest versions of the git-batch-merge,
git-clone, git-rebase tasks.
Platforms annotation was changed for git-version task, leaving only
linux/amd64.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
add a section in Readme about short lived tokens that can be used in
lieu of password with a note about bitbucket server workaround.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Annotation about linux/amd64,linux/s390x,linux/ppc64le platforms was added
to the latest versions of the npm, wget, write-file, tekton-catalog-publish,
pytest, python-coverage tasks.
Container image SHAs were updated to use the latest versions with
multi-arch support for npm and wget tasks.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
Other small adjustments:
* Made input workspace optional
* Added some explanation on how to use the input workspace
* Included a reference for .ssh directory setup
Annotation about linux/amd64, linux/s390x, and linux/ppc64le platforms was
added to the latest versions of the golang-* tasks.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
The image is used in many catalog tests. To run the tests on many
platforms, the image should be the multi-arch one (at this moment -
linux/amd64, linux/ppc64le, linux/s390x, linux/arm64).
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
Helping a user in Knative slack, I noticed that the documented default on TektonHub (and the catalog) was different from what was actually in the task. This corrects the README.
When adding `fixtures` volume, we need to consider whether the task
already has a volumes section. If the volumes is already defined, then
we should add `fixtures` rather than replacing the whole volumes.
quay.io/buildah/stable:v1.18.0 and quay.io/skopeo/stable:v1.3.0 are
multi-arch images, bumping them for buildah and skopeo-copy tasks will
allow to run the tasks on different architectures.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
