updating ubuntu image to 22.04 from 20.04 which is used in ci test
Signed-off-by: subhamkrai <srai@redhat.com>
(cherry picked from commit 11ce20feaf)
Signed-off-by: subhamkrai <srai@redhat.com>
The build and release actions will rarely ever need to be
debugged. To make them more efficient and reduce their
runtime, we remove the tmate action so it won't add 10
unnecessary minutes to the end of the action.
Signed-off-by: travisn <tnielsen@redhat.com>
with detached mode, we don't need to wait for the
tests to complete. Now, we can get inside tmate before
the tests start and we can monitor the tests.
By default, this mode will wait at the end of the job for
a user to connect and then to terminate the tmate session.
If no user has connected within 10 minutes after the post-job step started,
it will terminate the tmate session and quit gracefully.
Signed-off-by: subhamkrai <srai@redhat.com>
we need make `limit-access-to-actor: false` and also
in the right place where tmate `uses` is called for
composite yaml.
Signed-off-by: subhamkrai <srai@redhat.com>
Go 1.18.5 and other Go 1.18 version patches provided many vulnerability fixes
but as go.mod doesn't support minor version i.e why moving to next go release
Signed-off-by: Pratik Raj <rajpratik71@gmail.com>
* Unconditionally offer it when running from the rook org
* Offer it if the current repository has a USE_TMATE secret
* Offer it if the workflow is being re-run
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
The setup tools package and libgit2 are required on
ubuntu 18.04 in order to install the mkdocs framework
and publish the docs. After we move to ubuntu 20.04
this should no longer be necessary.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The push image build CI action is mistakenly running on
arm64 instead of amd64, which is failing the build since
it only expects amd64.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Do not use the cross build container when building, publishing, and
promoting rook/ceph images. It is no longer needed, and its complexity
can add flakiness.
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
This reverts commit c53304c3b4.
After experimenting with this release, we have found that the
`workflow_run` action source doesn't work for branches. The
documentation was updated with this PR and has more detail.
https://github.com/github/docs/pull/531
For now, we will revert back to using on.push.tags = ["v*"]
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
earlier push build action was not triggered due
to github action limitation.
```
An action in a workflow run can’t trigger a new workflow run.
```
so now, we'll use user personal toke to create tag so that push
build action pick the user not github action who created the tag.
Closes: https://github.com/rook/rook/issues/8580
Signed-off-by: subhamkrai <srai@redhat.com>
The unshallow step in the action is replaced now with the
fetch-depth: 0 option on the checkout@v2 action.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit c6d8df931f)
The tagged builds will run git checkout on the correct tag,
though the publish and promote actions expect a branch name
to be available due to internal build assumptions. Now the
publish looks up the branch name from the tag and passes
it to the publish command as expected.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit d8c5f459de)
For all Rook-maintained GH actions, use a default shell that has xtrace
enabled to help debug any errors.
Enable xtrace on all actions except these that use only external tools:
- codespell
- commitlint (wagoid/commitlint)
- golangci-lint
- helm-lint (chart-testing)
- stale
- yamllint
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
For the github action to publish the build to aws, we also need to
include the aws-region setting in the action settings.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
We are moving towards github action.
This commit allows pushing build images
to Docker hub using gh action for master
build similar to what Jenkins does.
And, also removing `Publish if Master` step
from the Jenkinsfil file.
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai
dependabot[bot]
Travis Nielsen
parth-gr
Deepika Upadhyay
Pratik Raj
neilnaveen
Josh Soref
Alexander Trost
Blaine Gardner