Hi Oleg,
i'm also interested! can you please add following repo?
- https://github.com/jenkinsci/performance-signature-dynatrace-plugin
Regards,
Raphael
Am Montag, 4. März 2019 15:40:57 UTC+1 schrieb Oleg Nenashev:
>
> Hi Baptiste, the requested repositories have been added.
>
> @All I also
Hello,
i'm experiencing the same problem. I released a new version of the
Performance-Signature-* plugins but it still hasn't shown up on the update
center.
The release is available via
repo.jenkins-ci.org:
https://repo.jenkins-ci.org/releases/de/tsystems/mms/apm/performance-signature-dynatrac
Hello,
is there any new activity with this plugin / repository?
Regards,
Raphael
Am Dienstag, 16. Mai 2017 20:20:11 UTC+2 schrieb Kevin Phillips:
>
> I'd like to offer my assistance with the Remote Parameterized Trigger
> plugin project. There are a handful of issues and merge requests reported
Thanks for doing all the background work!
BTW: Can we adjust the links from https://twitter.com/jenkins_release to
use the new plugins.jenkins.io page?
Am Dienstag, 7. März 2017 23:12:22 UTC+1 schrieb Daniel Beck:
>
> Hi everyone,
>
> I pushed a change to the update center today.
>
> TLDR: Wik
You can just use something like this:
curl -s -X POST --user $CREDS -H "$CRUMB"
$SERVER/job/$JOB/lastBuild/input/FinishRecording/proceedEmpty
(the url is shown in console output or stage view)
the corresponding pipeline step :
input id: 'FinishRecording', message: 'Proceed?'
https://jenkins.io/
We pushed our changes in our repo
<https://github.com/T-Systems-MMS/perfsig-jenkins/blob/master/pom.xml#L28>.
Any update to this?
Kind regards,
Raphael
Am Donnerstag, 28. Januar 2016 14:07:06 UTC+1 schrieb Raphael Pionke:
>
> Hey Daniel,
>
> Sorry about the delay, we've
nnerstag, 17. Dezember 2015 16:44:57 UTC+1 schrieb Daniel Beck:
>
> The plugin ID should ideally be close to the display name (as it's used
> e.g. in JIRA as component), and obvious about what it is. So 'dynatrace'
> should be in there.
>
> On 17.12.2015,
c. It would be great to get his
>> feedback before going forward.
>>
>> Even if we go forward with a new plugin:
>> * performance-signature is vague IMHO
>> * If the plugin is dynatrace-specific, I would prefer to see "dynatrace"
>> in its name
>
Any update to this?
Kind regards,
Raphael
Am Dienstag, 22. September 2015 11:09:59 UTC+2 schrieb Raphael Pionke:
>
> Hi Oleg,
>
> we know the other Dynatrace plugin and after a long evaluation, we have
> decided
> to developed a new plugin with (good) serious reasons
>
plugin for Dynatrace, which does the similar thing.
> https://wiki.jenkins-ci.org/display/JENKINS/Dynatrace+Plugin
>
> What is the difference between plugins? Would it be possible to merge the
> functionality?
>
> вторник, 15 сентября 2015 г., 15:00:17 UTC+3 пользователь R
Hi,
this plugin fetches performance values from Dynatrace XML Dashboards during
a build and evaluates and compares the result with previous builds and
non-functional requirements. This plugin uses user-specified XML Dashboards
and PDF detail Reports. Additionally this plugin adds several build
11 matches
Mail list logo