[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Denys Digtiar reopened an issue I have created a fresh environment from 2.121 and installing: Pipeline: Multibranch 2.18 Github Branch Source Plugin 2.3.4 Job DSL 1.69 I was able to reproduce the issue using the steps in the description. I can still see Takeover for job-dsl-plugin_multibranch » master by source #1 from source that no longer exists Branch reopened: master (5045094d82daa475fe79e7f5e52eba58c6df9020) Scheduled build for branch: master after I re-run the Seed Job. Jenkins / JENKINS-43693 multibranchPipelineJob overrides old branch indexing sources Change By: Denys Digtiar Resolution: Fixed Status: Closed Reopened Add Comment
[JIRA] (JENKINS-51096) Support external H2 database
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51096 Re: Support external H2 database Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java http://jenkins-ci.org/commit/pipeline-maven-plugin/8fe121717a0c78ea1499ea66191f1bded2a3e4bd Log: JENKINS-51096 cleanup *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51096) Support external H2 database
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51096 Re: Support external H2 database Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginMonitoringDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/db/migration/h2/MigrationStep10.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncRunListener.java jenkins-plugin/src/main/resources/sql/h2/10_migration.sql jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/dba267e76dd42c9004e41e1a2ac760e8449d4666 Log: JENKINS-51096 database query time optimisation: introduce jenkins_job.last_build and jenkins_job.last_successful_build *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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
[JIRA] (JENKINS-51096) Support external H2 database
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51096 Re: Support external H2 database Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginMonitoringDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/db/migration/h2/MigrationStep10.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncRunListener.java jenkins-plugin/src/main/resources/sql/h2/10_migration.sql jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/704d42a6fdc5d31e2a778f44eba3d038999323ca Log: JENKINS-51096 database query time optimisation: introduce jenkins_job.last_build and jenkins_job.last_successful_build *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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
[JIRA] (JENKINS-51147) Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Title: Message Title Menghua Xiao updated an issue Jenkins / JENKINS-51147 Plugin Kubernetes Continuous Deploy Plugin makes input command fail Change By: Menghua Xiao Component/s: azure-commons-plugin 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-51147) Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Title: Message Title Menghua Xiao commented on JENKINS-51147 Re: Plugin Kubernetes Continuous Deploy Plugin makes input command fail This is related to JEP-200. The environment variables are injected via an action which will be serialized in the case you mention, however, the action is not white listed so an exception was thrown. Fixing 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-51147) Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Title: Message Title Menghua Xiao started work on JENKINS-51147 Change By: Menghua Xiao 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-38926) Add a report about the sandbox usage
Title: Message Title Denys Digtiar commented on JENKINS-38926 Re: Add a report about the sandbox usage Arnaud Héritier scriptAproval.xml is included in the bundle if the root configs component is selected. Do you think this is still relevant? 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-51179) Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint`
Title: Message Title Oleg Nenashev commented on JENKINS-51179 Re: Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint` I am still not sure what causes it in your case, but I have created https://github.com/jenkinsci/jenkins/pull/3439 which improves diagnostics and propagates proper errors to the Fingerprint loading engine. At least users will see which file causes issues 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-51179) Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint`
Title: Message Title Oleg Nenashev started work on JENKINS-51179 Change By: Oleg Nenashev 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-51179) Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint`
Title: Message Title Oleg Nenashev updated JENKINS-51179 Jenkins / JENKINS-51179 Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint` Change By: Oleg Nenashev 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-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Michael Pridemore commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Same issue. Jenkins 2.107.3 Bitbucket Pipeline for Blue Ocean 1.5.0 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-51179) Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint`
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-51179 Pipeline dies with `java.lang.String cannot be cast to hudson.model.Fingerprint` Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Mostyn Bramley-Moore commented on JENKINS-51253 Re: jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency These dependencies was removed: default-jre-headless (>= 2:1.8) | java8-runtime-headless How about adding back something like this? java8-runtime-headless | openjdk-8-jre-headless Though perhaps only java8-runtime-headless is required. 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
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-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Jacob Keller commented on JENKINS-50556 Re: git polling succeeds even when origin/master has nothing new I've had this pull request running as well in my test instance that I setup to test the thousands of branches case with the build details pull request as well, so far I haven't found any issues either. I'm curious what the ATH thing is as well. Hopefully we can get to the bottom of that one. 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-51280) Support skipping the checkout step for the git scm plugin
Title: Message Title Jason Pyeron commented on JENKINS-51280 Re: Support skipping the checkout step for the git scm plugin mildly related in concept 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-51283) CASC_JENKINS_CONFIG environment variable is not used anymore
Title: Message Title Nicolas De Loof commented on JENKINS-51283 Re: CASC_JENKINS_CONFIG environment variable is not used anymore please use https://github.com/jenkinsci/configuration-as-code-plugin/issues for CasC 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-51280) Support skipping the checkout step for the git scm plugin
Title: Message Title Jason Pyeron commented on JENKINS-51280 Re: Support skipping the checkout step for the git scm plugin I need to make tests, but to start: https://github.com/jenkinsci/git-plugin/pull/591 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-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz edited a comment on JENKINS-51267 Re: Warnings polluted with unrelated Qt MSBuild warnings I forgot to mention that it occurs only if:CMAKE_CXX_FLAGS=/Wall We also use CMAKE_EXE_LINKER_FLAGS=/FORCE:Multiple ") but it has no influence. 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-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz commented on JENKINS-51267 Re: Warnings polluted with unrelated Qt MSBuild warnings I forgot to mention that it occurs only if: CMAKE_CXX_FLAGS=/Wall We also use CMAKE_EXE_LINKER_FLAGS=/FORCE:Multiple") but it has no influence. 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-51284) [JEP-305] Make CasC incrementals-ready
Title: Message Title Baptiste Mathus updated JENKINS-51284 Jenkins / JENKINS-51284 [JEP-305] Make CasC incrementals-ready Change By: Baptiste Mathus 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-33269) Possible deadlock during checking remote job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33269 Re: Possible deadlock during checking remote job Code changed in jenkins User: cashlalala Path: src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java http://jenkins-ci.org/commit/parameterized-remote-trigger-plugin/607a85ed2babfc2a72444d426883d3ad65b067a1 Log: Merge pull request #20 from muczy/readtimeout_fix JENKINS-33269 Possible deadlock during checking remote job Compare: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/compare/1909ba74b246...607a85ed2bab *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51284) [JEP-305] Make CasC incrementals-ready
Title: Message Title Baptiste Mathus started work on JENKINS-51284 Change By: Baptiste Mathus 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-51281) [JEP-305] Incrementals-ify the Essentials plugin
Title: Message Title Baptiste Mathus updated JENKINS-51281 Jenkins / JENKINS-51281 [JEP-305] Incrementals-ify the Essentials plugin Change By: Baptiste Mathus 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-51284) [JEP-305] Make CasC incrementals-ready
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-51284 [JEP-305] Make CasC incrementals-ready Issue Type: Task Assignee: Baptiste Mathus Components: configuration-as-code-plugin Created: 2018-05-13 16:09 Labels: essentials essentials-triggered Priority: Major Reporter: Baptiste Mathus Configuration-as-Code is used in Essentials. It would be great and more practical that it's also incrementals-ready. https://github.com/jenkinsci/incrementals-tools/blob/master/README.md Add Comment
[JIRA] (JENKINS-51281) [JEP-305] Incrementsify the Essentials plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51281 [JEP-305] Incrementsify the Essentials plugin Change By: Baptiste Mathus Summary: [JEP-305] Incrementsalify Incrementsify the Essentials plugin 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-51281) [JEP-305] Incrementsalify the Essentials plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51281 [JEP-305] Incrementsalify the Essentials plugin Change By: Baptiste Mathus Summary: [JEP-305] Incrementalize Incrementsalify the Essentials plugin 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-51281) [JEP-305] Incrementals-ify the Essentials plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51281 [JEP-305] Incrementals-ify the Essentials plugin Change By: Baptiste Mathus Summary: [JEP-305] Incrementsify Incrementals-ify the Essentials plugin 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-51283) CASC_JENKINS_CONFIG environment variable is not used anymore
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-51283 CASC_JENKINS_CONFIG environment variable is not used anymore Issue Type: Task Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2018-05-13 15:58 Labels: essentials essentials-triggered Priority: Blocker Reporter: Baptiste Mathus Seems like a recent commit broke the usage of the CASC_JENKINS_CONFIG environment variable to point to the CasC configuration file. I found it out by updating to latest master of CasC in evergreen. It will be blocking us as long as we use latest tip of master. I bisected the issue: $ git bisect log git bisect start # good: [987b55ffdf7e7468ac9b739e5d7bee6129cfa7fc] [maven-release-plugin] prepare release configuration-as-code-0.4-a lpha git bisect good 987b55ffdf7e7468ac9b739e5d7bee6129cfa7fc # bad: [882d85351b045a33de7b91cf9cc5137d940a3626] Fix compilation error git bisect bad 882d85351b045a33de7b91cf9cc5137d940a3626 # good: [8921814751e0465ba31b853b9adec18bb557f0ff] [maven-release-plugin] prepare release configuration-as-code-0.5-a lpha git bisect good 8921814751e0465ba31b853b9adec18bb557f0ff # good: [4995ef13dc106f77bb121bcbaf25bd32157f68e3] integrations are not root elements git bisect good 4995ef13dc106f77bb121bcbaf25bd32157f68e3 # skip: [bdf0f0f47fea6d7641fc9741113ac4293409fee7] merge yaml trees before applying configuration #184 git bisect skip bdf0f0f47fea6d7641fc9741113ac4293409fee7 # skip: [18f91bdca9f96c72300f57e459c183796725251e] use the same merge sample as reported in issue git bisect skip 18f91bdca9f96c72300f57e459c183796725251e #
[JIRA] (JENKINS-51282) Azure VM plugin log is too chatty
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-51282 Azure VM plugin log is too chatty Issue Type: Task Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-05-13 11:45 Priority: Minor Reporter: Joseph Petersen jenkins | May 13, 2018 11:24:56 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Started Azure VM Maintainer Pool Size jenkins | May 13, 2018 11:24:56 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Finished Azure VM Maintainer Pool Size. 25 ms jenkins | May 13, 2018 11:25:56 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Started Azure VM Maintainer Pool Size jenkins | May 13, 2018 11:25:56 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Finished Azure VM Maintainer Pool Size. 32 ms jenkins | May 13, 2018 11:26:56 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Started Azure VM Maintainer Pool Size jenkins | May 13, 2018 11:26:56 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Finished Azure VM Maintainer Pool Size. 22 ms jenkins | May 13, 2018 11:26:58 AM hudson.model.AsyncPeriodicWork$1 run jenkins | INFO: Started Azure VM Agents Clean Task jenkins | May 13, 2018 11:26:58 AM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask execute jenkins | INFO: AzureVMAgentCleanUpTask: execute: start jenkins | May 13, 2018 11:26:58 AM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask execute jenkins | INFO: AzureVMAgentCleanUpTask: execute: Running clean with 5 minute timeout jenkins | May 13, 2018 11:26:58 AM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask cleanDeployments jenkins | INFO: AzureVMAgentCleanUpTask: cleanDeployments: Cleaning deployments jenkins | May 13, 2018 11:26:58 AM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask cleanDeployments jenkins | INFO:
[JIRA] (JENKINS-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Ivan Balepin commented on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history Bump - this looks pretty terrible. (Sidenote: trends graphs are useless) but even if they weren't, why are they breaking the pipeline view and pushing it down to the bottom of the page? This is especially bad with auto-refresh. The pipeline is supposed to refresh every second or so on auto-refresh. But you don't even see it!! because it's below the fold. All you see is stupid static trends, which don't even change with each refresh anyway. How can I get rid of the trend graphs at least, so that the actual useful, regularly refreshing pipeline view is up at the top again? I never really even asked for those trends graphs anyway. 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-51281) [JEP-305] Incrementalize the Essentials plugin
Title: Message Title Baptiste Mathus started work on JENKINS-51281 Change By: Baptiste Mathus 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-51281) [JEP-305] Incrementalize the Essentials plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51281 [JEP-305] Incrementalize the Essentials plugin Change By: Baptiste Mathus Labels: essentials essentials-triggered jep-305 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-51281) Incrementalize the Essentials plugin
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-51281 Incrementalize the Essentials plugin Issue Type: Task Assignee: Baptiste Mathus Components: essentials, essentials-plugin Created: 2018-05-13 11:36 Labels: essentials essentials-triggered Priority: Major Reporter: Baptiste Mathus We need to add the necessary configuration in the essentials-plugin so that we can consume it easily on each merge (and also because well, it is clearly one of the plugins that ought to use incrementals ). Add Comment
[JIRA] (JENKINS-51281) [JEP-305] Incrementalize the Essentials plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-51281 [JEP-305] Incrementalize the Essentials plugin Change By: Baptiste Mathus Summary: [JEP-305] Incrementalize the Essentials plugin 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-51280) Support skipping the checkout step for the git scm plugin
Title: Message Title Jason Pyeron created an issue Jenkins / JENKINS-51280 Support skipping the checkout step for the git scm plugin Issue Type: Improvement Assignee: Jason Pyeron Components: git-plugin Created: 2018-05-13 10:03 Priority: Minor Reporter: Jason Pyeron When performing complex SCM actions, it may be desirable to let the script perform all the actions after polling and fetch. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50245) us #584005: Branch Compare : expand Jenkins Plugin Capabilities - find common hash id
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50245 Re: us #584005: Branch Compare : expand Jenkins Plugin Capabilities - find common hash id Code changed in jenkins User: dshmaya Path: src/main/java/com/hpe/application/automation/tools/octane/model/processors/scm/GitSCMProcessor.java src/main/java/com/hpe/application/automation/tools/octane/model/processors/scm/SCMProcessor.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/0cd6e33b769b9c131b42581ffaac9d7f2ea840e9 Log: us #584005: Branch Compare : expand Jenkins Plugin Capabilities - find common hash id (JENKINS-50245)Branch compare feature (#87) us #584005: Branch Compare : expand Jenkins Plugin Capabilities - find common hash id - fix test Codacy/PR Quality 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-51279) Getting Job with ParameterizedTrigger with circular recursion is failing
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-51279 Getting Job with ParameterizedTrigger with circular recursion is failing Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2018-05-13 08:03 Labels: octane 5.3.5-beta 5.4-release Priority: Critical Reporter: Michael Seldin defect #627011 : Getting Job with ParameterizedTrigger with circular recursion is failing Add Comment
