Closed GrantBirki closed 1 year ago
.deploy noop
Your branch is behind the base branch and will need to be updated before deployments can continue.
BLOCKED
warn
Please ensure your branch is up to date with the
main
branch and try again
.deploy
Your branch is behind the base branch and will need to be updated before deployments can continue.
BLOCKED
warn
Please ensure your branch is up to date with the
main
branch and try again
Now I'm going to test with update_branch: disabled
set
.deploy
GrantBirki, started a branch deployment to sandbox
You can watch the progress here 🔗
Branch:
test
Deployment will not continue. Please try again once this branch is up-to-date with the base branch
testing with update_branch: force
.deploy
BLOCKED
force
I went ahead and updated your branch with
main
- Please try again once this operation is complete
@GrantBirki
Hi! I'm wondering if the version of GHES (3.6.2) used may be a factor. If you can re-run with debug logs I can do a more detailed comparison between your run logs and my own tomorrow to try and get a clearer picture.
@KevinMSampson Of course! Let me know which job you would like me to re-run (link) and I'll do so with debugging enabled. Thanks!
@GrantBirki the 2nd deploy run in this PR would be great to debug compare (normal deployment with warn enabled)
.deploy
Your branch is behind the base branch and will need to be updated before deployments can continue.
BLOCKED
warn
Please ensure your branch is up to date with the
main
branch and try again
Your branch is behind the base branch and will need to be updated before deployments can continue.
BLOCKED
warn
Please ensure your branch is up to date with the
main
branch and try again
@KevinMSampson I have re-run the CI job for .deploy
with update_branch: warn
set
Here are the actions log for that command with debug mode enabled
Please note this was done with
github/branch-deploy@v4.6.0
@KevinMSampson I would also suggest opening a new issue in the github/branch-deploy repo as I don't actively monitor this repo all that much as its just for me testing around with Actions and the sorts. Thanks! ⭐
.lock
You are now the only user that can trigger deployments to the production
environment until the deployment lock is removed
This lock is sticky and will persist until someone runs
.unlock production
.lock
Sorry GrantBirki, the production
environment deployment lock is currently claimed by monalisa
production
test
2023-03-13T14:57:31.648Z
monalisa
true
false
The current lock has been active for 0d:0h:0m:53s
If you need to release the lock, please comment
.unlock production
.wcid
The deployment lock is currently claimed by GrantBirki
tset
headless mode
2023-03-13T18:28:56.254Z
GrantBirki
true
production
The current lock has been active for 0d:0h:0m:17s
If you need to release the lock, please comment
.unlock production
.lock
.lock production
GrantBirki, you are already the owner of the current production
environment deployment lock
The current lock has been active for 0d:0h:1m:51s
If you need to release the lock, please comment
.unlock production
GrantBirki, you are already the owner of the current production
environment deployment lock
The current lock has been active for 0d:0h:1m:56s
If you need to release the lock, please comment
.unlock production
.unlock
The production
deployment lock has been successfully removed
.wcid
The deployment lock is currently claimed by GrantBirki This is a global deploy lock - All environments are currently locked
fire
headless mode
2023-03-13T18:32:18.584Z
GrantBirki
true
all
true
The current lock has been active for 0d:0h:0m:49s
If you need to release the lock, please comment
.unlock --global
.deploy
Your branch is behind the base branch and will need to be updated before deployments can continue.
BLOCKED
warn
Please ensure your branch is up to date with the
main
branch and try again
.deploy
GrantBirki, started a branch deployment to production
You can watch the progress here 🔗
Branch:
test
GrantBirki successfully deployed branch test
to production
.lock
GrantBirki, you are already the owner of the current global deployment lock
The current lock has been active for 2d:21h:17m:29s
If you need to release the lock, please comment
.unlock --global
You are now the only user that can trigger deployments to the production
environment until the deployment lock is removed
This lock is sticky and will persist until someone runs
.unlock production
.lock
You are now the only user that can trigger deployments to the production
environment until the deployment lock is removed
This lock is sticky and will persist until someone runs
.unlock production
.lock
GrantBirki, you are already the owner of the current production
environment deployment lock
The current lock has been active for 0d:0h:0m:39s
If you need to release the lock, please comment
.unlock production
.deploy noop production
.deploy noop development
GrantBirki, started a noop deployment to production
You can watch the progress here 🔗
Branch:
test
GrantBirki successfully noop deployed branch test
to production
GrantBirki, started a noop deployment to development
You can watch the progress here 🔗
Branch:
test
testing -> https://github.com/github/branch-deploy/pull/117