[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Ulli Hafner updated JENKINS-50084 Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Ulli Hafner Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag commented on JENKINS-50084 Re: Integration Test for ReferenceFinder 2 Bugs: 1.) Bei MustBeOverallSuccess false ignoriert er alle Failures obwohl die Überprüfung der IssueRecorder ein Success zurück liefert. BuildHistory.java Z. 104 isBetter -> isBetterOrEqual 2.) Wenn ein ReferenceJob angegeben ist, nimmt er immer den aktuellen (baseline) als Reference und nicht abhängig vom Buildstatus (ignore Previous Result hat dort keinen Einfluss) Siehe: OtherJobReferenceFinder.java Z. 47 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Ulli Hafner commented on JENKINS-50084 Re: Integration Test for ReferenceFinder recorder.setUnstableTotalAll(0); deaktiviert das QualityGate. Eine 1 aktiviert es bei mindestens einer Warnung. Issues fixed geht am einfachsten, durch Duplizieren der Datei und löschen einiger Warnungen. Dann den zweiten Build auf die andere Datei loslassen. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Arne Schöntag edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Wenn ich folgendes laufen lasse:{code:java}FreeStyleProject project = createJobWithWorkspaceFile(jobName, "eclipse.txt");IssuesRecorder recorder = enableWarnings(project, publisher -> {publisher.setUnstableTotalAll(7);});AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE);assertThat(result).hasTotalSize(8);assertThat(result).hasOverallResult(Result.UNSTABLE);recorder.setUnstableTotalAll(0);result = scheduleBuildAndAssertStatus(project, Result.SUCCESS);assertThat(result).hasOverallResult(Result.UNSTABLE);assertThat(result).hasNewSize(0);{code}bekomme ich ein SUCCESS build beim zweiten Mal, dass 8 Issues hat. Warum kommt da ein SUCCESS zurück, obwohl der vorherige Build UNSTABLE (ignoreAnalysisResult ist standardmäßig false) war? Das assertThat danach schlägt demnach fehl.Wie kann ich noch die Issues "fixen", dass beim zweiten build weniger vorhanden sind?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Arne Schöntag commented on JENKINS-50084
Re: Integration Test for ReferenceFinder
Wenn ich folgendes laufen lasse:
FreeStyleProject project = createJobWithWorkspaceFile(jobName, "eclipse.txt");
IssuesRecorder recorder = enableWarnings(project, publisher -> {
publisher.setUnstableTotalAll(7);
});
AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE);
assertThat(result).hasTotalSize(8);
assertThat(result).hasOverallResult(Result.UNSTABLE);
recorder.setUnstableTotalAll(0);
result = scheduleBuildAndAssertStatus(project, Result.SUCCESS);
assertThat(result).hasOverallResult(Result.UNSTABLE);
assertThat(result).hasNewSize(0);
bekomme ich ein SUCCESS build beim zweiten Mal, dass 8 Issues hat. Warum kommt da ein SUCCESS zurück, obwohl der vorherige Build UNSTABLE (ignoreAnalysisResult ist standardmäßig false) war? Das assertThat danach schlägt demnach fehl. Wie kann ich noch die Issues "fixen", dass beim zweiten build weniger vorhanden sind?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-iss
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Der Reference Job hat nichts mit dem Bauen zu tun, das muss im Recorder gesetzt werden.Das Setzen können Sie analog zu einem der bestehenden Tests machen. Diese Parameter im Test am einfachsten als Lambda übergeben (siehe {{publisher}} Variable unten):{code}/** * Sets the UNSTABLE threshold to 8 and parse a file that contains exactly 8 warnings: the build should be * unstable. */@Testpublic void shouldCreateUnstableResult() \ { FreeStyleProject project = createJobWithWorkspaceFile("eclipse.txt"); enableWarnings(project, publisher -> publisher.setUnstableTotalAll(7)); AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE); assertThat(result).hasTotalSize(8); assertThat(result).hasStatus(Status.WARNING); HtmlPage page = getWebPage(result); assertThat(page.getElementsByIdAndOrName("statistics")).hasSize(1);} {code}Welche Setter Sie Nutzen können, sehen Sie in der Klasse {{IssuesRecorder}}.Folgende drei Setter sind verfügbar:{code}/** * If \ {@code true} then the result of the previous analysis run is ignored when searching for the reference, * otherwise the result of the static analysis reference must be \ {@link Result#SUCCESS}. * * @param ignoreAnalysisResult * if \ {@code true} then the previous build is always used */@DataBoundSetterpublic void setIgnoreAnalysisResult(final boolean ignoreAnalysisResult) \ { this.ignoreAnalysisResult = ignoreAnalysisResult;} /** * If \ {@code true} then only runs with an overall result of \ {@link Result#SUCCESS} are considered as a reference, * otherwise every run that contains results of the same static analysis configuration is considered. * * @param overallResultMustBeSuccess * if \ {@code true} then a stable build is used as reference */@DataBoundSetterpublic void setOverallResultMustBeSuccess(final boolean overallResultMustBeSuccess) \ { this.overallResultMustBeSuccess = overallResultMustBeSuccess;}/** * Sets the reference job to get the results for the issue difference computation. * * @param referenceJobName * the name of reference job */@DataBoundSetterpublic void setReferenceJobName(final String referenceJobName) \ { if (NO_REFERENCE_JOB.equals(referenceJobName)) \ { this.referenceJobName = StringUtils.EMPTY; } this.referenceJobName = referenceJobName;} {code}
Add Comment
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Der Reference Job hat nichts mit dem Bauen zu tun, das muss im Recorder gesetzt werden.Das Setzen können Sie analog zu einem der bestehenden Tests machen. Diese Parameter im Test am einfachsten als Lambda übergeben (siehe publisher {{ Variable publisher }} Variable unten):{code}/** * Sets the UNSTABLE threshold to 8 and parse a file that contains exactly 8 warnings: the build should be * unstable. */@Testpublic void shouldCreateUnstableResult() \{ FreeStyleProject project = createJobWithWorkspaceFile("eclipse.txt"); enableWarnings(project, publisher -> publisher.setUnstableTotalAll(7)); AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE); assertThat(result).hasTotalSize(8); assertThat(result).hasStatus(Status.WARNING); HtmlPage page = getWebPage(result); assertThat(page.getElementsByIdAndOrName("statistics")).hasSize(1);} {code}Welche Setter Sie Nutzen können, sehen Sie in der Klasse {{IssuesRecorder}}.Folgende drei Setter sind verfügbar:{code}/** * If \{@code true} then the result of the previous analysis run is ignored when searching for the reference, * otherwise the result of the static analysis reference must be \{@link Result#SUCCESS}. * * @param ignoreAnalysisResult * if \{@code true} then the previous build is always used */@DataBoundSetterpublic void setIgnoreAnalysisResult(final boolean ignoreAnalysisResult) \{ this.ignoreAnalysisResult = ignoreAnalysisResult;}/** * If \{@code true} then only runs with an overall result of \{@link Result#SUCCESS} are considered as a reference, * otherwise every run that contains results of the same static analysis configuration is considered. * * @param overallResultMustBeSuccess * if \{@code true} then a stable build is used as reference */@DataBoundSetterpublic void setOverallResultMustBeSuccess(final boolean overallResultMustBeSuccess) \{ this.overallResultMustBeSuccess = overallResultMustBeSuccess;}/** * Sets the reference job to get the results for the issue difference computation. * * @param referenceJobName * the name of reference job */@DataBoundSetterpublic void setReferenceJobName(final String referenceJobName) \{ if (NO_REFERENCE_JOB.equals(referenceJobName)) \{ this.referenceJobName = StringUtils.EMPTY; } this.referenceJobName = referenceJobName;}{code}
Add Comment
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Der Reference Job hat nichts mit dem Bauen zu tun, das muss im Recorder gesetzt werden.Das Setzen können Sie analog zu einem der bestehenden Tests machen. Diese Parameter im Test am einfachsten als Lambda übergeben (siehe publisher {{Variable}} unten) :{code}/** * Sets the UNSTABLE threshold to 8 and parse a file that contains exactly 8 warnings: the build should be * unstable. */@Testpublic void shouldCreateUnstableResult() \{ FreeStyleProject project = createJobWithWorkspaceFile("eclipse.txt"); enableWarnings(project, publisher -> publisher.setUnstableTotalAll(7)); AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE); assertThat(result).hasTotalSize(8); assertThat(result).hasStatus(Status.WARNING); HtmlPage page = getWebPage(result); assertThat(page.getElementsByIdAndOrName("statistics")).hasSize(1);} {code}Welche Setter Sie Nutzen können, sehen Sie in der Klasse {{IssuesRecorder}}.Folgende drei Setter sind verfügbar:{code}/** * If \{@code true} then the result of the previous analysis run is ignored when searching for the reference, * otherwise the result of the static analysis reference must be \{@link Result#SUCCESS}. * * @param ignoreAnalysisResult * if \{@code true} then the previous build is always used */@DataBoundSetterpublic void setIgnoreAnalysisResult(final boolean ignoreAnalysisResult) \{ this.ignoreAnalysisResult = ignoreAnalysisResult;}/** * If \{@code true} then only runs with an overall result of \{@link Result#SUCCESS} are considered as a reference, * otherwise every run that contains results of the same static analysis configuration is considered. * * @param overallResultMustBeSuccess * if \{@code true} then a stable build is used as reference */@DataBoundSetterpublic void setOverallResultMustBeSuccess(final boolean overallResultMustBeSuccess) \{ this.overallResultMustBeSuccess = overallResultMustBeSuccess;}/** * Sets the reference job to get the results for the issue difference computation. * * @param referenceJobName * the name of reference job */@DataBoundSetterpublic void setReferenceJobName(final String referenceJobName) \{ if (NO_REFERENCE_JOB.equals(referenceJobName)) \{ this.referenceJobName = StringUtils.EMPTY; } this.referenceJobName = referenceJobName;}{code}
Add Comment
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner commented on JENKINS-50084
Re: Integration Test for ReferenceFinder
Der Reference Job hat nichts mit dem Bauen zu tun, das muss im Recorder gesetzt werden. Das Setzen können Sie analog zu einem der bestehenden Tests machen. Diese Parameter im Test am einfachsten als Lambda übergeben:
/**
* Sets the UNSTABLE threshold to 8 and parse a file that contains exactly 8 warnings: the build should be
* unstable.
*/
@Test
public void shouldCreateUnstableResult() \{
FreeStyleProject project = createJobWithWorkspaceFile("eclipse.txt");
enableWarnings(project, publisher -> publisher.setUnstableTotalAll(7));
AnalysisResult result = scheduleBuildAndAssertStatus(project, Result.UNSTABLE);
assertThat(result).hasTotalSize(8);
assertThat(result).hasStatus(Status.WARNING);
HtmlPage page = getWebPage(result);
assertThat(page.getElementsByIdAndOrName("statistics")).hasSize(1);
}
Welche Setter Sie Nutzen können, sehen Sie in der Klasse IssuesRecorder. Folgende drei Setter sind verfügbar:
/**
* If \{@code true} then the result of the previous analysis run is ignored when searching for the reference,
* otherwise the result of the static analysis reference must be \{@link Result#SUCCESS}.
*
* @param ignoreAnalysisResult
* if \{@code true} then the previous build is always used
*/
@DataBoundSetter
public void setIgnoreAnalysisResult(final boolean ignoreAnalysisResult) \{
this.ignoreAnalysisResult = ignoreAnalysisResult;
}
/**
* If \{@code true} then only runs with an overall result of \{@link Result#SUCCESS} are considered as a reference,
* otherwise every run that contains results of the same static analysis configuration is considered.
*
* @param overallResultMustBeSuccess
* if \{@code true} then a stable build is used as reference
*/
@DataBoundSetter
public void setOverallResultMustBeSuccess(final boolean overallResultMustBeSuccess) \{
this.overallResultMustBeSuccess = overallResultMustBeSuccess;
}
/**
* Sets the reference job to get the results for the issue difference computation.
*
* @param referenceJobName
* the name of reference job
*/
@DataBoundSetter
public void setReferenceJobName(final String referenceJobName) \{
if (NO_REFERENCE_JOB.equals(referenceJobName)) \{
this.referenceJobName = StringUtils.EMPTY;
}
this.referenceJobName = referenceJobName;
}
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag edited a comment on JENKINS-50084 Re: Integration Test for ReferenceFinder Wie kann ich, wenn ich einen neuen Build baue einen Reference Job hinzufügen? Mit addProperty()? Was für eine JobProperty muss ich da setzten? Bzw. Wie kann ich algemein die Felder für den Reference Build konfigurieren (Im Test)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag commented on JENKINS-50084 Re: Integration Test for ReferenceFinder Wie kann ich, wenn ich einen neuen Build baue einen Reference Job hinzufügen? Mit addProperty()? Was für eine JobProperty muss ich da setzten? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Dazu langt es, das im Ergebnis (d.h. in der Instanz des AnalysisResult) der Methode {code}/** * Returns the reference static analysis run that has been used to compute the new issues. * * @return the reference build */public Optional> getReferenceBuild() {if (referenceJob == NO_REFERENCE) {return Optional.empty();}return new JenkinsFacade().getBuild(referenceJob, referenceBuild);}{code}auszuwerten. Dort sollte der entsprechende Build drin stehen.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner edited a comment on JENKINS-50084
Re: Integration Test for ReferenceFinder
Dazu langt es, im das Ergebnis (d.h. in der Instanz des AnalysisResult) der Methode {code}/** * Returns the reference static analysis run that has been used to compute the new issues. * * @return the reference build */public Optional> getReferenceBuild() {if (referenceJob == NO_REFERENCE) {return Optional.empty();}return new JenkinsFacade().getBuild(referenceJob, referenceBuild);}{code}auszuwerten. Dort sollte der entsprechende Build drin stehen.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title
Ulli Hafner commented on JENKINS-50084
Re: Integration Test for ReferenceFinder
Dazu langt es, das Ergebnis der Methode
/**
* Returns the reference static analysis run that has been used to compute the new issues.
*
* @return the reference build
*/
public Optional> getReferenceBuild() {
if (referenceJob == NO_REFERENCE) {
return Optional.empty();
}
return new JenkinsFacade().getBuild(referenceJob, referenceBuild);
}
auszuwerten. Dort sollte der entsprechende Build drin stehen.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle: Verglichen Der Status soll überprüft werden nachdem die Issues zwischen dem aktuellem Build und dem Vorherigen vorherigen verglichen wurden .Dabei müssen alle möglichen Ausgangszustände einberüchsichtigt werden. (Die Einstellungen im Build:- Ignore Previous Result - Overall Success- Reference Job - Vergleich mit einem anderen Jenkins Job) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle: Verglichen werden die Issues zwischen dem aktuellem Build und dem Vorherigen. Dabei müssen alle möglichen Ausgangszustände einberüchsichtigt werden. (Die Einstellungen im Build:- Ignore Previous Result +/- - Overall Success +/- - Reference Job - Vergleich mit einem anderen Build Jenkins Job) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag commented on JENKINS-50084 Re: Integration Test for ReferenceFinder Wie kann ich auf die Ergebnisse des ReferenceFinders (Dem Vergleich zum Vorherigen Build) zugreifen? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle: Angabe in Konfiguration: Nicht Vorhandener Job Ignore Previous Result + / Illegale Eingabe - > Fehler Vorhandener Job Overall Success +/ - > Ok Zirkuläre Abhängigkeit? - self zu self - self zu otherBuild ...zu self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: Job ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? Vergleich mit einem anderen Build Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "J
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle:Angabe in Konfiguration: Nicht Vorhandener Job / Illegale Eingabe -> Fehler Vorhandener Job -> Ok Zirkuläre Abhängigkeit? - self zu self - self zu otherBuild ...zu self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an em
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle:Angabe in Konfiguration: Nicht Vorhandener Job -> Fehler Vorhandener Job -> Ok Zirkuläre Abhängigkeit? - self -> zu self - self -> zu otherBuild ... -> zu self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag commented on JENKINS-50084 Re: Integration Test for ReferenceFinder Testfälle, die mir spontan eingefallen sind hinzugefügt. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag edited a comment on JENKINS-50084 Re: Integration Test for ReferenceFinder Testfälle, die mir spontan eingefallen sind in die Description hinzugefügt. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle:Angabe in Konfiguration: Nicht Vorhandener Job -> Fehler Vorhandener Job -> Ok Zirkuläre Abhängigkeit? - self -> self - self -> otherBuild ...-> self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issu
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Ulli Hafner started work on JENKINS-50084 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag assigned an issue to Arne Schöntag Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Assignee: Ulli Hafner Arne Schöntag Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Issue Type: Task Assignee: Ulli Hafner Components: analysis-core-plugin, warnings-plugin Created: 2018-03-10 19:08 Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups
