Build failure for TRUNK-CORE2-15 Plan

Hi @dkayiwa we got this failure here

Work around ?

Which CI build plan is that?

This one

Problem was sonar certificate expiration. I have just disabled that task and run again.

Thanks let me look again.

I can see that you are bumping version numbers to 2.6.0 but this creates unnecessary work for the next release manager who will again have to bump them if they are not done. Just remove the fix version completely.

You mean the Tickets with Core 2.6.0 label ?

Also asking , about CIEL , are we gonna ping @akanter to give me access ? or there’s a workaround to release one using Dictionary Manager

Did i say label or fix version? :slight_smile:

I probably got you wrong. let me rectify

I can select a bulk of tickets with fix versions Core 2.6.0 and Platform 2.6.0 but no privilege to do a bulk change .Can you you give me the privilege ?

You are already an admin on the trunk jira project.

Okk let me check.

@dkayiwa any insights why

2.5.x is available at OpenMRS Core: Project summary - OpenMRS Bamboo but not seen here OpenMRS Platform - OpenMRS Platform: Branches - OpenMRS Bamboo

Because you have not created it. Create it from here: Log in as a Bamboo user - OpenMRS Bamboo

If you fail, get back to me and i create it for you.

1 Like

Cleared thanks…

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts: Could not transfer artifact org.openmrs.contrib:ciel-dictionary:zip:2.3.0_20211012 from/to openmrs-repo-contrib (JFrog): Transfer failed for JFrog 401 Unauthorized → [Help 1] [ERROR]

@dkayiwa any idea why uploading CIEL to maven repo returns a 401

any particular credentials to append on the request

Which step is that, from the release documentation?

it is step 5

Which wiki page?