-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate docker image push on release ci pipeline #4928
Closed
paolino
wants to merge
34
commits into
paolino/4911/merge-2025-01-09-release
from
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
Closed
Automate docker image push on release ci pipeline #4928
paolino
wants to merge
34
commits into
paolino/4911/merge-2025-01-09-release
from
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We no longer run integration tests by building a nix derivation — we run shell scripts from the `justfile` instead. This means that we no longer specify configuration variables for our integration tests in nix.
- Update the mithril instructions to refresh the preprod state for the E2E tests #4918
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
from
January 9, 2025 17:42
ada042c
to
76da431
Compare
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
from
January 9, 2025 18:00
76da431
to
c3c3543
Compare
We no longer run integration tests by building a nix derivation — we run shell scripts from the `justfile` instead. This means that we no longer specify configuration variables for our integration tests in nix.
<!-- Detail in a few bullet points the work accomplished in this PR. Before you submit, don't forget to: * Make sure the GitHub PR fields are correct: ✓ Set a good Title for your PR. ✓ Assign yourself to the PR. ✓ Assign one or more reviewer(s). ✓ Link to a Jira issue, and/or other GitHub issues or PRs. ✓ In the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. * Don't waste reviewers' time: ✓ If it's a draft, select the Create Draft PR option. ✓ Self-review your changes to make sure nothing unexpected slipped through. * Try to make your intent clear: ✓ Write a good Description that explains what this PR is meant to do. ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding Jira ticket. ✓ Highlight what Testing you have done. ✓ Acknowledge any changes required to the Documentation. --> - [x] Multisig docs ### Comments <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number fix #4875 <!-- Reference the Jira/GitHub issue that this PR relates to, and which requirements it tackles. Note: Jira issues of the form ADP- will be auto-linked. -->
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
7 times, most recently
from
January 10, 2025 12:05
835dbbd
to
b9e2321
Compare
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
3 times, most recently
from
January 10, 2025 17:57
5cee18a
to
09862db
Compare
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
2 times, most recently
from
January 13, 2025 11:43
8c0f581
to
e6a9202
Compare
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
2 times, most recently
from
January 13, 2025 13:05
0377324
to
b980b5d
Compare
paolino
force-pushed
the
paolino/4900/automate-docker-image-push-on-release-ci-pipeline
branch
from
January 13, 2025 13:17
b980b5d
to
c1a71fa
Compare
Duplicate of #4937 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Issues
#4900