Re: [ee4j-build] First working release job

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Tomas Kraus wrote on 10/04/2018 07:09 AM:
> Hi All,
> I've got 1st release job working on new Jenkins:
> https://jenkins.eclipse.org/jaxb-impl/job/jaxb-fi-release/
> 
> release script from this job is attached.

There's so much magic in that script, I'm not sure what to do to adapt it
for my job.

For example, what do I do about this:

# Setup jaxb-impl-bot account information
git config --global user.email "jaxb-impl-bot@xxxxxxxxxxx"
git config --global user.name "Eclipse JAXBimpl Bot"

Does every project have an automatically created "bot" user?

And then for this:

echo '-[ Deploy artifacts to staging repository
]-------------------------------------'
mvn -U -C -s /home/jenkins/.m2/settings-jaxb-impl.xml \
    -DskipTests -Ddoclint=none -Prelease \
    clean package source:jar javadoc:jar gpg:sign install:install ${MVN_DEPLOY_ARGS}

You're using a "release" profile, but the parent pom has an "oss-release"
profile.  Does that mean you had to duplicate all that configuration in
your pom?  If you had renamed your profile to "oss-release" would it have
been simpler?  Can Maven be told to use two profiles and "merge" them?

What's the difference between "install:install" and "install"?
Ditto "deploy:deploy"?

Aren't some of those Maven steps implied by install or deploy?

If this just deploys to a staging repository, how does it get pushed out
to the real repository?

If the artifact I deploy is a SNAPSHOT release, do I need to change anything
in the above mvn command?