Skip to content
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

👻 Add newfile.txt #20

Closed
wants to merge 3 commits into from
Closed

👻 Add newfile.txt #20

wants to merge 3 commits into from

Conversation

sjd78
Copy link
Owner

@sjd78 sjd78 commented May 10, 2024

No description provided.

@sjd78 sjd78 force-pushed the main branch 7 times, most recently from 3248556 to c1d0cfb Compare May 10, 2024 17:46
sjd78 added 2 commits May 10, 2024 16:56
  - Target my quay.io repository with standard image build

  - Drop architectures from the image build that I don't care about

  - Experiment with verdaccio npm registry mirror
    in image-build-2.yaml

Signed-off-by: Scott J Dickerson <[email protected]>
If the workflow is run from a PR, and the PR includes
a change to the `Dockerfile` or `package-lock.json`, then
run image builds for all of our target platforms.

The images are built but not pushed to any repository.

We want to be reasonably sure that any major build file changes
will not cause the image-build-and-push on PR merge workflow
to break.  Doing the image build here should show up most
problems much earlier.  For example, a npm version update
in the build container could break github action `nofiles`
or network access capabilities for the npm install.

See konveyor#1742, konveyor#1746, and konveyor#1781 for some other examples of
when this check could have caught issues before a PR
merge.

Supports: konveyor#1883

Signed-off-by: Scott J Dickerson <[email protected]>
Signed-off-by: Scott J Dickerson <[email protected]>
@sjd78 sjd78 force-pushed the main branch 4 times, most recently from 131f579 to f2647f4 Compare May 14, 2024 16:45
@sjd78 sjd78 closed this May 14, 2024
@sjd78 sjd78 deleted the fake_pr_1 branch May 14, 2024 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant