[Bioc-devel] Trigger a new build after version bump

Jakob Theorell j@kob@theore|| @end|ng |rom ndcn@ox@@c@uk
Tue Dec 17 07:35:49 CET 2019

Dear Ahmed,
I am not in the core team, but I still wonder: how long have you waited since you pushed? During the review process you get an immediate update of the package upon push with a version bump, but with accepted packages it takes 24-48 hours for the changes to trickle through to the build report. And you have to go in and check the build reports yourself on the BioConductor sites related to the release and devel branches.
Best regards
Jakob Theorell, MD/PhD
Autoimmune Neurology Group
Nuffield Department of Clinical Neurosciences
University of Oxford

From: Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of Ahmed Metwally <ametwall using stanford.edu>
Sent: 17 December 2019 02:34
To: bioc-devel using r-project.org <bioc-devel using r-project.org>
Subject: [Bioc-devel] Trigger a new build after version bump

Dear Bioc devel team,

OmicsLonDA package is failing to build on release and devel branches:

I have fixed the issue and pushed the changes to RELEASE_3_10, and dev-master branch. I bumped the package version on the RELEASE_3_10 to v1.2.1 instead of v1.2.0. I did the same for the dev branch, bumped the version to v1.3.3 instead of v1.3.0. I was following instructions listed here: https://bioconductor.org/developers/how-to/git/sync-existing-repositories/

However, my changes didn't trigger a new build. In the past, when I was submitting the OmicsLonDA to Bioc, whenever I do version bump, I receive an email says that I successfully triggered a new build. This time I didn't receive any emails. Also, the build error and data don't change in the above-mentioned URLs to reflect a new build!

Please let me know what I'm missing here.

        [[alternative HTML version deleted]]

Bioc-devel using r-project.org mailing list

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list