I haven't found any clear information about this around.
Is it possible to integrate the sourceforge tracking system for bugs/features with Mylyn?
I've found this page that seems a bit old (indeed the link for downloading the general connector does not work).
Anyone have a clue about this? It is possible to realise such a kind of connection?
Yes with the move of SourceForge to use Allura the configuration on the page you highlighted is outdated.
I posted details on getting the Web Template Connector to work for Allura at http://officefloor.wordpress.com/2012/12/10/allura-sourceforge-mylyn-connector/
The generic connector is now in the Mylyn incubator. Use this download site:
http://download.eclipse.org/mylyn/incubator/3.7 (for Eclipse 3.6, 3.7, 3.8)
Since I wasn't able to get it running – maybe it's because of Eclipse Luna or something else – I slightly modified Daniel's method which partially uses the REST interface:
Basic Configuration
Add the following parameters and appropriate values to the table unter Additional Settings section in the Properties for Task Repository dialog:
project – your so-called UNIX name of the project
tickets – the ticketing application, e.g. bugs or features
bearer_token – you need to set-up a bearer token as described in the Allura documentation
under Advanced Configuration, use:
Task URL: ${serverUrl}/p/${project}/${tickets}/ (the same as in Daniel's method)
New Task URL: ${serverUrl}/p/${project}/${tickets}/new (the same as in Daniel's method)
Query Request URL: ${serverUrl}/rest/p/${project}/${tickets}?access_token=${bearer_token}
Query Pattern: \{"summary":\s*"({Description}.+?)",\s*"ticket_num":\s*({Id}.+?)\}
Milestone query
To query tasks by milestones, use the following parameters in your Edit Query configuration:
add a parameter milestone with e.g. M1 to the parameter table
use the following Query URL: ${serverUrl}/rest/p/${project}/${tickets}/search?q=_milestone%3A${milestone}&access_token=${bearer_token}
Related
I'm trying to write a script that quickly checks if our Jenkins plugins are up to date. I know that this is a built in feature in Jenkins, but for security reasons, our Jenkins instance doesn't have internet access.
I know that I can get a lot of information about a plugin, including version, from:
https://plugins.jenkins.io/<name-of-plugin>
However, I can't get it to return anything other than HTML. I could scrape the HTML for the version number, but if there is a stable API that returns JSON or similar, that would be preferred. I'm pretty sure Jenkins isn't scraping HTML to check for updates, so the API must exist. Does anyone know where it is?
There seem to be two solutions available. I ended up scraping:
https://updates.jenkins.io/download/plugins/<name-of-plugin>
The latest version is always in the second column of the second row, so scraping is trivial. It works well most of the time, but sometimes the connection is refused, which I assume might be due to of the volume of requests sent by the script.
Another option that I found is to download the following JSON file:
https://updates.jenkins.io/current/update-center.actual.json
It is currently 1.7MB and contains information about the latest version of all Jenkins plugins. It also contains meta data like dependencies, which allows your script to validate that all dependencies are satisfied.
Unfortunately I haven't found a way to download JSON for individual plugins, so you either have to scrape HTML for individual plugins or download a massive JSON for all plugins.
Update: I found the API:
https://plugins.jenkins.io/api/plugin/<name-of-plugin>
And I also found the source code and the documentation:
https://github.com/jenkins-infra/plugin-site-api
I used to use buildbot eight before, where i was able to access my html artifacts generated by tests by just using URL:
<server>:<port>/path_to_resource,
where path to resource was in <preifx>/master/public_html.
I can't access it in buildbot 0.9.10 as I get resource not found.
I wonder if there is an option what would allow me to access my html files from a browser?
This feature was removed in 0.9.0.
An issue asks for the implementation of a plugin implementing this feature. It is still open currently with no assignee.
I have not found any other solution. I would be very interested if a solution was found.
In previous versions of AEM, certainly in CQ 5.6 and AEM 6.0, it was possible to tail the error logs over HTTP, without connecting to the server over SSH.
For example, I could get the last 1000 lines from the error log of my AEM author instance by calling:
http://localhost:4502/bin/crxde/logs?tail=1000
This seems to no longer be possible in AEM 6.2, this path does not resolve to anything.
Is there another way I could still tail the log over HTTP?
A colleague answered this question for me on a chat so I'm putting it here to make it easier to find in the future.
There's now a neat utility in the OSGi console that allows one to view the logs as well as configure the various loggers. You can find it at http://localhost:4502/system/console/slinglog
The Appender tab provides links to the various log files that can be used to load logs over HTTP.
Here's an example request it makes:
http://localhost:4502/system/console/slinglog/tailer.txt?tail=1000&name=%2Flogs%2Ferror.log
As you can see, both the log file name and the tail parameter can be specified. You can also use grep with both simple phrases and regular expressions.
This is a built-in feature of Apache Sling.
In addition FYI, you can also find the status-slinglogs where you can perform log file downloads in a zip and logger actions in a txt to your local at /system/console/status-slinglogs
http://localhost:4502/system/console/status-slinglogs
and the direct urls for the downloading these zip files are as below
http://localhost:4502/system/console/status-slinglogs.zip
http://localhost:4502/system/console/status-slinglogs/configuration-status-20170126-183246.zip (where as 20170126-183246 is and time stamp)
You should not be looking at log files via CRXDE lite.
log files in 6.2 are project specific - better to open them from a text editor.
see attached screenshot.
Hope this helps!
Regards,
Prince
You can curl the log with e.g.:
curl -u admin:admin 'http://localhost:4502/system/console/slinglog/tailer.txt?tail=4000&name=%2Flogs%2Ferror.log'
where 4000 is the number of lines you want to get.
I recently wrote a tool named "Log Tailer Plus" to solve exactly this problem. It's entirely free/open source - Take a look at a post describing usage here : https://blogs.perficientdigital.com/2019/05/14/introducing-aem-logtailerplus/
TLDR; You can grab an AEM package from here ( https://github.com/prftryan/LogTailerPlus ) install it to your machine, and access via http://localhost:4502/log-tailer-plus (if local) or http://server:port/log-tailer-plus
This tool will allow you to follow any number of logs at once by leveraging the out of the box logging endpoint(/system/console/tailer ) as well as dynamically checking active OSGI Logging Logger configurations. Currently, highlighting is supported, but only for relatively standard logging patterns (it's done via regex).
This is a new release, works on AEM 6.2+. Enjoy
I thought this was a simple question, and still nothing works.
My first use-case is that the IDEA 15 (Community) appears to NOT have a repository configured. The *Plugins" tab in the Settings window / dialogue supports three operation aside from clicking on a plugin.:
A button for [Install JetBrains plugins] ... This seems to be things downloaded with the installer or updates;
A [Browse repositories plugins] button ... which contains an "empty" list Further this dialogue contains two buttons for:
A [Manage repositories]
[HTTP proxy settings] - Proxy configuration / setup
An [Install plugins from disk] button ... which does what it says ;-)
This question to ask is, what URL do I need to put into that:
* The [Manage repositories]
... list because the clean install had "nada" in that list.
The list of JetBrains plugins isn't the same as the list on the plugins repository web page:
https://plugins.jetbrains.com/
In fact IDEA help pages recommend using the JetBrains repository... They do not seem to want to let one know the URL.
Also, what is the "Community" plugins URL? At the very least I'd like to verify that/IF the JetBrains plugin-list is updating (as there's no "update list" option to be seen).
Weird huh?
I had the same problem while using the Community edition and trying to install the lombok plugin. Setting the HTTP Proxy to "Auto-detect proxy settings" resolved it for me.
It's under browse repositories -> HTTP Proxy Settings -> HTTP Proxy -> Auto detect proxy settings.
The [Manage repositories] list should be empty, unless you have some private plugins repository.
A [Browse repositories plugins] button should show you all the plugins, if not then check your firewall or proxy settings, or click on the Reload button.
[
I don't know the specific URL, either, but Meo's answer is correct in saying that there's no need to add it manually. It sounds like you're confused by the difference between the list you see on the site and the list you see in IDEA CE.
The reason for the difference isn't a missing URL at all, but rather that many of the plugins listed on the site are not enabled for the Community Edition, so it doesn't display them. The PHP plugin at https://plugins.jetbrains.com/plugin/6610 is an example. While that page doesn't make it clear that it requires the Ultimate Edition, you can find out by scrolling down to the Updates list and clicking the (latest) version number. There you'll find a Supported Products list, where the Community Edition is listed as being incompatible because the plugin requires the "ultimate" module (a module that is only included in IDEA Ultimate Edition).
If Browse Repositories... is empty, perhaps something happened with your version of Android studio?
If you're on the Canary channel your build might be too advanced for plugins, for instance. At least, that's what I think my issue was, as I switched to another (older) instance and everything was fine after this
I felt a bit stupid upon realising this!!
I had the exact same issue on my Android Studio 3.6.1 but a quick restart after looking for solutions turned out to be the way to go.
I have gone through the http://docs.codehaus.org/display/SONAR/Developing+Plugins but unfortunately it does not give detailed steps.
Can some one help me understand how I need to call a code review tool that uses ANTLR for parsing the code files and then capture the output into Sonar
As well how do I start maintaining the rules based on XPATH for my code analysis tool on Sonar as it is done for Java/Javascript?
A good starting point is to have a look at the code of existing plugins:
http://github.com/sonarqubecommunity
I suggest that you use the sonar dev mailing list : dev at sonar dot codehaus dot org.
Developing a Sonar plugin can't simply covered by a "guide"...