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.

Sign up for GitHub

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

Jump to bottom

[RELEASE] New release for 2025-01-30 #4346

Closed
12 tasks done
alecharp opened this issue Jan 30, 2025 · 9 comments
Closed
12 tasks done

[RELEASE] New release for 2025-01-30 #4346

alecharp opened this issue Jan 30, 2025 · 9 comments
Assignees
@alecharp
Labels
release Used for issues about BOM releases

Comments

@alecharp
Copy link
Member

alecharp commented Jan 30, 2025 •
edited
Loading

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

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
@alecharp alecharp added the release Used for issues about BOM releases label Jan 30, 2025
@alecharp alecharp self-assigned this Jan 30, 2025
@alecharp alecharp pinned this issue Jan 30, 2025
@alecharp
Copy link
Member Author

https://ci.jenkins.io/job/Tools/job/bom/job/master/3820/

@alecharp
Copy link
Member Author

The first build failed due to artifact caching issue while testing run-condition plugin on 2.492.x line.

@alecharp
Copy link
Member Author

https://ci.jenkins.io/job/Tools/job/bom/job/master/3822/

@alecharp
Copy link
Member Author

alecharp commented Jan 30, 2025 •
edited
Loading

The second build failed because the artifacts caching reporting 403 when accessing stapler (for authentication-tokens plugin) and spring-core (for commons-lang3-api plugin).

@alecharp
Copy link
Member Author

https://ci.jenkins.io/job/Tools/job/bom/job/master/3824/

@alecharp
Copy link
Member Author

https://ci.jenkins.io/job/Tools/job/bom/job/master/3825/

@alecharp
Copy link
Member Author

alecharp commented Jan 30, 2025 •
edited
Loading

The third build also failed with 403 while retrieving artefacts for at least one plugin testing.
Thanks to @dduportal, a new build was triggered without having to change the Jenkinsfile.

This artefact caching issue is being investigating in jenkins-infra/helpdesk#4442.

@alecharp
Copy link
Member Author

https://ci.jenkins.io/job/Tools/job/bom/job/master/3826/

@alecharp
Copy link
Member Author

New release: https://github.com/jenkinsci/bom/releases/tag/4051.v78dce3ce8b_d6

@alecharp alecharp unpinned this issue Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alecharp alecharp

Labels
release Used for issues about BOM releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alecharp