Describe the bug
We lost our Jenkins instance that managed all content stored on BP.org. This included new releases and was the primary source for all tarballs. This is an impediment to properly shipping a new release (e.g. 28.4) at this time.
Re-implement the Jenkins CI using GitHub Actions or a similar stack.
Version-Release number
All
To Reproduce
Steps to reproduce the behavior:
Try to make a new release
Actual behavior
Nothing happens really.
**Expected behavior
Artifacts will be built automatically and stored properly in BP.org.
Describe the bug
We lost our Jenkins instance that managed all content stored on BP.org. This included new releases and was the primary source for all tarballs. This is an impediment to properly shipping a new release (e.g. 28.4) at this time.
Re-implement the Jenkins CI using GitHub Actions or a similar stack.
Version-Release number
All
To Reproduce
Steps to reproduce the behavior:
Actual behavior
Nothing happens really.
**Expected behavior
Artifacts will be built automatically and stored properly in BP.org.