Sample-Repo

If you got https://report-uri.com working, then you're probably most of the way there.

It's hard to say exactly what's not working for you right now, but a couple of points that might help:

• application/reports+json is the correct content type; the explainer is incorrect. (And thanks, I will fix it.)
• Both the site which triggers the report, and the reporting endpoint need to be on HTTPS; Chrome will remove any insecure endpoints from its cache.
• If the reporting endpoint is on a different origin from your site, then it will need to support CORS: You'll need to handle a CORS preflight request to allow the request to proceed.
• You won't see the reports in the Devtools network tab; Chrome queues those separately in the browser process, and sends them later, outside of any particular browser tab. They are usually sent within a minute, but if sending fails, Chrome will retry a few times before giving up. You can see the network exchange if you export the network logs from chrome://net-export/, and then view them at https://netlog-viewer.appspot.com/

Try enclosing the tags with a single quote

Thanks to the comments, I was able to clone my repository using the https url instead of the ssh url and it worked without the need for token.

It's a Spring boot project, so the pom must have a parent. Simply add these lines at the top of your pom.xml:

Finally turned away from Jasperreports, and I managed to switch the implementation to poi. In this case the Excel configuration could be a bit more flexible based on my needs.

Conclusion: Jasper is not quite capable in creating content included calendar!

You can use the autowrap option for $mdDialog.show.

autoWrap - {boolean=}: Whether or not to automatically wrap the template with a tag if one is not provided. Defaults to true. Can be disabled if you provide a custom dialog directive.

https://material.angularjs.org/latest/api/service/$mdDialog#mddialog-show-optionsorpreset

You are using Docker in Docker (DinD) which is not a recommended CI approach. You should mount your Host's Docker Daemon Socket as volume to the Jenkins container like:

docker container run -v /var/run/docker.sock:/var/run/docker.sock ...

So you can work with images & containers on your host machine rather than in the Jenkins container. Click Here to learn more.

Running the remote worker on a different architecture / OS combination than Bazel itself isn't working yet. We still have a couple of places in Bazel where we inspect the local machine - they were added as temporary measures, but haven't been fixed yet.

Edit: It may work in some cases, especially for platform-independent code (e.g., Java or Scala).

If your build is test-heavy, you could try only running tests remotely with --test_strategy=remote; I'm not sure if the default Jvm configuration will work, though.

If you want to run the entire build remotely, then you need to tell Bazel what kind of machines / OS it's executing on. Right now, that'd require setting --host_cpu, and probably --crosstool_top / --host_crosstool_top to configure a C++ compiler for that platform.

Also, some combinations of platforms are more and some less likely to work. In particular, combining MacOS and Linux or different flavors of Linux are much more likely to work than Windows in any combination.

You are using mockMvc to connect to a WireMock instance. That won't work. Change mockMvc on the consumer side to a restTemplate