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.

Sign up for GitHub

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

Jump to bottom

Update Parfait Release process to support latest PCP/containers #130

Open
tallpsmith opened this issue Nov 13, 2024 · 0 comments
Open

Update Parfait Release process to support latest PCP/containers #130

tallpsmith opened this issue Nov 13, 2024 · 0 comments
Assignees
@tallpsmith

Comments

@tallpsmith
Copy link
Contributor

The original Parfait release process I used relied on a Docker setup that worked because installing the older PCP in a container didn't try to start PCP at the end (or at least didn't error when it did so).

Some recent updates/upgrades to Parfait now also do not work well inside the container due to Mockito changes.

This issue addresses this so that we can complete a Parfait release (or at least I can on my Mac...)
@tallpsmith tallpsmith self-assigned this Nov 13, 2024
tallpsmith added a commit that referenced this issue Nov 13, 2024
@tallpsmith
#130 Modify the Dockerfile used for the Release process to use the su…
8aebbb7 
…pported Quay.io hosted containers.
tallpsmith added a commit that referenced this issue Nov 13, 2024
@tallpsmith
#130 Make the surefire plugin use a JVM option to allow Mockito to wo…
771349a 
…rk properly inside the release container.

this does have the sideaffect of slowing each of the tests, perhaps I'll modify this to be a profile triggered by an environment option, but for now it's not _too_ slow to run the build.
tallpsmith added a commit that referenced this issue Nov 14, 2024
@tallpsmith
#130 Turns out, this isn't actually needed.
5c55a52 
Maybe needed for a newer JDK, but not 11.
tallpsmith added a commit that referenced this issue Nov 14, 2024
@tallpsmith
#130 Simplify launch with WORKDIR
7d56c14
tallpsmith added a commit that referenced this issue Nov 14, 2024
@tallpsmith
#130 Introduce concept of .releasing.env which needs to be ignored by…
5cd8ecf 
… git
tallpsmith added a commit that referenced this issue Nov 14, 2024
@tallpsmith
#130 Introduce Release batch file which launches the Docker build/rel…
4ad7d8b 
…ease process and automates GPG key fun
tallpsmith added a commit that referenced this issue Nov 14, 2024
@tallpsmith
#130 Updating RELEASING.md with the current steps, and small edits to…
5b94753 
… README to indicate supported JDKs (for the build itself).
@tallpsmith tallpsmith mentioned this issue Nov 14, 2024
Merged
tallpsmith added a commit that referenced this issue Nov 15, 2024
@tallpsmith
#130 Almost there with the SSH_AGENT/SCM integration. Git tag works.
57c1db6
tallpsmith added a commit that referenced this issue Nov 19, 2024
@tallpsmith
#130 Include the configured Release & Development versions into the M…
89eedb3 
…aven Release invocation.
tallpsmith added a commit that referenced this issue Nov 19, 2024
@tallpsmith
#130 Looks like these properties need to be after the goal otherwise …
9549f27 
…they seem to get ignored.
tallpsmith added a commit that referenced this issue Nov 19, 2024
@tallpsmith
#130 This may be screwing up the release process.
bb62d48
tallpsmith added a commit that referenced this issue Nov 19, 2024
@tallpsmith
#130 GPG Passphrase env variable may not be getting passed to the lau…
4ad5127 
…nched Maven release command
tallpsmith added a commit that referenced this issue Nov 19, 2024
@tallpsmith
#130 GPG Passphrase hell no. 28478575...
126c08c
tallpsmith added a commit that referenced this issue Nov 21, 2024
@tallpsmith
#130 Consolidate the environment properties into the .releasing.env f…
9ffafe6 
…ile and let Docker use that instead of manually passing each along.

This now also allows a dryRun property to come across easily.
tallpsmith added a commit that referenced this issue Nov 21, 2024
@tallpsmith
#130 Revert back to 1.2.1-SNAPSHOT, forgot to rollback the previous t…
091bcbf 
…est release.

SCM tag and Maven central repo had been dropped, so 1.2.1 had never actually been officially released.
tallpsmith added a commit that referenced this issue Nov 21, 2024
@tallpsmith
#130 Add back in release:perform phase now that dryRun is working.
3370680
tallpsmith added a commit that referenced this issue Nov 29, 2024
@tallpsmith
#130 Modifications to the new suggested Maven release process.
4da550f 
My suspciion is with some previous pom refactoring we were missing the configured Release profile trigger which generated important stuff for the deploy, probably rejecting the artifacts somewhere?
tallpsmith added a commit that referenced this issue Nov 29, 2024
@tallpsmith
#130 Revert back to 1.2.1-SNAPSHOT version
ac6b3c3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tallpsmith tallpsmith

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tallpsmith