Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RELEASE] New release for 2024-12-06 #4066

Closed
12 tasks done
gounthar opened this issue Dec 5, 2024 · 11 comments
Closed
12 tasks done

[RELEASE] New release for 2024-12-06 #4066

gounthar opened this issue Dec 5, 2024 · 11 comments
Assignees
Labels
release Used for issues about BOM releases

Comments

@gounthar
Copy link
Contributor

gounthar commented Dec 5, 2024

A new release is being scheduled.
Release manager: @gounthar

Note

For tasks that don't have a specific script, i.e. tasks 2, 4, 5, 7, and 10, run ./bom-release-issue-complete-task.sh <task number> to check the box off without having to manually edit the issue.

Release progress

  • 1. makes sure the CRON expression to run the job is appropriate for the release date
  • 2. run ./bom-lock-master.sh before the job runs
  • 3. wait to verify that job started at ci.jenkins.io
  • 4. run ./bom-release-issue-job-running.sh <buildNumber>
    • Example: ./bom-release-issue-job-running.sh 1234
  • 5. wait for build to make it through the prep stage then (typically) take a 1.5-2 hr break
  • 6. (LOOP) if there are any failures, fix until everything is successful
  • 7. run ./bom-run-cd-workflow.sh
    • wait for the release process to complete
    • this takes 7-8 minutes
  • 8. manually edit the auto-generated release notes
    • remove <!-- Optional: add a release summary here -->
    • remove <details>
    • remove <summary>XYZ changes</summary>
    • remove </details>
  • 9. run ./bom-release-issue-add-release-comment.sh
  • 10. run ./bom-unlock-master.sh
  • 11. verify that the branch is unlocked
  • 12. run ./bom-release-issue-close.sh
@gounthar gounthar added the release Used for issues about BOM releases label Dec 5, 2024
@gounthar gounthar self-assigned this Dec 5, 2024
@gounthar gounthar pinned this issue Dec 5, 2024
@gounthar
Copy link
Contributor Author

gounthar commented Dec 5, 2024

The local build was successful:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  08:21 min
[INFO] Finished at: 2024-12-05T11:48:02+01:00
[INFO] ------------------------------------------------------------------------

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

We're seeing some errors with a 403 when downloading artifacts. 🤷

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

I still have some problems with retrieving some dependencies:

[ERROR] Failed to execute goal on project badge: Could not resolve dependencies for project org.jenkins-ci.plugins:badge:hpi:2.5
12:09:03  [ERROR] dependency: com.fasterxml.woodstox:woodstox-core:jar:6.6.1 (test)
12:09:03  [ERROR] 	Could not transfer artifact com.fasterxml.woodstox:woodstox-core:jar:6.6.1 from/to azure-aks-internal (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): Premature end of Content-Length delimited message body (expected: 1,549,934; received: 1,237,084)
12:09:03  [ERROR] -> [Help 1]
12:09:03  org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project badge: Could not resolve dependencies for project org.jenkins-ci.plugins:badge:hpi:2.5
12:09:03  dependency: com.fasterxml.woodstox:woodstox-core:jar:6.6.1 (test)
12:09:03  	Could not transfer artifact com.fasterxml.woodstox:woodstox-core:jar:6.6.1 from/to azure-aks-internal (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): Premature end of Content-Length delimited message body (expected: 1,549,934; received: 1,237,084)
12:09:03  
12:09:03      at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)
12:09:03      at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:136)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:355)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:313)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
12:09:03      at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
12:09:03      at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
12:09:03      at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
12:09:03      at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
12:09:03      at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
12:09:03      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
12:09:03      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
12:09:03      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
12:09:03      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)12:09:03      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
12:09:03      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
12:09:03      at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
12:09:03      at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
12:09:03      at java.lang.reflect.Method.invoke (Method.java:580)
12:09:03      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
12:09:03      at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
12:09:03      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
12:09:03      at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
12:09:03  Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.jenkins-ci.plugins:badge:hpi:2.5

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

Relaunching.
https://ci.jenkins.io/job/Tools/job/bom/job/master/3542/

We still have some errors with 403.

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

And it failed, again. 🙄
This time, with the artifact caching proxy:

[ERROR] Error executing Maven.
17:25:18  org.apache.maven.cli.internal.ExtensionResolutionException: Extension io.jenkins.tools.incrementals:git-changelist-maven-extension:1.7 or one of its dependencies could not be resolved: Plugin io.jenkins.tools.incrementals:git-changelist-maven-extension:1.7 or one of its dependencies could not be resolved:
17:25:18  	Could not transfer artifact org.eclipse.jgit:org.eclipse.jgit:jar:6.6.0.202305301015-r from/to azure-aks-internal (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): Premature end of Content-Length delimited message body (expected: 3,104,830; received: 1,235,341)
17:25:18  	org.eclipse.jgit:org.eclipse.jgit:jar:6.6.0.202305301015-r failed to transfer from http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of azure-aks-internal has elapsed or updates are forced. Original error: Could not transfer artifact org.eclipse.jgit:org.eclipse.jgit:jar:6.6.0.202305301015-r from/to azure-aks-internal (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): Premature end of Content-Length delimited message body (expected: 3,104,830; received: 1,235,341)
17:25:18  	org.eclipse.jgit:org.eclipse.jgit:jar:6.6.0.202305301015-r failed to transfer from http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of azure-aks-internal has elapsed or updates are forced. Original error: Could not transfer artifact org.eclipse.jgit:org.eclipse.jgit:jar:6.6.0.202305301015-r from/to azure-aks-internal (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): Premature end of Content-Length delimited message body (expected: 3,104,830; received: 1,235,341)

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

The last one worked.

@gounthar
Copy link
Contributor Author

gounthar commented Dec 6, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Used for issues about BOM releases
Projects
None yet
Development

No branches or pull requests

1 participant