Skip to content

The release profile matches the branch we actually release from #2

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

Merged
tastybento merged 1 commit into from
Aug 8, 2026
Merged

The release profile matches the branch we actually release from #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,12 +78,17 @@
<build.number>-b${env.BUILD_NUMBER}</build.number>
</properties>
</profile>
<!-- Release profile: fires only when Jenkins builds the release branch,
stripping the -SNAPSHOT and the -bNNN build number so the artifact is
just ${build.version}. The older addons match `origin/master`; this
repo's release branch is `main`, so the value has to match that or
every build stays a SNAPSHOT. -->
<profile>
<id>master</id>
<id>main</id>
<activation>
<property>
<name>env.GIT_BRANCH</name>
<value>origin/master</value>
<value>origin/main</value>
</property>
</activation>
<properties>
Expand Down
Loading