Setting up automated plugin release

[Marit M]

Hi,

 

I have followed the steps described in https://www.jenkins.io/doc/developer/publishing/releasing-cd/.

But I can’t seem to pass the validate job on the cd.yml

https://github.com/jenkinsci/bmc-cfa-plugin/runs/4594497623?check_suite_focus=true

 

It seems like “Check interesting categories” fails.

 

Any idea?

 

Thanks,

Marit.

[Marit M]

I managed to fix that by applying a label to the PR.

ב-יום שלישי, 21 בדצמבר 2021 בשעה 16:53:51 UTC+2, ‪Marit M‬‏ כתב/ה:

[Tim Jacomb]

this should fix your current issue: https://github.com/jenkinsci/bmc-cfa-plugin/pull/11

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/40b6db23-bf09-454f-a192-7e0225fb028an%40googlegroups.com.

[Marit M]

 Now I get an error on the release job regarding incrementals :

[WARNING] The requested profile "consume-incrementals" could not be activated because it does not exist.

201++ mvn -B -ntp -Dset.changelist -Dexpression=project.version -q -DforceStdout help:evaluate

202Error: on='[ERROR] Make sure `git status -s` is empty before using -Dset.changelist

https://github.com/jenkinsci/bmc-cfa-plugin/runs/4605825016?check_suite_focus=true

ב-יום רביעי, 22 בדצמבר 2021 בשעה 12:30:32 UTC+2, timja...@gmail.com כתב/ה:

[Jesse Glick]

On Wed, Dec 22, 2021 at 6:10 AM Marit M <mar...@gmail.com> wrote:

202Error: on='[ERROR] Make sure `git status -s` is empty before using -Dset.changelist

https://github.com/jenkinsci/bmc-cfa-plugin/pull/12 

[Marit M]

Now I'm getting wrong-check on validate job, what does that mean?

It seems to fail here:

if [ "$(jq -r .check_run.name < $GITHUB_EVENT_PATH)" \!= "$NAME" ]

then

outputResult wrong-check 1

ב-יום רביעי, 22 בדצמבר 2021 בשעה 16:24:00 UTC+2, ‪Jesse Glick‬‏ כתב/ה:

[Tim Jacomb]

There's quite a few checks that are run as part of warnings-ng and junit.

Only the main check 'Jenkins' matters for release.

Which wasn't finished when you sent this email, https://github.com/jenkinsci/bmc-cfa-plugin/runs/4616176655?check_suite_focus=true passed

and it's been released now https://github.com/jenkinsci/bmc-cfa-plugin/releases/tag/1.0.0060.v9bc9bf8fa267

--

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/09c23105-46ed-4116-bf7c-5179c63c316en%40googlegroups.com.

[Marit M]

Yeah, I saw it was finally released :-)!

Thanks for the assistance!

 I still need to figure out the how to format the numbers, and can I delete a release, will it be deleted from https://plugins.jenkins.io/ as well?

ב-יום חמישי, 23 בדצמבר 2021 בשעה 11:12:04 UTC+2, timja...@gmail.com כתב/ה:

[Jesse Glick]

https://github.com/jenkinsci/bmc-cfa-plugin/pull/15 ought to fix the version format I think. 61.vb33105387180 etc.

You cannot easily delete a release, but there is not generally any need to.

[Marit M]

I removed the SNAPSHOT to eliminate the timestamp.

How do I set the latest version? 

For some reason it sets the SNAPSHOT release as latest.

Thanks,

Marit.

ב-יום חמישי, 23 בדצמבר 2021 בשעה 16:32:23 UTC+2, ‪Jesse Glick‬‏ כתב/ה:

[Marit M]

And I don't see the incrementals checks in the PR.

How do I fix that and enable the incrementals? 

ב-יום שישי, 24 בדצמבר 2021 בשעה 06:22:29 UTC+2, ‪Marit M‬‏ כתב/ה:

[Marit M]

[WARNING] The requested profile "consume-incrementals" could not be activated because it does not exist.

201[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project bmc-cfa: Failed to deploy artifacts: Could not transfer artifact com.bmc.ims:bmc-cfa:hpi:1.0.00 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): authorization failed for https://repo.jenkins-ci.org/releases/com/bmc/ims/bmc-cfa/1.0.00/bmc-cfa-1.0.00.hpi, status: 403 Forbidden -> [Help 1]

202[ERROR]

203[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

204[ERROR] Re-run Maven using the -X switch to enable full debug logging.

205[ERROR]

206[ERROR] For more information about the errors and possible solutions, please read the following articles:

207[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

208Error: Process completed with exit code 1.

ב-יום שישי, 24 בדצמבר 2021 בשעה 06:29:27 UTC+2, ‪Marit M‬‏ כתב/ה:

[Marit M]

I can see that version 1.0.00 exist in https://repo.jenkins-ci.org/ui/repos/tree/General/releases/com/bmc/ims/bmc-cfa/1.0.00.

How do I make it the latest one?

Thanks,

Marit.

ב-יום שישי, 24 בדצמבר 2021 בשעה 06:57:07 UTC+2, ‪Marit M‬‏ כתב/ה:

[Gavin Mogan]

Why do you want that one to be the latest?
According to https://github.com/jenkinsci/bmc-cfa-plugin/releases your
latest version is 62 which matches updatecenter
$ curl -qLs https://updates.jenkins.io/update-center.actual.json | jq
'.plugins["bmc-cfa"]["version"]'
"62.v6b7af476b7f8"

So I'm not sure what more you want, it seems to be working fine

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/43e8dfbd-55d0-4877-8c5d-e55f79ecc308n%40googlegroups.com.

[Marit M]

I didn't meant to create that version format, what do I need to do to format it as: 1.0.00?

ב-יום שני, 27 בדצמבר 2021 בשעה 11:41:44 UTC+2, ga...@gavinmogan.com כתב/ה:

[Gavin Mogan]

I'll admit, I'm still confused by your request.

If you enable CD, you'll have releases with a sha (ish?) on the end of
it. If you just want the version number, don't use CD. At this point
since version 62 is released to artifactory, you won't be able to have
a version below 62 as they will all get parsed as older releases.

I tried to look at the git history of your repo, but its all over the
place, it looks like you un-did a bunch of jesse's fixes.

Can you clearly state what your desired goals are instead of randomly
changing things and then panicking when its not doing what your
expecting it to work.

Gavin

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cac1551e-f2be-4c65-9b23-2d7ba5f88eb8n%40googlegroups.com.

[Marit M]

Sorry for the confusion, now I understand that Incrementals appends a commit number, plus a SHA, to version numbers.

I'll stick with this versioning format and revert my changes.

Thanks,

Marit.

ב-יום שני, 27 בדצמבר 2021 בשעה 20:13:57 UTC+2, ga...@gavinmogan.com כתב/ה:

[Jesse Glick]

On Tue, Dec 28, 2021 at 5:50 AM Marit M <mar...@gmail.com> wrote:

now I understand that Incrementals appends a commit number, plus a SHA, to version numbers.

https://www.jenkins.io/doc/developer/publishing/releasing-cd/#pom-file-modifications says so; is there a way we could make this more prominent? 

[Ullrich Hafner]

Maybe you can inline the existing Abstract form the JEP before the section ‚Prerequisites‘? And add an example that shows the old and new versions in the abstract as well? 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr04RcPDC8UQh5xKV2fQ1coQThNjR7AxSrnQ7Veay4rq7g%40mail.gmail.com.