starting release of 1.48.0...

[Jim Hargrave]

I was able to pull in Chase's recent commits.

Probably take me a few days but will do a full release with apps.

deployment/maven/build.sh baJim

[Jim Hargrave]

I deployed the new apps and updated websites, made 1.49.0-SNAPSHOPT in main etc,, but having an issue with the sonotype release logic. I created a tag v1.48.0 as normal. But then used gitlab to create a release - whoch failed during the sonotype deployment. 

What I'm I missing?

BTW: Many thanks to Mihai's instructions for getting me this far!!

Jim

[Jim Hargrave]

I reran the release pipeline and saw this:

[INFO] Uploaded bundle successfully, deployment name: Okapi-1.48.0, deploymentId: 87c517f1-d764-4bfe-b294-708732f34e33. Deployment will require manual publishing

[INFO] Waiting until Deployment 87c517f1-d764-4bfe-b294-708732f34e33 is validated

[ERROR]

Deployment 87c517f1-d764-4bfe-b294-708732f34e33 failed

pkg:maven/net.sf.okapi.logbind/build-...@1.48.0:

- Project name is missing

Jim

[Denis A. Konovalyenko]

Hi Jim,

It looks like I have missed the conference and release time... :)

I assume there must be specified the project name in the okapi/deployment/logbind-logback/pom.xml. I tend to think that something like the following should be enough:

<name>Build Okapi Logback</name>

At the same time, I noticed that there is not only "The 1.48.0 release" commit but also "Prepared dev for 1.49.0-SNAPSHOT" one. So, the latest or even both of them should be reverted in order to add the required to the 1.48.0 release...

And one more note. According to the Okapi tags section on GitLab The latest tag is "v1.4.8" and the "v1.48.0" one is not present. Should not we push the "v1.48.0" instead?

In any case, to speed this up a bit, a related merge request #961 has been opened to make the initial step for addressing the deployment hicup.

With best regards,

Denis

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/2cd01aa3-0ed4-4146-8a1b-57b02c1d0f79%40gmail.com.

[Denis A. Konovalyenko]

Jim,

I do not know if the revertion of commits mentioned in the merge request #961 would also delete related tags. So, it might be necessary to delete them locally and remotely before moving on to making a release one more time.

Local deletion:

git tag --delete <tagname>

And remote:

git push --delete <remote> <tagname>

where <remote> is the name of your remote repository (commonly "origin")

and <tagname> is the name of the tag.

A possible example that would work for me:

git tag --delete v1.4.8
git push --delete upstream v1.4.8

Thanks!

Denis

[Denis A. Konovalyenko]

Jim,

And one more note - the CI release stage deploys all artifacts to Central Sonatype, and they have to be manually published by selecting the appropriate deployment and clicking "Publish".

Here is a UI to make it easier to follow up.

There should appear a new one. Others can be dropped. :)

Thanks,

Denis

P.S.:

Sonatype login details can be found under the CI/CD Settings > Variables:

- MAVEN_REPO_USER

- MAVEN_REPO_PASS

[Jim Hargrave]

Thanks Denis - I will recreate the tag with the correct name. I created it from cherry picking the 1.48.0 release commit. Possible I missed a step or incorrectly applied the instructions.

This is something we need to automatate in the future. 

Jim

To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/3338b921-18a0-e504-98ec-c6b3d97cb0f2%40gmail.com.

[Jim Hargrave]

BTW: I tried logging into the nexus repository manager (using both my saved username/password and those found in gitlab variables) and it failed. Perhaps they have expired?

Jim

To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/3338b921-18a0-e504-98ec-c6b3d97cb0f2%40gmail.com.