Sorry for the delay, my filter filtered out this thread.

Yes, this merge job was resolved Oct12.
I am in another thread explaining the issues with the released versions too
with Guangrong

Global-jjb has a fix now to flag these occurrences and we will plan for an
upgrade of global-jjb soon.

I can bring this topic up in the TSC.

On Thu, Oct 17, 2019 at 3:19 AM Lefevre, Catherine <
catherine.lefe...@intl.att.com> wrote:

> Good morning Guangring, Jessica,
>
>
>
> Can you please confirm that this issue has been solved ?
>
>
>
> Many thanks & regards
>
> Catherine
>
>
>
> *From:* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *On
> Behalf Of *Guangrong Fu
> *Sent:* Saturday, October 12, 2019 2:28 AM
> *To:* jwagant...@linuxfoundation.org
> *Cc:* onap-rele...@lists.onap.org; onap-tsc@lists.onap.org;
> jba...@linuxfoundation.org; kp...@linuxfoundation.org;
> dmcbr...@linuxfoundation.org
> *Subject:* Re: [onap-tsc] [Onap-release] Releases not matching intended
> versions
>
>
>
> Hi Jess,
>
>
>
> Thanks for your information.
>
>
>
> I was trying to fix it by bumping the version number, but the merge job
> raised a 401 problem (
> https://jenkins.onap.org/view/holmes/job/holmes-common-master-merge-java/146/console
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_holmes_job_holmes-2Dcommon-2Dmaster-2Dmerge-2Djava_146_console&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=6hpYrAO5uiI2TBTvsC5qb5yqxbn6uLLbZAbYGaHsy9M&e=>).
> Could you please take a look?
>
>
>
> Thanks,
>
> Guangrong
>
>
>
>
>
>
>
>
>
> 原始邮件
>
> *发件人:*jwagant...@linuxfoundation.org <jwagant...@linuxfoundation.org>
>
> *收件人**:*onap-release <onap-rele...@lists.onap.org>;onap-tsc <
> onap-tsc@lists.onap.org>;James Baker <jba...@linuxfoundation.org>;Kenny
> Paul <kp...@linuxfoundation.org>;David McBride <
> dmcbr...@linuxfoundation.org>;
>
> *日 **期 * *:*2019年10月12日 05:27
>
> *主 **题 **:[Onap-release] Releases not matching intended versions*
>
> Dear ONAP team.
>
> I wanted to give you a heads up that today we have flagged 3 releases
> files that were created
>
> with the wrong versions. This is caused from the releases files where
> teams define a "version"
>
> variable but the build they are selecting as a candidate has a different
> version.
>
> For example:
>
>
>
> *https://gerrit.onap.org/r/#/c/demo/+/96967/1/releases/1.5.0.yaml
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_demo_-2B_96967_1_releases_1.5.0.yaml&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=4KYkSNkeSdbCoz2tYecICLYyjf44INMSpbNYUGexYLs&e=>
> -> the release candidate*
>
> *is 1.6.0 not
> 1.5.0: https://jenkins.onap.org/job/demo-maven-stage-master/151/console
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_job_demo-2Dmaven-2Dstage-2Dmaster_151_console&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=xu0mwULQUCYhT7Z9Fa5ODOvwsRiEOmJ0Q1Lxu8Odq5c&e=>*
>
>
>
> *https://gerrit.onap.org/r/#/c/cli/+/96781/2/releases/5.0.0-maven.yaml
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_cli_-2B_96781_2_releases_5.0.0-2Dmaven.yaml&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=52RKAFsVhuWgPOc76Rx1bLjNi4hDzGYpadXed0jPujc&e=>
> -> the release candidate*
>
> *is 4.0.0 not 5.0.0
> -> https://jenkins.onap.org/job/cli-maven-stage-master/113/console
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_job_cli-2Dmaven-2Dstage-2Dmaster_113_console&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=WNpKM6HfUkids6unyKIujp7x_pl0QwW95B_h7Yw4qbk&e=>*
>
>
>
> *https://gerrit.onap.org/r/#/c/holmes/common/+/96870/1/releases/maven-1.2.12.yaml
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_holmes_common_-2B_96870_1_releases_maven-2D1.2.12.yaml&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=Ex6NhXZ6LfmcDB_FxAd8_fuyUr6IrrhxeJuhXwWwR6g&e=>
> ->*
>
> *the release candidate is 1.2.11 not 1.2.12
> -> https://jenkins.onap.org/job/holmes-common-maven-stage-master/162/console
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_job_holmes-2Dcommon-2Dmaven-2Dstage-2Dmaster_162_console&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=JnJhUapsymeN5rzC2vasqcZSa1-x28p1Fg-Fop29IKg&s=tu7Lmb19RmbVf6KyQp-eO-oDiz8nWHI1qhSc5kZ4p5w&e=>*
>
>
>
> Please make sure to double check your pom and version.properties that they
> match the version
>
> your team is working on.
>
>
>
> *Comitters:* please double check releases files and make sure the
> candidate being proposed
>
> in the "log_dir" variable is the actual version you want to release.
>
>
>
> Also, please please please do not overwrite Jenkins failures. Please
> report them instead since
>
> fixing bad merge changes are difficult to fix.
>
>
>
> Thanks a ton
>
> Jess
>
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5505): https://lists.onap.org/g/onap-tsc/message/5505
Mute This Topic: https://lists.onap.org/mt/34506031/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to