[JIRA] [job-dsl-plugin] (JENKINS-23318) GerritContext does not honor default settings in Jenkins' Gerrit Trigger config
Stephan
[JIRA] [job-dsl-plugin] (JENKINS-23318) GerritContext does not honor default settings in Jenkins' Gerrit Trigger config
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Stephan
[JIRA] [maven] (JENKINS-21597) New Maven Plugin causes build listeners to be called after the completion of every module, causing a lot of plugins to break
Stephan
[JIRA] [maven] (JENKINS-21597) New Maven Plugin causes slowdown for huge multimodule projects
Stephan
[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()
Stephan
[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()
Stephan
[JIRA] (JENKINS-16757) Commons Logging 1.1.1 creates Deadlocks
Stephan
[JIRA] (JENKINS-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered
Stephan
[JIRA] (JENKINS-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered
Stephan
[JIRA] (JENKINS-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered
Stephan
[JIRA] (JENKINS-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered
Stephan
[JIRA] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
Stephan
[JIRA] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
Stephan
[JIRA] (JENKINS-15229) There should be an option to provide the jobs for a certain build and all previous builds
Stephan
[JIRA] (JENKINS-14685) Subversion Plugin should be able to ignore property only commits (eps. Mergeinfos)
Stephan
[JIRA] (JENKINS-13758) Incremental Builds: If a build is aborted right after a failed one, not all necessary modules are build
[ https://issues.jenkins-ci.org/browse/JENKINS-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Pauxberger reassigned JENKINS-13758: Assignee: kutzi Since you did the original fix, can you please have a
[JIRA] (JENKINS-13758) Incrememntal Builds: If a build is aborted right after a failed one, not all necessary modules are build
Stephan Pauxberger created JENKINS-13758: Summary: Incrememntal Builds: If a build is aborted right after a failed one, not all necessary modules are build Key: JENKINS-13758 URL:
[JIRA] (JENKINS-13758) Incrememntal Builds: If a build is aborted right after a failed one, not all necessary modules are build
[ https://issues.jenkins-ci.org/browse/JENKINS-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Pauxberger updated JENKINS-13758: - Description: This is related to JENKINS-5764. We had the following scenario:
[JIRA] (JENKINS-13758) Incremental Builds: If a build is aborted right after a failed one, not all necessary modules are build
[ https://issues.jenkins-ci.org/browse/JENKINS-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Pauxberger updated JENKINS-13758: - Summary: Incremental Builds: If a build is aborted right after a failed
[JIRA] (JENKINS-13758) Incremental Builds: If a build is aborted right after a failed one, not all necessary modules are build
[ https://issues.jenkins-ci.org/browse/JENKINS-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Pauxberger updated JENKINS-13758: - Description: This is related to JENKINS-5764. We had the following scenario:
[JIRA] (JENKINS-13758) Incremental Builds: If a build is aborted right after a failed one, not all necessary modules are build
[ https://issues.jenkins-ci.org/browse/JENKINS-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162731#comment-162731 ] Stephan Pauxberger commented on JENKINS-13758: -- Created Pull Request #472, that
