News:New Package Submission Workflow Updates!
0
0
Entering edit mode
shepherl 2.8k
@lshep
Last seen 3 days ago
United States

Hello Bioconductor Development Community,

The team has made a significant change to the single package builder process for submitting new packages to Bioconductor.

Previously, when submitting a new package, the process was to submit on github, add a webhook for interactive building on version bump, acceptance, addition to the git.bioconductor.org repository system, and addition to the daily builder manifest.

Now upon submission of your package to github, the preapproval process will involve immediately adding packages to git.bioconductor.org. Subsequent builds of the package during the review process will be triggered by a version bump and push to the upstream repository at git@git.bioconductor.org:packages/<your package="">. Upon acceptance your package will be added to the daily builder manifest for official inclusion in Bioconductor.

The webhook will be deactivated and no longer trigger builds during the review process. Any package that was previously submitted (Before July 7th, 2020) will not have to worry about the new workflow. You can continue your new package review as you have been and we will deactivate your webhook once you are through the submission process. This will only affect packages newly submitted.

Please ask any questions or concerns you may have.

Thank you Lori Shepherd on behalf of the Core Team

new packages submission bioconductor News • 237 views
ADD COMMENT
0
Entering edit mode

Hi shepherl, I have a question about triggering new builds. My recently submitted package had 1 error due to not being subscribed to the bioc-devel mailing list. I have now subscribed and need to trigger a new build. The automated email says that new builds are triggered when pushing changes to the remote host git@git.bioconductor.org:packages/packagename. However, I don't need to make any changes to any package files. Is there a way to trigger a new build without making unnecessary changes and using to the remote host?

ADD REPLY
0
Entering edit mode

We prefer to have the build triggered by a version bump in the description despite the changes not being in the code itself. This practice re-enforces the process of using version bumps for changes in the daily builder to allow new versions to propagate there as well.

ADD REPLY
0
Entering edit mode

Understood. I will do that then. Thank you for the quick response.

ADD REPLY

Login before adding your answer.

Traffic: 238 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6