This set up is not possible in Bioconductor.
I suggest that you explore the use of 'mocks' so that your code thinks, during
testing and examples, that it is querying an elasticsearch server, but is
actually checking that it can send the appropriate message / interpret the
expected response --
Since you are able to push, please issue a version bump 0.99.1 on your package
DESCRIPTION file.
Only then we can confirm if something is broken.
Nitesh
> On Jul 16, 2020, at 10:47 AM, Shepherd, Lori
> wrote:
>
> Thank you for your inquiry. We have experienced some issues adding
>
Thank you for your inquiry. We have experienced some issues adding credentials
for new packages. We are investigating and should have a solution shortly. We
will comment on your open issue on the tracker when the issue is resolved. We
apologize for any inconvenience this has caused.
There was no version bump.
To trigger a build you have bump the version.
Best,
Nitesh
> On Jul 16, 2020, at 10:37 AM, Spiro Stilianoudakis
> wrote:
>
> Hello Bioconductor,
>
> I submitted a new package titled preciseTAD, for review. There were errors
> in the build results. I have
Hello Bioconductor,
I submitted a new package titled preciseTAD, for review. There were errors
in the build results. I have addressed them and I went through the steps to
add a remote pointing to g...@git.bioconductor.org:packages/preciseTAD. I
successfully pushed the results upstream, but it
Hello Bioconductor,
I would like to submit my software package to Bioconductor and I have some
questions.
My package strongly depends on ElasticSearch (ES,
https://www.elastic.co/elasticsearch) as database and search engine. It sends
data to, and retrieves data from ES.
Thus, a big part of
